Fire at will bug COMPLETELY untouched

[Sham]

Besides being addressed in the patch notes still exists.

Anyone else?

[Korrex]

Odd, people are saying it's fixed...

EDIT: It's even mentioned in the patch notes.

[Chara H Dreemurr]

I wait for the patch dl to play Kislev. Fire at will still problematic ? :(

[๋]

Works for me. Matter of fact, I rarely ever have had a problem with it to begin with. I know it was 'random'.

[Falaris]

Fixed issues with ranged unit's 'Fire at Will' stance by increasing the number of checks units make to start firing. They will now also prioritise firing over maintaining positional unit cohesion (We are working through fixing as many instances of this bug as possible so if you run into any further issues after the update is live please do report them through the link at the bottom of this blog).

That note? The one direcitng you to

https://community.totalwar.com/wh3-support

if you find any instances of it not being fixed?

What's the issue that is completely untouched and what unit did you notice it with?

[Dreagon]

The way it is phrased does imply there are multiple causes of the bug and that they didn't manage to adress all of them so it's not a surprise it may still show up in some circumstances.

[Chara H Dreemurr]

Originally posted by Dreagon:

The way it is phrased does imply there are multiple causes of the bug and that they didn't manage to adress all of them so it's not a surprise it may still show up in some circumstances.

You are right.
My message would have sound like : " Did they fixed it ? " when it's reality, there is more instance of this bug.
Fixing one instance (or at least try it) doesn't mean it will be perfect.

My bad

[Chara H Dreemurr]

I mean, i really want to play Kislev but i'm afraid of this bug. I did experiment it with Elspeth and it was enough to stop the campaign. :/

[Sham]

Originally posted by Falaris:

Fixed issues with ranged unit's 'Fire at Will' stance by increasing the number of checks units make to start firing. They will now also prioritise firing over maintaining positional unit cohesion (We are working through fixing as many instances of this bug as possible so if you run into any further issues after the update is live please do report them through the link at the bottom of this blog).

That note? The one direcitng you to

https://community.totalwar.com/wh3-support

if you find any instances of it not being fixed?

What's the issue that is completely untouched and what unit did you notice it with?

Kislev. Booted up a Tzarina campaign and did 2 battles.

Toggling did nothing. Units started working fine after targeting a unit, then would fire at will correctly after.

I have a late chorf campaign I'm gonna try next

[Mr Robert House]

for ♥♥♥♥ sake i want to play kislev... the low tier hybrid infantry spam faction...

[bondKI]

they mentioned ONE instance of that bug gone. there are multiple however, as they have also said...

[cernodan]

I see people still believe CA's patch notes.
You've only yourself to blame for this naivete.

[Ben]

Originally posted by Korrex:

Odd, people are saying it's fixed...

EDIT: It's even mentioned in the patch notes.

It's been proved quite a few times by Legend that what is written in the patch notes isn't always done..

[dolby]

why do i have a feeling we gonna see this threads for months now....
works fine (Mother Ostanka) but i never had this bug anyway.

[eYe]

It's not fixed, as for people saying they rarely encountered the bug you probably don't do large army battles. If you play 1 stack vs 1 stack of armies (20 v 20) you probably won't get the bug. It usually triggers when there's more than 40 units on the battlefield. There's some kind of engine limitation going on here.

[Falaris]

Originally posted by eYe:

It's not fixed, as for people saying they rarely encountered the bug you probably don't do large army battles. If you play 1 stack vs 1 stack of armies (20 v 20) you probably won't get the bug. It usually triggers when there's more than 40 units on the battlefield. There's some kind of engine limitation going on here.

The problem is that the targeting check had fairly low priority, it could go quite a few seconds between each check, and they would be from center-to-center, so it would miss opportunities to fire.

The checks have upped priority and more varied source checks for fire. That's the fix.

Some units probably didn't get the memo, so there's units it might not have been applied for. That's what the link is for.

If the unit is positioned so another unit is in the way, it still won't fire anyway, but then, that's working as intended.