Skip to content
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

Closed
MeSaber opened this issue Jul 25, 2024 · 7 comments
Closed

Tremor erratically changing target #3472

MeSaber opened this issue Jul 25, 2024 · 7 comments
Labels
Bug Something isn't working

Comments

@MeSaber
Copy link

MeSaber commented Jul 25, 2024

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

@MeSaber MeSaber added the Bug Something isn't working label Jul 25, 2024
@SethDGamre
Copy link
Collaborator

I'm gonna bet this is related to proximity priority forcing target changes to farther target.

@MeSaber
Copy link
Author

MeSaber commented Oct 2, 2024

Yes this is still an issue with gauntlet/rattle in high trajectory too.

@SethDGamre
Copy link
Collaborator

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.

@SethDGamre
Copy link
Collaborator

https://youtu.be/ExU1KKRJy6g example of the dumb shit that happens when you have proximity priority < -1

@SethDGamre
Copy link
Collaborator

https://discord.com/channels/549281623154229250/724924957074915358/1291221698460389407 reducing to -1 seems to create better results

@SethDGamre
Copy link
Collaborator

I'm gonna consolidate these proximityPriority issues into this and seek approval.
#3807

@MeSaber
Copy link
Author

MeSaber commented Oct 8, 2024

https://youtu.be/ExU1KKRJy6g example of the dumb shit that happens when you have proximity priority < -1

This is the reason you cannot use high trajectory ever because it becomes a micro management issue or manually aiming :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants