-
Notifications
You must be signed in to change notification settings - Fork 244
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
Damaged units create smoke at exact position outside LOS #2990
Comments
Btw I could find a replay where I abuse this bug if that's necessary for reproduction, just lmk if you can't reproduce it |
I think a replay could be handy to check which unit this was and probably first check if unit is not at fault. |
It happens regardless of unit type, CEGs are just synced so use the unit's real position |
Ive actually tried this out and i think its a feature rather than bug. You still need airlos to see smoke iirc so its not fog smoke. This adds a layer of repairing is a good thing to stop the smoke to pinpoint your location, just as the smoke speed also tells units current HP. Imo it should stay as is and used as a tactical advantage if you dont repair your units. Edit: The smoke appears around 43% HP with long intervals and smoke gradually speeds up as HP gets lower. https://i.imgur.com/84LCeC4.png |
So it seems the cegs are shown on airlos. |
if its airlos, that screenshot makes it seem thats too far away for it |
iirc Floris removed airlos from specific smoke cegs? |
Description
The problem is that when heavily damaged, units outside of your los can be pinpointed without even having radar via the smoke they give off
Expected Behaviour
Either the smoke should not be seen outside LOS or it should be placed where radar wobble would have the unit
Actual Behaviour
The smoke from a unit outside LOS is placed exactly on its position
Reproduction steps
Get a unit that is heavily damaged outside your los, and use some ranged unit, like rocket bots or mobile light artillery, to show that the unit is indeed at the exact position.
Other
No response
The text was updated successfully, but these errors were encountered: