8,981
edits
Talk:Modifying an existing level: Difference between revisions
Talk:Modifying an existing level (view source)
Revision as of 21:00, 18 April 2026
, Yesterday at 21:00no edit summary
Paradox-01 (talk | contribs) mNo edit summary |
Paradox-01 (talk | contribs) mNo edit summary |
||
| Line 144: | Line 144: | ||
====Scaling==== | ====Scaling==== | ||
Roundtripping the old helix through Blender caused an upscaling. | |||
Old code: | Old code: | ||
| Line 211: | Line 211: | ||
=====Roundtripping===== | =====Roundtripping===== | ||
* On a general note: | * On a general note: Roundtripping data is a very effective method to detect observable differences and actual bugs. | ||
* More specifically: Descriptor IDs, such as in <code><TRAC id="6787"></code>, are not preserved because ONI files use ''local'' IDs and are later repacked during DAT creation. Therefore, IDs in XML/ONI are typically reset to 0. | * More specifically: Descriptor IDs, such as in <code><TRAC id="6787"></code>, are not preserved because ONI files use ''local'' IDs and are later repacked during DAT creation. Therefore, IDs in XML/ONI are typically reset to 0. | ||
** Therefore, you can define hash parity of output files as a general goal, with the exception that differences can be ignored if they are caused only by non-semantic ID changes. In other words: you may consider semantic equivalence under normalized comparison as sufficient. | ** Therefore, you can define hash parity of output files as a general goal, with the exception that differences can be ignored if they are caused only by non-semantic ID changes. In other words: you may consider semantic equivalence under normalized comparison as sufficient. | ||