It’s good to see some of the issues this update created being fixed. Is there any word on when Ogryn will be getting some love @FatsharkStrawHat?
2 Likes
Inb4 it’s another “totally deliberate change that was not communicated for a year for reasons” like the close range ‘change’ was.
1 Like
I’m sure I’ll get yelled at for incessantly yelling in FS bug reports.
FWIW, StrawHat did confirm it was a bug on Reddit.
6 Likes
That does make a difference. Thanks StrawHat!
2 Likes
maybe it was fixed but in the constant version controls it got overwritten. like when scab bosses got buffed to not jump into their deaths at the start of their mission, that got removed until this update.
Can you guys revert this patch. Me and all of my friends are crashing every game instead of 2 or 3 games. Its the same old 2001 and 2014 error code thats been an issue for 7 months now. Its just worse after this patch
1 Like
4 out of 5 matches I played since this patch had either me (3 times) or another player crash once or multiple times per 20 minute match.
But hey, the freeze into crash is gone, it is now a instant disconnect into just as instant “wanna rejoin the lobby”.
Hey! OK, so here is what happened, you aren’t crazy:
- I had searched it up and I found a ticket. I was told it’s being fixed in the next hotfix. Which is when that comment came out
- In Hotfix 1.5.4, we had this note:
After it was released, players told us it didn’t fix it as intended.
I’ve been doing more digging the past couple days because I’ve seen comments like yours. I was told this was working as intended, where they are deactivated upon getting hit. However, we’re working on a change to this, but it has other implications that require more testing, so this fix will likely come at the beginning of next year.
I know this isn’t the ideal answer, but I hope it helps answer some questions.
TL;DR - Part of it was fixed, the rest was working as intended. We’re changing that, but it has more implications that need to be tested further before we can release it.
3 Likes
Hey! To you and @adrianh, would you be able to submit reports for us? Ideally, either on the Technical Support area on the forums, or using this link (https://support.fatshark.se/hc/en-us/requests/new)? I’m trying to get more information for the team so we can narrow down the issues. It’s good the freeze into crash is gone, but clearly there is more work to be done. The more data we have, the easier it is to try to repro and identify. 
Thank you in advance.
2 Likes
While you’re a legend for digging into it further, I’m rather confused, maybe more so because of lack of sleep.
I don’t see how it’s working as intended when it changes ~2 year old established behavior and the introduced bug was fixed for the chain weapons and force weapons that suffered from the exact same issue, while the power weapons were left unfixed, missing the keep_active_on_stun=true that the other 2 groups got.
I think maybe there’s a game of broken telephone going on here, miscommunications across 3 levels; we don’t seem to be talking about the same things?
Regardless, next year is unbearably long for popular weapons, it’s already been a month since the fix for other 2 weapon families and the bug as a whole started at the end of September '24 when they refactored some of the underlying special activation code, I’m guessing in anticipation of the new weapons.
P.S. Then yeah, it looks like that bug report ticket was closed prematurely as the fix was only partial.
This patch did not fix the crashing issue. I myself and others are still crashing constantly.
Nope, I read that post and was confused as well, I just couldn’t think of a good way of saying “That doesn’t really make sense.” without typing out way more than I could be bothered with.