DeckChairVonBananaCamel

keyboard/mouse, or controller?

actually i also miss kohm having non-hitscan projectiles

ah, that makes sense yeah i like having the option of passively gain syndicate standing whilst doing other stuff, like saving solaris prisoners, or in this case collecting voidplumes from the angels

that and the super lo-fi radio filter

the netracells are here to stay as far as im aware?

nah, not the size, the atmosphere though looking back to your original comment, i think i might have misread what you were on about

hmm or like a "always copy frame colours" checkbox or something?

Did you ever play Mercenaries: Playground of Destruction on the PS2/Xbox? God that game was sick. Playing that game upscaled to 4k and running at 60fps via backwards compatibility is legit the only reason I'm tempted to get an xbox

Nah, DE keeps a limited number of prime things in circulation at any time, when an item is "retired" it gets moved into an inactive pool of stuff. Running parallel to prime access (the newest stuff) is another deal that brings back a couple of older prime access deals. And occaisionally (and im pretty sure right now) an event will be run where a buttload of older prime stuff comes back and becomes available to get from Varzia on maroo's bazaar (either available from relics purchasable with ingame currency, or pre-built using real money)

Deimos is tiny! Like really tiny. On average Deimos is only 12.4km (7.7 miles) across, but the skybox environment shows it stretching off into the distance like a vast planetary body, instead of curving down and away (or i suppose up if the cambion drift is on the concave side). Deimos is, without hyperbole, actually small enough to fit in a railjack mission with enough room to spare that you could have a cool mission where you fly around it and assault surface targets. The cambion drift is around 1.7km across, this is approximately how big it would look in comparison to the surface of Deimos: EDIT: This is not a real criticism of the game, it's in general discussion for a reason, I'm just having fun. Thought I'd add this juuuuuuust in case

depends on the cards you get, but a well built valkyr wrecks

i mean OP meant "additive with other crit mods" because that would make sense that they would then say they are not sure if it is worth it

i think they meant additive with other crit mods, which as far as im aware it is?

YYYYYYYEEEEEEEEEEEAAAAAAAAAAAAAHHHHHHHHHHHHHHH!!!!!! Just tested it and i cannot seem to replicate the bug anymore!! LETS GOOOOOOOOOO!!!

Ive added step-by-step instructions on how to fix it with this new method to the original post (with credit to you, of course 😊)

OH MY GOD!! I gave this a test and fiddled a bit more with it, just dodge roll and press and hold the secondary fire button until you finish your roll and it deactivates the bug!

you dont need to wait for the animation to end before switching out from your warframe, you just need to make sure you release the heavy attack button before hitting the transference button

the beam mode contributes to the buff, but does not benefit from it. However it is very strong, so even though it only applies to the magazine throw it is definitely worth it

I always forget about controllers, I hope my explanation of how to stop the infinite void blast bug is at least helpful for you

I originally posted this a week ago in the "Abyss of Dagath" subforum, which disappeared a few days later with the release of "Whispers in the Walls" (i had to recover it from google cache). I am reposting it mainly because a fix players can use is included (down the bottom under "Stopping it once it starts", but you may need to read the rest for context on what it means) so I feel it is still relevant. Also sorry to Lord_Drod for retagging you, just wanted to make sure people knew you were responsible for the alternate, preventative solution. THE MELEE BUG FIRST Ok so first im going to lay down the basics of this bug. With the auto melee implementation the melee key is more of a toggle. In simple terms pressing the key seems to send a "start melee" command, and then releasing it sends the "stop melee" command. There is a bug you can play around with resulting from the fact that the warframe "remembers" that it is still supposed to be in auto-melee mode even when you enter and then exit operator mode. To replicate this bug easily you can do the following: Start melee by holding down the quick melee key. Whilst holding that key, activate transference to switch to operator Release the quick melee key. Switch back to the warframe. This should result in a situation where the warframe remembers receiving the "start melee" command, but never received the "stop melee" command as you released the key whilst your controls were assigned to the operator. So you will witness the warframe proceed to start swinging wildly without need of player input (until you press and release the melee key again so it gets the "stop melee" command). This works with both regular and heavy attacks, as the heavy attacks are also affected by auto melee. THE VOID BLAST BUG I want to thank @Lord_Drod for pointing me in the right direction by mentioning that this bug usually isnt encountered if you have "heavy attack" and "secondary fire" bound to different keys You can fairly reliably reproduce the void blast bug by following either these steps: Switch to operator Switch back AFTER triggering the switch-back, but BEFORE fully returning to your warframe press and hold the "secondary fire" button, but don't release it until AFTER the transfer completes. Or these steps: Get downed Trigger "Last Gasp" Kill the required 3 enemies (or 1 eximus) AFTER killing the required enemies, but BEFORE fully returning to your warframe press and hold the "secondary fire" button, but don't release it until AFTER the transfer completes. Either way the aim is to PRESS but not RELEASE the secondary fire button during the transfer-back-to-warframe animation THE SPECULATION When reviewing the EE.log for the mission i found this: This is the process the game goes through when successfully using Last Gasp (referred to here as "Second Chance") From what i can tell the process goes like this Last gasp succeeds, so the warframe is revived from the downed state Immortality is applied to both operator (or in this case drifter) and the warframe The control scheme changes Control is switched back to the warframe and the warframe control scheme is loaded in Now, step 3 is referencing the line: 1501.491 Input [Info]: InitMapping for all devices with bindings /Configs/EE.cfg/LotusWindows_KeyBindings and filter /Lotus/Powersuits/PowersuitAbilities/TransferenceInputFilter This step appears present whenever transference is used, but I cannot seem to find reference to this in EE.cfg, so my ASSUMPTION is that this is a hard-coded filter that is supposed to BLOCK inputs during the short window where you are switching back and forth from operator mode. My GUESS is that this control mapping includes heavy attack, but doesn't filter it out? Meaning there is a 502 millisecond window where you can trigger a "heavy attack" whilst still technically being in control of the operator. Combine this with the first bug where auto melee allows the warframe to "remember" the melee input but instead apply it to the operator, and then the next time you switch to operator it is stuck in a loop of "heavy attack" resulting in void blast firing on a loop. STOPPING IT ONCE IT STARTS SIGNIFICANT DEVELOPMENT! Thanks to @PollexMessier For putting me on the right track with this one! You can deactivate the bug even when in Last Gasp with the following solution: Whilst in operator mode (and the infinite void blast bug is occuring) perform a dodge roll. Whilst the dodge roll animation is playing, press but dont release secondary fire. Once the roll ends and the operator starts void blasting again, release the secondary fire. The old solution: All you have to do is send the "stop heavy attacking" command during the same switch-back-to-warframe animation, this is easily done by managing to RELEASE the "heavy attack" key during that animation (simply tap that key during the animation) BEWARE HOWEVER! You cannot solve this problem in Last Gasp mode as you cannot switch back to your warframe, it must be done when in normal operator mode!! This concludes my TED talk Edit (originally added as 1st comment): I want to add that the reason this issue is so prevalent is likely because we all hammer the secondary fire button when in last gasp mode (in my case to send as many phahd projectiles into the wild as i can)

Nevermind i took the risk and now have a log of the mission!

so im in a mission with the annoying "operator gets stuck in void blast loop" bug. Just want to make sure the mission log will contain this bug. Does the EE.log only generate on crash, or does it generate after every mission? Basically i want to make sure i am able to provide the info to DE because i hate this bug Edit: i have the game paused right now

Whats the specs of your pc?

I dont think i hae encountered this bug, but i play solo. Is this a multiplayer bug?

was it a weekly or a daily? i cannot remember If it was a weekly it'll be part of the "catchup" mechanic, complete a week's challenges and the nightwave will start giving you incomplete past weeklies to help players who cannot play consistently