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

[SUGGESTION] Exempt Aerial units from uncaching units #256

Open
Sargers opened this issue Apr 25, 2020 · 1 comment
Open

[SUGGESTION] Exempt Aerial units from uncaching units #256

Sargers opened this issue Apr 25, 2020 · 1 comment
Labels
cache caching related issue suggestion

Comments

@Sargers
Copy link
Contributor

Sargers commented Apr 25, 2020

Is your feature related to a problem? Please describe.
As far as I can tell jet pilots and the like are able to uncache units while flying about. Usually not a massive issue but for fairly dense missions this can cause issues of fps as units gets cached in and out constantly. (Secondhand info but apparently some FPS issues in REINDEER were caused by this).

Describe the solution you'd like
Aerial units such as jet pilots do not cause units to be uncached.

Describe alternatives you've considered
Possibly have the uncaching be based on a timer so a jet has to be within uncache range for a period of time before caching?

Additional context
Obviously this adds the issue of jet pilots not being able to scout individual patrols away from the platoon and will see units get cached in by the platoon which is immersion breaking. However I feel the scouting of objectives can be solved by static objects giving away positions and patrols far away enough to be cached arent really relevant threats to a platoon.

@Sargers Sargers added suggestion cache caching related issue labels Apr 25, 2020
@Bosenator
Copy link
Contributor

I'll look into adding a dynamic blacklisting of players into the rewrite at some point in the future. I think it'll just have to be a module, that if present, means aircraft will not uncache AI - one that can be Zeusable. Loitering/time based caching rules are sort of a headache to achieve, unfortunately. This will sadly mostly be reliant upon mission makers to keep their attachements in mind, more so than any automated system can achieve performantly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cache caching related issue suggestion
Projects
None yet
Development

No branches or pull requests

2 participants