-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Sometimes cubemap box's absmin and absmax are incorrectly written into %mapname%_cubemaps.txt file.
They are written as if the origin is zero vector.
The reason of this happening is the way how the cubemap_box entity is tied into.
To reproduce the issue:
--- create a bound box brush of the cubemap
--- create origin brush
--- select the bounds brush first, then select the origin brush (the order is important!)
--- tie to entity
To create the cubemap without the issue, origin brush must be selected first, then the bounds brush is selected, then tying to entity.
Possible reason for the issue:
It seems as if the brushes of an entity are being processed in the exact order as when they were selected prior to tying to entity. When the cubemap brush is being processed, and the bounds (absmin/absmax) are created, the origin brush was not processed yet so it creates local bounds.
On the other note, such thing never happens to cubemaps without origin brush.