Hexerin Posted November 23, 2023 Share Posted November 23, 2023 The damage increase is not being applied to the weapon. Testing screenshots: Spoiler Hoplite Virtue: Trusty Sidearm, which grants the same damage increase but actually functions: These results are 100% consistent no matter what random status procs occur, over dozens of individual instances of hits. Also, just to be absolutely sure I fully left, changed the evolution elsewhere, and returned. Link to comment Share on other sites More sharing options...
Tiltskillet Posted November 23, 2023 Share Posted November 23, 2023 It's working for me in the Sim. Damage goes from 459 to 663 on yellow crit and Critical Parallel with the buff active, which is showing up on the buff bar. I noticed you're testing against Corpus in the images. The buff is triggered on personal shield break, not enemy, which should be spelled out on both this and Incarnon Gorgon. 1 Link to comment Share on other sites More sharing options...
Hexerin Posted November 24, 2023 Author Share Posted November 24, 2023 (edited) 8 hours ago, Tiltskillet said: It's working for me in the Sim. Damage goes from 459 to 663 on yellow crit and Critical Parallel with the buff active, which is showing up on the buff bar. I noticed you're testing against Corpus in the images. The buff is triggered on personal shield break, not enemy, which should be spelled out on both this and Incarnon Gorgon. I'm not talking about the shield break buff, I'm talking about the base damage increase. As should be obvious considering I'm comparing it to the other evolution option, which doesn't give conditional damage increase yet causes the gun to deal more damage. Which I explained in the post. Here, I even retested vs Grineer, just to really drive it home: Spoiler Hoplite Virtue, still not working: Trusty Sidearm, which actually works: Here are the two evolutions, for reference: Spoiler Notice how they provide the same baseline buff to damage. Hoplite Virtue isn't functional, while Trusty Sidearm is. This isn't a new bug, it's been around for several months at least. It's been reported multiple times too. Edited November 24, 2023 by Hexerin Link to comment Share on other sites More sharing options...
Tiltskillet Posted November 24, 2023 Share Posted November 24, 2023 15 hours ago, Hexerin said: I'm not talking about the shield break buff, I'm talking about the base damage increase. As should be obvious considering I'm comparing it to the other evolution option, which doesn't give conditional damage increase yet causes the gun to deal more damage. Which I explained in the post. Oh sorry. As penance I confirmed this isn't working in mission, after noticing that the evolution wasn't changing properly in the Sim. (I was still getting both Trusty Sidearm buffs even after switching to Hoplite.) In mission, I was getting 266 / 531 non-Incarnon body shot damage with against Overguard with Trusty Sidearm, 239/478 with Hoplite. Unmodded, no other pertinent Evos or buffs, other than a damage blessing that was active for both. On 2023-11-23 at 2:43 AM, Hexerin said: Also, just to be absolutely sure I fully left, changed the evolution elsewhere, and returned. For me it wasn't changing over unless I went all the way back to the Orbiter. I only tested this briefly, but that would match the behavior of past Sim equipment update bugs. Very inconvenient, and hopefully it doesn't mean those larger problems are back. Link to comment Share on other sites More sharing options...
Hexerin Posted November 25, 2023 Author Share Posted November 25, 2023 11 hours ago, Tiltskillet said: For me it wasn't changing over unless I went all the way back to the Orbiter. I only tested this briefly, but that would match the behavior of past Sim equipment update bugs. Very inconvenient, and hopefully it doesn't mean those larger problems are back. In my experience, you only have to go back to relay. Has never failed me in my testing thus far. Link to comment Share on other sites More sharing options...
henri1004 Posted August 27 Share Posted August 27 Commenting just to (hopefully) bring some attention to this. Bug is still active with the exact behavior as specified above. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now