_Rhea_

Didn't have a single crash since I disabled SSAO 3 weeks ago.

When you have 10 hits per second, clicking is not an option. You'd truly have to use scripts / macros / whatever.

No it doesn't, that means that you can't simply switch to your primary by clicking the LMB if you have it set up the way you do, meaning, shooting flying mobs is a lot more clunky on a melee build. Please fix the bug. Still present, still annoying. More so on some missions, such as Index. Every single time anyone on the entire team kills an enemy it interrupts melee. 100% reproducible.

Don't get me wrong, I love making builds, and all that, however I also have a life. A single weapon ground up from zero (which might need "a potato") requires often a lot of resources - a lot more than one can grind in a single week, if that person has a life. And my life is quite the nolife at the moment (what, 2-4 hours of warframe a day? That's quite a lot for having a life. I question having one now. !@#$%) Even if you're going only for the box and pass on the last reward, in other words using either a frame, or a weapon that isn't on the list. You still need to grind for the other. There is plenty of other content in this game that I am yet to fully explore, I'd like to have some time to do that as well.

As an example I'll use Protea. I have quite the spammy build, and pressing 1~4 all the time is quite a gymnastics exercise. (I actually have a joint condition that makes it quite painful.) For that reason I take advantage of the "Use Selected Power" on a mouse button. However, it being what it is and I spam all 4 abilities, and not just one, so it keeps switching to the wrong ability all the time. To not mention that it even considers "selected power" transference... now that's very annoying. Why even have "select next/previous power" keybinds if they're absolutely pointless and the selection is immediately overwritten by using transference or another ability? I'd love to see a toggle to enable/disable this auto switch. Please. Reviving the old thread:

Yes it's a well known issue that neither AMD nor nvidia wants to fix - nvidia doesn't play well with AMD chipsets, blames AMD for it - while AMD says that it's the nvidia driver that's crashing. Both true, but someone should fix it. That said, there is still a trigger condition in the game. Very high chance of the crash when you load back into your orbiter after a mission. So the game developer can also address this issue instead of blaming the above mentioned parties ;)

Didn't play in two days. Just wanted to play one mission today, crash immediately. So no, not really fixed. Just moody - every other day is good.

Both myself and my friends have encountered this 100% reproducible out of bounds reset while "walking" through a specific corridor - see video: https://cloud.rhea.dev/s/T9yXy7eZr4fMAQr (While I'm at it, please start designing maps with proper collisions instead of abusing out of bounds where it doesn't belong - walls and ceiling - there are abilities that require you to dash straight up to execute. Or rework all those abilities (including Naramon school requiring a ground slam)) (Professional Nitpick #2 - stop using mesh colliders for the entire map. Poor performance, poor player experience, getting stuck on door handles, etc. Simplify the collisions.)

Not a single crash today. I haven't changed anything at all. I don't think that changing the directX version solved your issue either, sounds like a coincidence.

Since my builds are mostly melee, all relying on melee arcane given armour to not go pop when I trip on a banana peel... The difficult content in the game is now basically unplayable because of this.

So I tried to cap my framerate at 60 to see if it makes any difference... Same thing, crashed after the mission finished, just after I loaded back to orbiter~ WAR-3967763 Edit: So the game crashed two more times in one mission, that's about 4x in an hour. Unplayable.

Crash reporter actually did something this time, to whom it may be of concern: WAR-3967763

Mind you I'd rate this priority 1 because it does make endgame unplayable - imagine going for an hour+ long steel path survival fissure or arbitration (which you HAVE TO do in order to get certain warframes like Voruna which drop only from rotation C i.e. every 20 minutes) aaaaand then enjoy the crash, deleting all your progress and drops. If there are any logs or any additional information I can provide, yell what you need, happy to help - your friendly neighborhood senior game programmer Rhea. Cheers.

Today it crashed after I finished a standard invasion in a public squad, the last visible frame has some green sh* on the left - missing textures or something? (Orbiter is equipped with the xmas theme. But given that it crashes in random missions as well, it's unlikely to be the issue.) Edit: Had the exact same crash again with the green sh* on the left after exiting a mission, this time with different loadout (frame/weapons/everything) I feel like these are two different and yet related crashes - one is in the orbiter with xmas snow being "green" (see my other issue for transparent snow, probably related!!) and the other crash is during a mission. The one I remember was on Lua, potentially similar snowy powdery textures missing or something causing it to crash? (That said it crashed after 17 minutes of fighting in one spot in survival so...) Edit2: Nevermind, just crashed when I loaded into orbiter after a mission, without xmas decorations (all disabled)

Attached memtest:

More than two crashes a day since the Dante update, including hotfix #1 and #2. These seem to be driver crashes. All in game graphics settings as high as possible (except the obvious disabled ones like motion blur or depth), framerate capped 144, GPU 3090Ti (evga) on Windows10 I get a web pop-up when it happens yelling at me about faulty RAM, overheating or overclocking issues. I don't think that 75°C degrees is too much for 30 series, or 50°C for 5950x cpu. Thorough memtest is passing, ain't got no overclocking beyond standard PBO/XMP.

As the title says, notice that all the snow piles are transparent. 2024.03.27.17.14

Zariman bounties reward incorrect number of Voidplumes, this also applies to Cavia in the form of the Standing reward (report already exists) so it looks like a related issues :) I've also noticed that the "difficulty indicators" on each bounty depict one "star" for all non-steel path bounties, and two "stars" for all steel path bounties. 2024.03.27.17.14

I have the same issue, there is no fix that I know of. If you're on the same network with other players, the last one to log-in is the only functional client even if you all have different ports configured in Warframe settings, correctly forwarded to your respective machines. Hopefully they will actually give enough poop to fix it some day, it's been a bug in their net code since the beginning of time. I mean imagine having a family and wanting to play the same game in the same house. How outrageous.