2020-09-30 05:43 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0006260Spring engineGeneralpublic2019-07-22 21:54
Assigned To 
Product Version104.0 +git 
Target VersionFixed in Version 
Summary0006260: Add modrule to set how high above ground is required to visible for the corresponding ground square to be visible
DescriptionCurrently units cannot see tall units which are partially occluded by terrain. This is particularly annoying when they're under fire from tall laser towers on top of cliffs.

There was discussion about how LOS could be improved on spring on a zk forum thread:


[03:26:42] <raaar> from Hokomoko's description
[03:26:44] <raaar> "Now let's try to explain concisely how the engine works:
[03:26:44] <raaar> If you can trace a line from the seeing unit's losheight (a game configurable value) to ~5 elmos above ground without hitting any ground in the middle and without being over the maximum sight distance, all ground units in the square will be visible."
[03:27:15] <raaar> that "5" elmos could be a modrule game devs could change

On that post I describe a more complex system with N layers for ground LOS and each unit's visibility depends on whether the highest layer below their height is visible or not.
TagsNo tags attached.
Checked infolog.txt for ErrorsIrrelevant
Attached Files




Kloot (developer)

Last edited: 2019-07-22 19:55

View 2 revisions

"a more complex system with N layers for ground LOS"

Sure, have fun implementing it.

This is a less general duplicate of 0005880.


hokomoko (developer)

Basically you want to allow games to decide whether it's worse to have invisible tall units that should have been visible, or visible short units that shouldn't have been visible.

I suppose that could be done and the perf effect won't be terrible, but I suspect no one including you will ever use it after they see the unintended consequences.


hokomoko (developer)

The N layers system is never gonna happen and I suspect the same is true for doing units heights/losheights for the facts that were already mentioned in the thread and in 0005880.

-Issue History
Date Modified Username Field Change
2019-07-22 04:53 raaar New Issue
2019-07-22 10:14 Kloot Note Added: 0020050
2019-07-22 19:55 Kloot Status new => closed
2019-07-22 19:55 Kloot Resolution open => duplicate
2019-07-22 19:55 Kloot Note Edited: 0020050 View Revisions
2019-07-22 21:51 hokomoko Note Added: 0020052
2019-07-22 21:54 hokomoko Note Added: 0020053
+Issue History