the_Zinith

Requiem Fissures also do not give you bonus relics.

Firing Noctua (and Grimoire too after testing) sucks in certain particle effects and clothing within a radius of ~5m, centered on the book. This obscures your vision, especially when aiming. It's annoying at best and acts as an impromptu self-flashbang at worst. This stops when you stop firing. Particle effects affected include, but are not limited to: Thrown Tenet Ferrox pulses, Corpse cinders when an enemy dies to Heat damage, This one is considerably worse compared to others Clouds of smoke when certain robotics die, such as MOAs, Blue sparks that some Sentient units emit constantly, Impact sparks from Grimoire's Primary Fire, Impact sparks from gunfire in general, Radiation FX from Radiation Status Effect, Swirls of energy when a Leech Eximus heals a friendly unit, This one is also bad Drifter Intrinsics device in Teshin's Cave. Corrupted Jackal Mortar impact, Vengeful Flame, Tenebrous and Naberus Ephemeras, These are very mild Except for Naberus Ephemera, which can cover your entire screen in thin, black smoke Wisp Prime's Healing Reservoir, Wil-o-Wisp's ghost, Chyrinka Pillar's orb, Protea's shield grenade, It's quite bad for grenades which are still on the ground FX around Gauss' hands when Redline is active, Sparks when an Electricity Status Effect connects with the ground, Vitus Emblem. Cloth physics are also affected - Syandanas, armor pieces, and articles of clothing built into Warframes - like Wisp Prime's or Ballroom Simulacrum Baruuk's robes. This isn't that annoying, just looks goofy. Here's some videos of what this looks like:

Every time you open 5 relics in an endless Fissure mission, you are rewarded with a bonus, partially refined relic that matches the type of Fissure (Lith Fissure -> Lith relic). This relic can also be immediately selected and opened without leaving the mission. Omnia Fissures don't do that. While there is a spot for the relic in the endless mission reward track, no relic is actually given to you - it instead shows up as a blank tooltip. Video comparing 5 rotations of Axi and Omnia survival:

This is still an issue, and makes the weapon almost unusable in Corpus missions. I can comfortably stroll through a SP mission, only to hit an impenetrable blue wall made out of three Nullifiers - at this point I can either switch to operator and pop the bubble, or waste my heavy ammo, or dismiss the archgun, kill the Nullifiers and wait for the cooldown to reset, except in that time five different impenetrable walls have spawned on top of me, once again rendering the gun useless.

Unfortunately, this is no longer the case - the app once again mixes system and app languages together, with an added splash of English for a good measure, just like in my first post in this thread.

The bug appears to have resolved itself? Current app version is 4.15.16.0, which according to the Play Store was released on July 22 2023, and I remember that version still being bugged like 2-3 weeks ago. However it seems fine now? I did update my Android in the meantime, and WebView also received few updates - maybe that did it? All settings, names and descriptions are in English, as they should be. The above is only correct when the app's language is set to English. When you set it to a different language, all UI elements will always be in English, while item names, descriptions and news articles will be in your target language. This is better than before, since it takes your system language out of the equation. Still bad if you want to use a language other than English.

If you open a relic in a fissure mission, or pick up a medallion in a syndicate mission, then all future instances of the Archgun cooldown banner after that will be changed from its original, generic black box with a white border look, to a fancy, Vitruvian styled one, with additional text and UI elements based on whether you opened a relic or picked up a medallion. Video with before and after for relics; And a screenshot of the syndicate medallions:

This bug is entirely visual - there is a trace of the bubble left around a Nullifier after you break it, but it's non-functional. It doesn't protect the unit from damage or abilities, and it will not nullify you if you step inside. Still very annoying. Video demonstration using Sevagoth's slow:

Enemies affected by Sevagoth's 2 explode when they come in contact with his 1. This explosion sounds exactly like the ones from Nova's Molecular Prime. Maybe because the entire explosion VFX is lifted directly from her. A video for comparison:

When Larkspur is used as a heavy weapon, its beam will not damage a Nullifier or its bubble while the gun is locked onto said Nullifier unit. The beam will still correctly damage the bubble if you aim it without triggering the lock-on. Affects both base and prime versions of the gun. This bug was supposedly fixed in Update 29.10.0: New video of the bug: And my original bug report from late 2020:

The trigger for the bug may just be AoE. I haven't tested it thoroughly, but I managed to bug out my tornadoes by firing a Klamora/Phahd Amp at 20 railjack officers in simulacrum and spamming Zephyr's 2 at them when they were void magnetized. I also 'organically' triggered the bug in SP Circuit with Prisma Lens, Cyanex, and Stropha + Madurai, and in a mobile defense syndicate mission with Trumna, Pyrana Prime, and Stropha + Zenurik + Dethcube Prime w/ Helstrum. The bugged tornadoes behave as such: They did not absorb any damage types from my weapons, They spread only one instance of damage, After spreading the damage, they no longer reacted to gunfire, Tangentially related - 'destroyed' tornadoes also act like this. You can 'destroy' a tornado by feeding it absurd amounts of damage. It still CCs enemies, but doesn't absorb gunfire. A tornado bugged like this will flip between normal and 'dud' states with each cast. So on cast 1 you have a dud tornado, on cast 2 it's normal, on cast 3 it's a dud again, then 4 it's fixed, etc. This bug is unlike 'normal destroyed' tornadoes mentioned above, which would just work again for all future uses. And they do, just tested 'normal' destruction and future casts were all fine, no duds, no matter how many times I cast the ability after destroying my tornadoes. Here's the fun part, any combination of the 3 tornadoes can be bugged or normal or bugged-but-temporarily-in-working-condition, and they will flip accordingly: Let's name each tornado A, B and C. You manage to bug out A and B, but C stays healthy. On cast 1 A&B will be duds, C will be healthy. On cast 2 A&B will function and C will be healthy. Cast 3: A&B are duds, but you manage to bug out C. Cast 4: A&B function again, but C is a dud. Cast 5: A&B are duds but not C. Cast 6: A&B are functional but C is a dud. And so on. Here are 2 videos of the bug and the flipping behavior:

App version: 4.15.7.1 Android 12 Phone: SM-A528B/DS The Companion app does not respect its own language settings when said setting differs from the phone's system language. Namely, the app gets confused and merges the app setting language, system language and in some places default English. I did tests with Polish and Turkish as my system languages, so I'll use them in examples: When both system and app languages are set to the same language, everything matches (to be expected) Polish system language, Turkish app: Loading screen inside jokes will match system language - Polish Latest news will match app language - Turkish Menu flyout buttons, such as Foundry or Void Relics, will be in English* Except for bottom two - Settings and Logout, these will match system language - Polish Buttons inside, like Foundry subcategories and most other app UI elements, will match system language - Polish Item names and descriptions, including Warframes, Arcanes, etc. will match app language - Turkish Except Blueprints? The 'blueprint' part of a blueprint will match system language? - Polish Syndicate names, open world names will also match system language - Polish There are probably other inconsistencies as well * - The menu is usually in English, however after Turkish system language tests the menu sometimes stayed Turkish. I also did tests with German as system Language and the menu was German for a while, then I changed app language and the menu was in English, then after a while it was both in English and German. Additionally, after rebooting my phone the Companion app was fully in English for a moment, but then it 'woke' up after a while and mixed the languages again. This can be seen in the 'UI language swap' video at around 3:20. I close the app, wait a while and then it's all mixed up. Videos: