Changes between Version 1 and Version 3 of Ticket #1411


Ignore:
Timestamp:
Jun 8, 2013, 2:13:12 PM (11 years ago)
Author:
Kareem Ergawy
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1411

    • Property Keywords review patch added
    • Property Milestone Backlog → Alpha 14

  • Ticket #1411 – Description

    v1 v3  
    1 Some entities should only be visible in Atlas for the aid of map designers, in game they should be invisible. For example, [source:/ps/trunk/binaries/data/mods/public/simulation/templates/special/territory_pull.xml territory pull] and [source:/ps/trunk/binaries/data/mods/public/simulation/templates/special/territory_block.xml block] entities, or some types of ambient emitters (proposed in #1962). Probably this could be done with a flag in the visual actor component, which would check the flag and `g_AtlasGameLoop->running` or something before submitting the model for rendering.
     1[PATCH] Some entities should only be visible in Atlas for the aid of map designers, in game they should be invisible. For example, [source:/ps/trunk/binaries/data/mods/public/simulation/templates/special/territory_pull.xml territory pull] and [source:/ps/trunk/binaries/data/mods/public/simulation/templates/special/territory_block.xml block] entities, or some types of ambient emitters (proposed in #1962). Probably this could be done with a flag in the visual actor component, which would check the flag and `g_AtlasGameLoop->running` or something before submitting the model for rendering.
    22
    33Not sure if they should be hidden in the Atlas simulation test, but for simplicity all Atlas cases could be treated the same.