I've had this bug a few days ago, and sent the save file to Legend. He made a video about it: https://youtu.be/ZKCQFZzXM6s?si=-prmfXEWc9oXTFEn

I've also just published a bug report here on the forum with this exact situation, please go and upvote it, so that the developers take it seriously! 

Yeah, it's atrocious and kind of ruins most archer/gun focused factions. Sadly the community here seems to be more obsessed with the location of an obscure legendary lady and with the premature reveal of the future DLC's contents.

There's dozens of bug reports in the bug report forum regarding this. Big content creators have flagged it too. CA should be well aware. 6.1 has a major rework to a range heavy faction, they would have to be extremely stupid not to get it fixed for then.

So about 50/50 I'd say.

Does Dev acknowledge yet ?

​

Pray#3234 wrote:

Does Dev acknowledge yet ?

No they haven't, they actually have never officially acknowledged it outside of a few posts on bug reports that they close prematurely. It might be one of those "unfixable" bugs like the gate bug. They really shot themselves in the foot with this because it's only really gotten worse and worse as the games progressed. I think they would've been better off just not touching it because at the start of the game we went from "units being able to stack and fire through each other" to "units just won't fire at all"

The last Hotfix also broke the animations of multiple throwing units.
While it usually works when they are given a direct attack order, if they are only on fire at will Dwarf Miners, Ironbreakers, Infernal Ironsworn and to a lesser extent the exalted Plaguebearers will bug out and many entities will be stuck in a failed animation loop without actually throwing anything.
I have already seen multiple tournament matches where these units failed to do anything as a result, but it appears to me that the community overall is not really aware of it yet.
I am really wondering what kind of fundamental change ended up breaking range units like this.

​

Vrooktar#4671 wrote:

The last Hotfix also broke the animations of multiple throwing units.
While it usually works when they are given a direct attack order, if they are only on fire at will Dwarf Miners, Ironbreakers, Infernal Ironsworn and to a lesser extent the exalted Plaguebearers will bug out and many entities will be stuck in a failed animation loop without actually throwing anything.
I have already seen multiple tournament matches where these units failed to do anything as a result, but it appears to me that the community overall is not really aware of it yet.
I am really wondering what kind of fundamental change ended up breaking range units like this.

I've seen this as well, sometimes half the group doesn't throw, sometimes the entire unit doesn't throw. They might've just broken the "ranged" animation for all the units since the positioning thing wasn't really unit specific and could happen to pretty much any unit (melee included). Makes you wonder what kind of spaghetti code they've written

​

Vrooktar#4671 wrote:

The last Hotfix also broke the animations of multiple throwing units.
While it usually works when they are given a direct attack order, if they are only on fire at will Dwarf Miners, Ironbreakers, Infernal Ironsworn and to a lesser extent the exalted Plaguebearers will bug out and many entities will be stuck in a failed animation loop without actually throwing anything.
I have already seen multiple tournament matches where these units failed to do anything as a result, but it appears to me that the community overall is not really aware of it yet.
I am really wondering what kind of fundamental change ended up breaking range units like this.

In that same dwarf campaign, I've seen miners be hesitant to throw their charges... that's the reason then.

​

Giojay69#7451 wrote:

​

Vrooktar#4671 wrote:

The last Hotfix also broke the animations of multiple throwing units.
While it usually works when they are given a direct attack order, if they are only on fire at will Dwarf Miners, Ironbreakers, Infernal Ironsworn and to a lesser extent the exalted Plaguebearers will bug out and many entities will be stuck in a failed animation loop without actually throwing anything.
I have already seen multiple tournament matches where these units failed to do anything as a result, but it appears to me that the community overall is not really aware of it yet.
I am really wondering what kind of fundamental change ended up breaking range units like this.

I've seen this as well, sometimes half the group doesn't throw, sometimes the entire unit doesn't throw. They might've just broken the "ranged" animation for all the units since the positioning thing wasn't really unit specific and could happen to pretty much any unit (melee included). Makes you wonder what kind of spaghetti code they've written

For one of my mod units that used the Ironbreaker animation I was able to circumvent the issue by changing the animation category.
But I don't really understand how exactly that works.

By the way, a month ago I made a bug report on that.
If folks consider it important they can push for an investigation:
The latest Hotfix broke the throwing animation for Ironbreakers, Miners and Infernal Ironsworn 

This is just great. Anytime I go up against more than one stack this shit triggers. Renders the game unplayable indeed. We need a Hotfix like NOW!

Hey all, this is happening to me in my current Ikit Claw campaign. I definitely notice it on battles where I’m facing more than one army, so like 40 unit vs 40 unit battles.

Even if I give direct orders to fire they seem slow to do it. But yeah I am definitely seeing ranged units just stand there and it is driving me bonkers. 

I’m sorry if it has already been posted, but has anyone linked their bug reports? I would like to upvote them as much as possible, please.

I am really disappointed this glitch is present. How does this get past testing? I mean almost any ranged unit seems affected at times. I don’t usually like to throw “game breaking” out there but if ranged units won’t shoot things at range, that seems very much broken.

Has CA acknowledged this?

Yes, it has been reported 10 times or so in the bugs section. If only we had an option to roll back updates.

Fire at will bug

Units getting stuck setting up ladders in sieges

Gate bug

Unit order delay

Unit pathfinding issues in sieges

I have lost hope that CA will fix the messy battles, one would think that they would focus on battles as its a cornerstone of the franchise but alas here we are, bugs running rampant like usual

Here's to hoping that they will do better with their next main title Total War franchise 

Heavily doubt it though.

OK, I went to the bugs forum and upvoted every posting on this bug I could find. I saw the CA said they are aware of the issue… I really hope they fix this soon. I decided last night to just give up on my Ikit Claw campaign even though I am hours into it near turn 100. It is just too frustrating. Especially in the middle and advanced part of campaigns since this bug happens in larger battles (like 40 v 40) therefore the bug is happening in pretty much every battle. Lame.

I think I’ll just table this game for a while. I’ll check back in a month or so and see if it ever gets fixed, but this kind of crap makes me wary of not just WH3 but pretty much any game from CA. If they can’t be trusted to get basic stuff like this working in a game then they can’t be trusted in the future at all. I really hope they understand how this type of bug ruins the game at a fundamental level and ruins trust.

Stuff like this is pretty much why I don't trust CA doing a decent 40k game. 

​

Player#11296 wrote:

OK, I went to the bugs forum and upvoted every posting on this bug I could find. I saw the CA said they are aware of the issue… I really hope they fix this soon. I decided last night to just give up on my Ikit Claw campaign even though I am hours into it near turn 100. It is just too frustrating. Especially in the middle and advanced part of campaigns since this bug happens in larger battles (like 40 v 40) therefore the bug is happening in pretty much every battle. Lame.

I think I’ll just table this game for a while. I’ll check back in a month or so and see if it ever gets fixed, but this kind of crap makes me wary of not just WH3 but pretty much any game from CA. If they can’t be trusted to get basic stuff like this working in a game then they can’t be trusted in the future at all. I really hope they understand how this type of bug ruins the game at a fundamental level and ruins trust.

Hear ya brother, i dumped my recent Malakkai campaign for the same reason

Gave me a reason to play a Khorne campaign into late endgame but still, one should not have to refrain from doing certain content because the game developer refuse to spend the resources needed to deliver a functioning product.

CA have been absolutely terrible in the bug fixing department in the majority of the prior decade

It's horrendous frankly put.

So I wanted to go back to WH3 and play a full campaign which is something I haven't done in years literally. Then I saw report after report about this bug and even the community bugfix mod team saying they can't do anything about it as it's CA's tweaks to the game engine that messed this up and I simply gave up on the game. I can't I just can't start an Empire campaign and have this stupid thing ruin my campaign by endlessly frustrating me. So... will they fix it? Oh hell no. I don't think CA has any people left in the WH3 team capable of working with the core engine.

But here's the more interesting part: from what modders say it's an issue caused by CA's attempts to optimize the game by avoiding the engine hogging resources via limiting it on purpose [which from what other folks say was the root cause of WH3's problems with Intel processors]. So if what's being said is correct, they ruined the game by trying to optimize it which is so very much CA-like that absolutely does not surprise me.

The problem for CA is simple thou: the most popular factions in this game have always been ranged ones - of course outside of this forum where there's an ongoing obsession by a militant minority with stuff like Chaos factions. But most people play stuff like Empire, HE, Dwarfs etc. And w/ the ranged bug those factions just aren't viable unless you want to experience endless frustration which as we all know is why anybody would be launching this game and buying DLCs. Frustration - the key ingredient.

So good job CA. 

PS: stop making excuses for them. If they are incapable of fixing this [which they might be] they can just give modders access to the engine and let them fix it which they will as they have with so many other bugs CA could not be bothered to fix - ever. It's just a question of them just not bothering with minor stuff like yet another game and most of all user experience breaking bug.

​

Captain_Rex#1635 wrote:

Stuff like this is pretty much why I don't trust CA doing a decent 40k game. 

same, if the total war warhammer community doesn't hype it i don't understand how it will sell enough

​

valexis2#4045 wrote:

​

ravonline#3849 wrote:

So I wanted to go back to WH3 and play a full campaign which is something I haven't done in years literally. Then I saw report after report about this bug and even the community bugfix mod team saying they can't do anything about it as it's CA's tweaks to the game engine that messed this up and I simply gave up on the game. I can't I just can't start an Empire campaign and have this stupid thing ruin my campaign by endlessly frustrating me. So... will they fix it? Oh hell no. I don't think CA has any people left in the WH3 team capable of working with the core engine.

But here's the more interesting part: from what modders say it's an issue caused by CA's attempts to optimize the game by avoiding the engine hogging resources via limiting it on purpose [which from what other folks say was the root cause of WH3's problems with Intel processors]. So if what's being said is correct, they ruined the game by trying to optimize it which is so very much CA-like that absolutely does not surprise me.

The problem for CA is simple thou: the most popular factions in this game have always been ranged ones - of course outside of this forum where there's an ongoing obsession by a militant minority with stuff like Chaos factions. But most people play stuff like Empire, HE, Dwarfs etc. And w/ the ranged bug those factions just aren't viable unless you want to experience endless frustration which as we all know is why anybody would be launching this game and buying DLCs. Frustration - the key ingredient.

So good job CA. 

PS: stop making excuses for them. If they are incapable of fixing this [which they might be] they can just give modders access to the engine and let them fix it which they will as they have with so many other bugs CA could not be bothered to fix - ever. It's just a question of them just not bothering with minor stuff like yet another game and most of all user experience breaking bug.

yeah creative assembly is a disaster as a company, i don't understand how it's still here

More access to coding with the help of AI will bring so much competition than gaming sofware comapnies will very very quickly disapear

Believe it or not Mistral's AI and Qwen [I think it's from alibaba - ie China] are rather good with WH3 tweaks [db and stuff like that]. I wouldn't be surprised if in a few years AI would finally allow us to get the games we want - bug free and dev. whims free.