Crash after winning siege battle.

[DecayWolf]

Playing Asrai, battle against VCoast. Won the siege, game freezed then crashed.

Till then I had zero crashes, after 4.0.4 it always happens.

Every single time I come back to the game, when I am about to win and finish the campaign, CA releases their untested BS patches that results into campaign loss. Every single time.

Lol, and you guys complain why you aren't selling DLCs anymore? I wonder why.

[czpetr]

Yep, happens against vampire counts and daemons too. Winning siege causes freeze, then CTD. Started after 4.0.4.

It is likely connected to the crumbling mechanic.

[DecayWolf]

It only happens in offensive siege battles.

Land battles and defensive siege battles doesn't trigger CTD. Seems to be direct related to any faction that can desintegrate/crumble. And only happens if these units were still in the battle, after the outcome is decided.

Good job CA.

[Red-_-Monkey]

Somehow this always happens after a patch. I've seen it for years. I'm starting to think they do this on purpose to spite us. Why do we worship devs? There's so many bugs that are just "meh", 1 correction of text and they DNGAF. Bugs that are fixed always come back when they face criticism.

[huey30]

I've also noticed that after 4.0.4 archers once again think that they are melee units

[DecayWolf]

Originally posted by Red-_-Monkey:

Somehow this always happens after a patch. I've seen it for years. I'm starting to think they do this on purpose to spite us. Why do we worship devs? There's so many bugs that are just "meh", 1 correction of text and they DNGAF. Bugs that are fixed always come back when they face criticism.

Could be a wild theory, but maybe someone inside does have spite on their consumer base, for boycotting the latest DLC, which somehow that person believes the recent layoffs is directly related and not due business as a whole. I mean there are dumb people everywhere.

Either is that, or they are just unbeliavable incompetant. I mean how the heck they release a patch, that cannot be rolled back without testing it beforehand?

I mean, campaigns often take hudrends of hours, and can be completely ruined by ♥♥♥♥ like this. Players whom play on legendary is even worse, could be a complete death sentence for the campaign.

I swear, every time I try to get back into the game, CA releases this BS, over and over again.

[Red-_-Monkey]

Originally posted by DecayWolf:

Originally posted by Red-_-Monkey:

Somehow this always happens after a patch. I've seen it for years. I'm starting to think they do this on purpose to spite us. Why do we worship devs? There's so many bugs that are just "meh", 1 correction of text and they DNGAF. Bugs that are fixed always come back when they face criticism.

Could be a wild theory, but maybe someone inside does have spite on their consumer base, for boycotting the latest DLC, which somehow that person believes the recent layoffs is directly related and not due business as a whole. I mean there are dumb people everywhere.

Either is that, or they are just unbeliavable incompetant. I mean how the heck they release a patch, that cannot be rolled back without testing it beforehand?

I mean, campaigns often take hudrends of hours, and can be completely ruined by ♥♥♥♥ like this. Players whom play on legendary is even worse, could be a complete death sentence for the campaign.

I swear, every time I try to get back into the game, CA releases this BS, over and over again.

Maybe they do it to sabotage CA/SEGA? The kroxigor issue with nakai must have been intentional. For that to occur you're have to remove code/text...
They cycle staff so often from project to project. WH3 needs a dedicated staff with intrinsic knowledge of every patch... verbatim. It's a complex game. CA/SEGA clearly does not understand this. The staff themselves need stability.

[Deo]

so stupid, only came back a few days ago to play and now stuck at undead siege because of crashes (

[DecayWolf]

Originally posted by Red-_-Monkey:

Originally posted by DecayWolf:

Could be a wild theory, but maybe someone inside does have spite on their consumer base, for boycotting the latest DLC, which somehow that person believes the recent layoffs is directly related and not due business as a whole. I mean there are dumb people everywhere.

Either is that, or they are just unbeliavable incompetant. I mean how the heck they release a patch, that cannot be rolled back without testing it beforehand?

I mean, campaigns often take hudrends of hours, and can be completely ruined by ♥♥♥♥ like this. Players whom play on legendary is even worse, could be a complete death sentence for the campaign.

I swear, every time I try to get back into the game, CA releases this BS, over and over again.

Maybe they do it to sabotage CA/SEGA? The kroxigor issue with nakai must have been intentional. For that to occur you're have to remove code...
They cycle staff so often from project to project. WH3 needs a dedicated staff with intrinsic knowledge of every patch... verbatim. It's a complex game. CA/SEGA clearly does not understand this. The staff themselves need stability.

Good point, also CA sucks at saving old data, which may also have caused this.
Still though, there's no excuse for releasing a patch without testing, and without the option to roll back. That just incompetence.

[Triple G]

Originally posted by DecayWolf:

Good point, also CA sucks at saving old data, which may also have caused this.
Still though, there's no excuse for releasing a patch without testing, and without the option to roll back. That just incompetence.

I´m unsure if there´s any company which lets You roll back to some hotfix, which fixes 4 bugs.

What they could do - is release all their stuff on an actual beta branch, because that´s where it belongs to - and then You could always roll back to the "last known stable version". But on the other hand they don´t need to do it, when nobody from CA bothers to care about the steam forums, the technical issues reports and the bug reports - or given they had a beta branch - the feedback section. But perhaps that´s just small dev stuff - as a bigger dev You release the crap without testing, and release other patches after patches after patches later, while some core or major issues never get addressed, but 150 other bugs which You didn´t even know about. Or they just write random stuff in their bigger patch notes "Fixed this and that" (while it was never broken)