-
Notifications
You must be signed in to change notification settings - Fork 332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tremor erratically changing target #3472
Comments
I'm gonna bet this is related to proximity priority forcing target changes to farther target. |
Yes this is still an issue with gauntlet/rattle in high trajectory too. |
it's as I thought. proximityPriority = -3 for the tremor, and -2 for only high trajectory mode on the gauntlet. I typically avoid using them because of this exact problem where it forces the unit to reacquire long range targets rather than committing to a shot on a barely closer target. |
https://youtu.be/ExU1KKRJy6g example of the dumb shit that happens when you have proximity priority < -1 |
https://discord.com/channels/549281623154229250/724924957074915358/1291221698460389407 reducing to -1 seems to create better results |
I'm gonna consolidate these proximityPriority issues into this and seek approval. |
This is the reason you cannot use high trajectory ever because it becomes a micro management issue or manually aiming :/ |
Description
After you switched to 'spread fire' it seems to behave very badly, it stops firing because it has to move turret towards the other side of targets instead of using closest targets. It also seem to prefer targets in the backline of targets found, and switch between backline target sides so turret keeps changing.
2024-07-25_06-51-40-638_Center Command BAR v1_105.1.1-2511-g747f18b BAR105.sdfz.zip
Expected Behaviour
Fire at closest target in both modes.
Edit: Maybe not change target until current target drops out of attack range.
Actual Behaviour
Erratic target changing especially in spread mode.
Reproduction steps
No response
Other
No response
The text was updated successfully, but these errors were encountered: