Jump to content

Talk:Modifying an existing level: Difference between revisions

m
no edit summary
mNo edit summary
mNo edit summary
Line 1: Line 1:
This community is the manifested pain of Herodotus...
==Idea==
==Idea==
To convert an extracted ONLV into a new project file you need even more in-depth knowledge about the file structure than for simply building a level project file from scratch.
To convert an extracted ONLV into a new project file you need even more in-depth knowledge about the file structure than for simply building a level project file from scratch.
Line 6: Line 8:
One-click operation:
One-click operation:
# Level extraction.
# Level extraction.
# Post-edit dae files to [[Importing_character_models#Troubleshooting|make them compatible with blender]]. The onisplit arg -blender seems to work for [[Importing_character_models#Blender-specific_OniSplit_commands|character import/export]] only.
# Conversion of ONLV into an actual project file.
# Conversion of ONLV into an actual project file.
# Recycling of physics and locklights.
# Recycling of physics and locklights.
Line 84: Line 87:
==Less write operations==
==Less write operations==
With each onload event the ONLV and ONLD would get extracted. To reduce somewhat the amount of write operations an xml cache file could be used to feed the program's overview table. If the DAT files are older then no new extractions are done.
With each onload event the ONLV and ONLD would get extracted. To reduce somewhat the amount of write operations an xml cache file could be used to feed the program's overview table. If the DAT files are older then no new extractions are done.
==Blender add-ons==
* [https://github.com/ekztal/Blender-v5-DAE-Importer-Add-on Blender-v5-DAE-Importer-Add-on] (broken but fixable)
* BetterCollada (untested)
8,914

edits