Talk:Modifying an existing level: Difference between revisions

m
no edit summary
mNo edit summary
mNo edit summary
Line 133: Line 133:


====Gunk flag textures====
====Gunk flag textures====
Based on previous tests, collision boxes seem to need an exception rule in the master file.
=====Collision=====
'''COLLISION versus _marker_barrier'''


So, OFGA imports should result in uneditable proxies (changes in position and rotation allowed only) and then create exception rules. To surpass the limit of original OFGA, you either need to create a new object class as shared resource or incorporate it into the AKEV core geometry. For special texture treatment, you would still need an exception rule.
COLLISION is a material found in the '''shared resource collection'''. Based on previous tests, collision boxes seem to need an exception rule in the master file.
 
Onisplit's level export will output the material _marker_barrier. Its purpose is pretty much the same. But while COLLISION won't automatically gunk flag its geometry, <code>_marker_barrier</code> will automatically flag geometry with <code>Transparent TwoSided Invisible NoObjectCollision NoOcclusion</code>.
 
So, at some point, we could replace instances of COLLISION with _marker_barrier as a workaround: By that we avoid the necessity to write an exception rules into the level master xml for assigning gunk flags to collision.
 
'''Usage of OFGA'''
 
OFGA imports should result in '''uneditable proxies''' (changes in position and rotation allowed only) and then add exception rules so the object have no character collision.
 
To derive editable OFGA variants, we could create a new object class as shared resource or incorporate the new object into the AKEV core geometry. For special texture treatment, we would still need an exception rule.
 
The bigger idea is that every object with custom data gets treated appropriately automatically: Their features get added the the master xml or are optionally also used to build new OFGA resources.
8,914

edits