Talk:Modifying an existing level: Difference between revisions

Talk:Modifying an existing level (view source)

Revision as of 14:25, 6 April 2026

1,476 bytes added , Monday at 14:25

m

no edit summary

Paradox-01

8,914

edits

@@ Line 106: / Line 106: @@
 If this is also possible, there is no more reason left why Blender should not become the community’s editor.
-==Revive demo level alpha helix==
+==Reviving demo level Alpha Helix?==
+===History===
+When you work on a level, you need to constantly test it ingame so possible errors are caught as early as possible. For that reason the tool around Helix had a plugin-based workflow. An AE package takes much longer to install and the AEI doesn't start Oni automatically.
+To not confuse novice modders with two different workflows, the new Helix should be package-based. The advantage would be that the package structure is ready from first second and interdependencies can better be dealt with during level development.
+===Dev notes===
+====Scaling====
+Round-tripping the old helix through Blender caused an upscaling.
+Old code:
+ <unit meter="0.1" name="decimetre"></unit>
+ <up_axis>Y_UP</up_axis>
+New code:
+ <unit name="meter" meter="1"/>
+ <up_axis>Z_UP</up_axis>
+The scaling can be reverted to normal by setting meter value.
+New code:
+ <unit name="meter" meter="0.1"/>
+====Up axis====
+A different up axis matters for character development. For levels, it was not yet testet.
+====Gunk flag textures====
+Based on previous tests, collision boxes seem to need an exception rule in the master file.
+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.