Jump to content

CitizenV

Grand Master
  • Posts

    1,102
  • Joined

  • Last visited

Posts posted by CitizenV

    • TYPE: In-game
    • DESCRIPTION: Completing what we thought was 2nd isolation vault of 3. More on this below.
    • VISUAL: p1O8Xl5.jpg
    • REPRODUCTION: No idea. I assume it's desync since it happened to another teammate (not host) too.
    • EXPECTED RESULT: We should have seen 4 different symbols.
    • OBSERVED RESULT: Me and another player both saw 4 Fass symbols. It may have happened to the 3rd client player but he didn't respond.
    • REPRODUCTION RATE: I've only seen this once.

    The comment above about us thinking this was the "2nd" of 3 isolation vaults is referring to general bugs with the bounties not being completed accurately. We did 3 isolation vaults in this session and each one was treated as the 1st. We only encountered 1 Necramecha in each vault and rewards matched T1. When we completed each vault, they were slow to update and buggy. The waypoint didn't show us towards the Esophage. And it took several minutes until after we all exited the vault for it to show us the bounty reward. This isn't the first session where I've encountered issues like this. It has happened several times today and I've yet to be able to complete a T3 vault because of these bugs.

     

    • Like 1
  1. I just finished several Gian Point runs with the same group, and the host ended the run by returning to dock, and leaving. If it matters, he left while we were still loading into the dojo and onboard his Railjack.

    I exited the Railjack, went to the Configure Railjack terminal, and found none of the Mission Rewards were available. Intrinsics were the same as before the mission, no new wreckage, missing all the avionics we collected, etc.

    I left his dojo, and went to check it out in my own dojo and all the rewards were there. Never had this happen before today's patch.

  2. 9 hours ago, CitizenV said:
    • TYPE: Scarlet Spear Event
    • DESCRIPTION: We were in Scarlet Spear 49. Around 2:10 AM EST 4/4/20. The flotilla had reached 41/100 then all progressed stopped. Literally, there were 0 kill codes being transmitted from ground crews for 10-15 minutes. The flotilla chat was only space crews talking between themselves about the slow ground crews. When our squad left our mission, the flotilla appeared to be reset. We were back to 0/100 but it was active again. There were 4 ground crews and kill codes were being sent.
      • You can see this in the picture below. The kill code receivers ranking shows significant progress was made in this flotilla, but the overall stats claim we're at 1/100. It doesn't match.
    • VISUAL: osT2QJn.jpg
    • REPRODUCTION: No idea. This happened to a clanmate so it isn't a one-time bug. He actually predicted that when we'd return to the flotilla that we'd be back at 0/100, and he was right.
    • EXPECTED RESULT: The event should have proceeded as normal. Ground crew send kill codes. Space crew uses them.
    • OBSERVED RESULT: All progress halted in Scarlet Spear 49, then was reset to 0/100.
    • REPRODUCTION RATE: I've only seen it once.

     

    Same bug occurred around 11:55 EST, 4/4/20 in Scarlet Spear 6. The flotilla reached 87/100 and I noticed some people were complaining about slow kill codes. I was just looking at the store and didn't realize I was in a full flotilla.

    I joined a ground squad to help out, and a few minutes in, it was reset to 0/100. Needless to say, they didn't reach 100/100...

    Screenshot of chat showing the highest score before reset:

    8yhkupR.jpg

    Reset occurred a few minutes later:

    0lleU9v.jpg

    Picture of flotilla after wave ended:

    xwmikNF.jpg

    • TYPE: Scarlet Spear Event
    • DESCRIPTION: We were in Scarlet Spear 49. Around 2:10 AM EST 4/4/20. The flotilla had reached 41/100 then all progressed stopped. Literally, there were 0 kill codes being transmitted from ground crews for 10-15 minutes. The flotilla chat was only space crews talking between themselves about the slow ground crews. When our squad left our mission, the flotilla appeared to be reset. We were back to 0/100 but it was active again. There were 4 ground crews and kill codes were being sent.
      • You can see this in the picture below. The kill code receivers ranking shows significant progress was made in this flotilla, but the overall stats claim we're at 1/100. It doesn't match.
    • VISUAL: osT2QJn.jpg
    • REPRODUCTION: No idea. This happened to a clanmate so it isn't a one-time bug. He actually predicted that when we'd return to the flotilla that we'd be back at 0/100, and he was right.
    • EXPECTED RESULT: The event should have proceeded as normal. Ground crew send kill codes. Space crew uses them.
    • OBSERVED RESULT: All progress halted in Scarlet Spear 49, then was reset to 0/100.
    • REPRODUCTION RATE: I've only seen it once.

     

  3. The MR 28 test is extremely buggy when it comes to throwing the canister. Half the time I'm unable to throw the canister and it might be linked to switching to/from Operator. Despite practicing 4-5 times to ensure I could complete it even with the bugs, I still failed my actual test because I couldn't throw the canister 4 of the times...

     

    EDIT: After further testing, the parrying gunfire animation seems to prevent throwing a canister.

    • Like 2
  4. It happened again. This time I was waiting between each Mercy finisher, but it still bugged out. This time I remembered to save the recording at least.

    I waited it out a minute with no change, and left in the end. I didn't want to block my squadmate's Liches from spawning.

    Host/client issue? I don't remember if I was in a squad the first time this happened, but I was the 2nd and 3rd times. In both cases I went solo afterwards, partially in case it was a client bug and partially so other people's Liches didn't block my Lich spawn.

    giphy.gif

    giphy.gif

  5. Now we're on Hotfix 26.1.3  and this bug still exists unfortunately. I don't remember encountering it again since above but did today

    We were playing a Defense node on Ceres, and my Kuva Lich spawned on the other side of the map from the defense objective. I helped kill the Lich as quickly as I could, since all my teammates left the objective to attack it. The pod was fine, but I wanted to get the Lich out of the way ASAP.

    I knew 2/3 Requiem and guessed the 3rd correctly. But I was left with a kneeling Kuva Lich and no menu to do anything. I stayed for over a minute, before deciding to just disconnect.

    yIIcu4u.jpg

    If I'd had to guess, it's because I killed it too quickly? I basically took out each section of health and did the Mercy finisher as soon as it was available. EDIT: IIRC, my "fix" the first time around was to kill it slower. Let HUD return to normal after each Mercy before doing the next one.

    If it matters, I was using Wisp and in a squad this time. EDIT: The first time this happened I was playing solo and using Nezha.

  6. If you have the chat box open on the Nightwave Acts menu, part of the chat filter list can be seen outside of the chat box.

    It only seems to happen when Nightwave Acts menu is open. I don't see it occurring when its overlaying other menus.

    cpQxiXA.jpg

  7. When going to the settings menu and changing keybinds, there's no prompt to save changes like other menu settings. Its current behavior:

    1. Options > Controls > Customize Key Bindings

    2. Change something or set to Defaults

    3. Press Back or hit esc key

    4. Press Back or hit esc key = no confirmation pop-up that asks "Your settings have been modified. Save changes?"

    Instead, it saves as if you pressed Confirm in step 4. This means if you accidentally set your keybinds to default, you're going to end up saving the changes if you think you'll get a prompt to undo the changes like any other settings change. The only option to get around it is to exit Warframe before it saves.
     

  8. Final update: pretty sure this is due to melee attack speed affecting the Kuva Lich finisher animation. I've been playing with Wisp lately, so my melee attack speed is quite fast. This causes the animation to glitch.

    When I play other frames, this doesn't occur.

  9. I'm pretty sure this bug was introduced with Tek Enhance earlier this year.

    The duration for Smeeta's Charm is incorrect when you switch to operator mode. It always displays the buff as having more time than it actually does.

     

    Screenshots below as an example. They were taken only a few seconds apart (time to swap to operator).

    yAu5blk.jpg

    VCyjKbg.jpg

     

  10. I was playing the Lua Spy that was in my Kuva Lich's territory and encountered several bugs:

    1) The mission was labeled an Exterminate on the map. I believe this error occurs with other Lua missions as well (e.g. Rescue labeled as Exterminate).

    2) A thrall spawned inside vault A and instantly triggered the alarms when I started the vault. Please prevent thralls from spawning inside vaults like other enemy invasions.

    3) Liset Air Support could not pause the timer in any of the vaults. Ordis said there were no alarms active.

  11. Bug still exists as of Hotfix 26.0.7. Example below.

    Lich killed me on 2nd Requiem. Note it doesn't show the incorrect Requiem.

    AccyEFO.jpg

     

    After I revived, the Requiem display stayed.

    KhVQjdz.jpg

     

    What I forgot to capture is what happened after another player completed a finisher on their Lich. My incorrect Requiem showed up, and my HUD came back.

  12. EDIT: Reformatted and added more pictures.

    1. My HUD disappears when performing a finisher on a Lich. The finisher's own animation will also be cut short, and my HUD will disappear. All that's left is the Requeim display on the bottom. Sometimes the HUD comes back if I'm able to perform another finisher. Most of the time I'm stuck with this until the end of the mission.

    5rXijwG.png

    2. My Kuva Lich killed me on my 2nd Requiem even though it was correct. Based on several successful attempts, I already knew my first two Requiems were LOHK then FASS. Despite not changing the order, my Lich killed me when I attempted the 2nd finisher with FASS in the last mission... It was even displayed in my log that way.

    UNSOmfB.png\\

     

    3. This is probably the same bug as #1. The Requiem in-game display doesn't match the actual attempts. The screenshot below is after I died during my 3rd Requiem, but the display still only shows the 1st. The log showed my actual attempt and correctly showed I failed on the 3rd.

     

    K1QNrG0.jpg  mR0NToG.png

     

  13. Typically when traveling through portals, carrying your momentum isn't a bad thing. However today I found there are instances when it works against you...

    When doing the Hall of Ascensions Nightwave on Lua, I was playing Nezha and his momentum carried me immediately out of 3 of the reward room portals after I entered them. That isn't an issue when you can go right back in, but that's not always the case. The agility puzzle teleports you back down and closes the entrance. I had to repeat the puzzle if I wanted an Agility Drift...

  14. At around 4:45 PM EST on Saturday , August 24th there was a Kuva Siphon mission on Adrastea Jupiter. It was a Sabotage mission type. Instead of loading the new Gas City tile set, it had the old standard Corpus ship tile set. It was still definitely Jupiter as we got Hexenon drops.

  15. After helping a clan mate with the task, I'm fairly sure you have to be within a certain distance. We didn't wait for him to get to the Doma Thumper before killing it, and he didn't get any credit. We found another Doma, waited until he was within a few meters, killed it and he got credit.

  16. I was in a squad for this week's Thumper tasks. We found a non-Doma Thumper first, and that completed the "Tusk Thumpin" task. After 2 more Thumpers, we found a Doma. I did not get credit for this, even after finishing the mission successfully. My squadmates supposedly got it, but they left before they actually confirmed...

    In any case, this nightwave task is somewhat bugged.

     

    Update: Second Doma kill registered. I wonder if the 1st one didn't work because I was relatively far away sniping it.

    • Like 1
×
×
  • Create New...