2024-04-16 18:45 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0004920Spring engineGeneralpublic2015-09-17 12:24
ReporterGoogle_Frog 
Assigned Tohokomoko 
PrioritynormalSeveritymajorReproducibilitysometimes
StatusresolvedResolutionfixed 
Product Version100.0 
Target VersionFixed in Version 
Summary0004920: LoS terrain occlusion failure case
DescriptionThis replay shows a case where a unit cannot see an enemy unit which it should be able to see. The enemy unit is in its sight range and over basically flat terrain. The test unit has losEmitHeight = 40.
Steps To ReproduceDo what is done in the replay. Put corrl in a certain location.
Additional InformationZK v1.3.7.5
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
has duplicate 0004917resolvedhokomoko LOS: jammer area is not displayed correctly 
+Relationships

-Notes

~0015046

Google_Frog (reporter)

It is as if LOS is emit point is offset further east and south from the unit position.

~0015073

Google_Frog (reporter)

The bug is obvious if units are moved to the edge of the map. The Ms are Weavers (arm_spider). The center Weaver on the bottom of the map is slightly out from the map edge.

This is with
los = {
      losMipLevel = 3,
      losMul = 1,
      airMipLevel = 4,
      airMul = 1,
    },

~0015075

hokomoko (developer)

Fix 5c33dbe1bce0aa654d426484be9d96d08a0a3b96 committed to develop branch: Fix 0004920

Round is incorrect when converting floating point position into a grid.
For example when the entire map is a single cell you'd want everything
between 0 and 1 to be 0., repo: spring changeset id: 5497
+Notes

-Issue History
Date Modified Username Field Change
2015-07-29 16:49 Google_Frog New Issue
2015-07-29 16:49 Google_Frog File Added: 20150730_004310_TartarusV7_100.sdf
2015-08-06 15:22 Google_Frog File Added: lowerRightLOS.jpg
2015-08-06 15:22 Google_Frog Note Added: 0015046
2015-08-19 10:00 Google_Frog File Added: mapEdgeLos.jpg
2015-08-19 10:02 Google_Frog Note Added: 0015073
2015-08-19 18:30 hokomoko Changeset attached => spring develop 5c33dbe1
2015-08-19 18:30 hokomoko Note Added: 0015075
2015-08-19 18:30 hokomoko Assigned To => hokomoko
2015-08-19 18:30 hokomoko Status new => resolved
2015-08-19 18:30 hokomoko Resolution open => fixed
2015-09-17 12:24 hokomoko Relationship added has duplicate 0004917
+Issue History