Hi,

Originally Posted by FrauBlake
Is it really necessary to disable V1 .lsx to binary compression (and vice versa) ?

Some might still want to use the tool for classic modding, because it's a necessity for more serious modding, and classic probably has tons more of old version files.

This check was a bit too restrictive for no reason; fixed to include V1 lsx files as well.
(Its original purpose was to detect future additions to the lsx file format to make sure that we serialize new formats properly)

Originally Posted by Katsuki
2) When converting from LSF -> LSX a header named Header.Unknown is not read (
when converting back LSX -> LSF replaces it as 0x200000 so it is lost in the process, the source file indicates a different number which I don't have a clue what it is, maybe a version number, in my case, it is 2104000C (553910284)).

Without this header, the meta.lsf will mark the savefile as 'incompatible', and globals.lsf will crash the loading.


This field was originally ignored because its value didn't have any effect (the game worked with every value just fine), and the original .lsx-es (where available) never contained this value, so I assumed that the game doesn't use it.
I've changed the lsx/lsf conversion process to automatically save & restore this value now.

Fixed version: https://s3.eu-central-1.amazonaws.com/nb-stor/dos/ExportTool-v1.7.2.zip