Hello, greetings from Czechia. I want to ask, if there are any limitations for serz.exe, regarding the size of processed .xml file? After merging of some routes I have a large Tracks.xml file (around 500 MB). After conversion with serz I only get a 1 kB Tracks.bin file with “SERZ…” inside. And have you ever tried any other convertor from .xml to .bin? Thank you!
There's no limitation to my knowledge. Serializing is a pretty simple process, a bit similar to Run-Length Encoding / Tokenising. If you end up with an empty bin, that is due to an accidentally deleted bracket in the xml (<,>). This makes the file invalid. Make sure the xml is valid and every tag/node is correctly closed. <Node>data</Node> or <EmptyNode/> For example this will lead to a corrupt bin, closing bracket deleted, in that case the rest is considered as data and Serz.exe will read all the rest of the file until it finds </Node> to close the data structure which is not there, therefore encoding fails. <Node>data/Node> It happened to me too . I've even once found a .bin in a JustTrains route that would lead to an infinite xml upon unserzing, filling up all my storage, which I could stop with Ctrl+C. You can check an xml here directly. https://www.xmlvalidation.com/ I'd recommend not using TSTools, as its editor is very limited. Better to use Notepad++ which allows folding and unfolding nodes, and checking structure. Gary, TSTools does the same in the background. Serz.exe [file] to a temp folder that is then displayed in the editor. You can't edit a .bin directly as it must be reencoded. Just like hex editing a zip file will result in garbage.
