Modifying an existing level: Difference between revisions

m
no edit summary
m (In fact this is not simpler :))
mNo edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
Instead of [[Creating a level|creating a new level]], you may simply want to export, modify and re-import an existing level.
Instead of [[Creating a level|creating a new level]], you may want to export, modify and re-import an existing level.


==Export of static geometry==
==Export of static geometry==
Line 74: Line 74:


;Scene import
;Scene import
According to Neo that feature is still under development. RIP.
According to Neo that feature was under development. RIP.


==Recycle object lists==
==Recycle object lists==
Line 95: Line 95:
==OBJC and vertex coloring==
==OBJC and vertex coloring==
* Object (XML) import via <Object> tag (master XML file) will get you objects without any vertex coloring. (OniSplit will pick *.oni class files from the shared folder.)
* Object (XML) import via <Object> tag (master XML file) will get you objects without any vertex coloring. (OniSplit will pick *.oni class files from the shared folder.)
* Object (DAE) import via <Model> tag (master SML file) should get you objects with vertex coloring, but no BSL functions. In that case you must add the corresponding OBJC files by hand.
* Object (DAE) import via <Model> tag (master XML file) should get you objects with vertex coloring, but no BSL functions. In that case you must add the corresponding OBJC files by hand.


You can choose between these two methods for consoles, triggers, turrets and furniture without particles. Doors and furniture ''with'' particles always require the XML method.
You can choose between these two methods for consoles, triggers, turrets and furniture without particles. Doors and furniture ''with'' particles always require the XML method.
8,521

edits