2022-06-29 03:25 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0005142Spring engineGeneralpublic2016-03-06 23:02
Reportersilentwings 
Assigned ToKloot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionno change required 
Product Version101.0 
Target VersionFixed in Version 
Summary0005142: gl.UnitShape stops the engine from drawing its buildqueue
DescriptionIf you use gl.UnitShape to draw a unit, near where the same unit should also be drawn as part of the engines buildqueue visualization, it will cause the engine to not draw its own queued version of the unit.
Steps To ReproduceRun bar:test, give a builder order to a unit, and then also give the some queued move overs. As each new move order is given, the queued building appears (drawn in gui_commands_fx with gl.UnitShape) and fades away until it vanishes (at which point gl.UnitShape stops being called), and only then does the engine suddenly starts to draw its own version of the queued building.

If you edit http://imolarpg.dyndns.org/trac/balatest/browser/branches/BAR/luaui/widgets/gui_commands_fx.lua?rev=5062#L466, and move the position at which gl.UnitShape draws, say to Z+100,Y,Z+100, then when gl.UnitShape is called the engine always continune drawing its own version of the buildqueue.

Correct behaviour: The engine should continue to draw its owned queued building, regardless of whether gl.UnitShape is being used or not. (If a game dev wants, they can/should disable the engine drawing of build queues using cmdcolors.)

TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0015991

Kloot (developer)

Last edited: 2016-03-06 23:02

View 2 revisions

you are drawing with depth-masking *enabled* in the same place as where the engine wants to draw, which prevents it from doing so.

+Notes

-Issue History
Date Modified Username Field Change
2016-03-06 22:20 silentwings New Issue
2016-03-06 23:02 Kloot Note Added: 0015991
2016-03-06 23:02 Kloot Note Edited: 0015991 View Revisions
2016-03-06 23:02 Kloot Status new => closed
2016-03-06 23:02 Kloot Assigned To => Kloot
2016-03-06 23:02 Kloot Resolution open => no change required
+Issue History