[DE]Momaw

The "semi automatic mode" is the alt fire, where it shoots a bouncing glaive-like projectile, and that should be inflicting status on every bounce. Is that not what's happening?  The shotgun primary firing mode has a very weak status chance, by design.

Thank you for the reports, I've confirmed that this is a problem and we'll look into it for our next update.

10 minutes ago, DarthVaderRUS said:

Not fixed

Sorry about that, a change failed to get deployed.  Should work now though, if you care to try again?

The range does not seem to be functioning as the mod describes, we can look into that.

26 minutes ago, Katinka said:

Can we please get the Day of the Dead version of the Voidrig Helmet back?

This will be coming, we haven't forgotten!

We've confirmed that adding the Unreal Tournament skins to the Kuva Lich versions of the Ogris or the Drakgoon is causing those weapons to perform like their ordinary non-Lich counterparts.  This is unintended behavior, adding a cosmetic skin to a weapon should (with a very few grandfathered exceptions) not affect the weapon's mechanics. We'll be updating to fix this as soon as possible.

Thanks for your information! We've managed to make this happen under the microscope, a programmer will investigate

As many eager Tenno flock into Baro's shop on PC today (Dec 4) and throw their ducats at him for the latest and most exotic items from the Origin System, some have noticed something odd about the mod Primed Fulmination (Increases AOE radius on secondary weapons).  Specifically that it can stack with its ordinary non-Primed variant.  Primed mods have been a feature of Warframe for several years, and it's our long standing policy that you can't have both the Primed and ordinary version of the same mod equipped at the same time.  You'll notice that you can't equip both Firestorm mods on primaries, as intended. We missed setting this up for Primed Fulmination, which is an error on our part. We will be fixing this in a hotfix soon. Nothing will happen to the mods you already own or have ranked up, you will simply not be able to equip both as is the usual case with Primed mods.

15 hours ago, Catrovert said:

Just noticed making a litch and feeding the prognitor frame to the helmith will make the game freeze/crash. Not sure if any still use it but might be worth mentioning.

Do you get a WAR number with that? Or is it possible to give more detailed steps?  I just tried subsuming a warframe that was the same as my lich's Progenitor and there was no problem for me, it just opened the Arsenal with a different warframe.

Checking your account, Lich stole your credits. You'll have to kill them to get your reward back

Can you provide any more details about how this bug occurs? Video would be especially great.  For example does it only occur if you are the host, or only if you are the client? Is your Xaku fully ranked, or can it happen during the ranking up process? Did you host migrate during the mission? Did you die and respawn? Anything to help us narrow it down would be much appreciated and lead to a quicker resolution :)

I have checked for crashes submitted by you, but there are none. Do you see the crash handler at all? If you do not, try turning off anything that might be trying to inject itself into Warframe like screen recorders, graphical enhancements, overlays, Razer Chroma, and see if that lets the game start normally.  If you can isolate what is causing the game to crash, you could try updating or adjusting settings on the problem program.

When talking about crashes, the WAR number shown by the crash reporter can help us very quickly see what the error was. This number is not uniquely tied to your account, there is no privacy risk associated with sharing it. Also remember to write in the crash reporter a brief description of what you were doing, real people DO read these and sometimes the descriptions are invaluable to figuring out what happened!

In the case of Orb Vallis and DX12, It looks like there is a fix coming very soon for this specific problem.

Seems okay here. We didn't remove this feature and would not, for the reasons you describe. Can you post a screenshot?

2 hours ago, kyori said:

• TYPE: In game
• DESCRIPTION: Cannot use Shedu while holding onto data mass etc
• VISUAL: nil
• REPRODUCTION: Equip Shedu and pick up a data mass etc
• EXPECTED RESULT: Shedu should be able to be used when holding data mass etc
• OBSERVED RESULT: Every time after picking up a data mass etc, Shedu will be switched to secondary weapon instead.
• REPRODUCTION RATE: 100%

Not a bug. While this initially worked, issues developed because a lot of code assumed that all primary weapons were two-handed. We disabled this to avoid more complicated problems.

...

18 hours ago, Deadzer343 said:

• TYPE: Warframe ability scaling
• DESCRIPTION: chancing strengh from 189% to 204% 
• VISUAL: first one is with 204% secound is 189%
• 
• ...

18 hours ago, proyekcja said:

• TYPE: Ingame
• DESCRIPTION: Out of place material cost. Pulmonars requires 24 Parasitic Tethermaws - sounds like another kind of fish, may be a similar mistake to the Tink requirement on the bonewidow weapon pod.

*REPRODUCTION: check the Pulmonars build requirement

• EXPECTED RESULT: I expected not to need fish as nothing else has ever used just the fish
• OBSERVED RESULT: it cost fish
• REPRODUCTION RATE: it is still on the blueprint

The Parasitic Tethermaw is an organ that comes from the Lobotriscid fish!

(infested anatomy can be... strange, sometimes)

I can confirm that, coming with Deimos Arcana, we are fixing the Gladiator set bonus as well as Weeping Wounds and Blood Rush not working on Garuda's Talons.  The intended design is that mods on the Talons will not interact or combine with mods on your ordinary melee weapon. In other words if you put the Gladiator set on your Talons it will work for your Talons, but if you then equip a Skana that doesn't have those mods, it will not affect the Skana.  Any situation where the mods on the Talons are found to be affecting anything other than the Talons should be considered a bug.

1 hour ago, 60framespersecond said:

@[DE]MomawI can pretty much reproduce this 100%. My settings are a bit "special" in that I'm running at 30fps cap and have custom keybinds, "interact" is bound to "V".

Steps:

1. Join Fortuna, can be from Orbiter or from the Vallis (I have queuing set to Solo)
2. Go to the Backroom door by means of fast travel to Eudico, Little Duck, or just walk over
3. Check that your Esc is working
4. Stand in front of the door so the "[V] Enter Backro...

Sometimes this may happen if you try to login right when we're in the middle of publishing an update.  People already in-game will see the "Update in progress" message but if you're just starting up you would miss that. Should always just be a matter of waiting a minute or two and then starting from the launcher.  Sorry for the confusion!