Talk:Modifying an existing level: Difference between revisions

m
mNo edit summary
 
Line 215: Line 215:
** 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.
** By the way, DAE files - which are internally XML - contain tags for the authoring tool and version. Therefore, these files may also differ at the byte level.
** By the way, DAE files - which are internally XML - contain tags for the authoring tool and version. Therefore, these files may also differ at the byte level.
<?xml version="1.0" encoding="utf-8"?>
<COLLADA xmlns="http://www.collada.org/2005/11/COLLADASchema" version="1.4.1">
    <asset>
        <contributor>
            <authoring_tool>Softimage|XSI Mod Tool version 7.5.203.0</authoring_tool>
        </contributor>
        [...]
* After all obvious bugs have been fixed with help of roundtripping, unit testing could be done to catch smaller mismatches and bugs. Eventually, ingame testing would be done.
* After all obvious bugs have been fixed with help of roundtripping, unit testing could be done to catch smaller mismatches and bugs. Eventually, ingame testing would be done.


8,982

edits