Locoswap Producing Enormous Xml Files

Locoswap v 1.6.1.0 has suddenly started producing Temp xml files of over 2TB filling my disk in seconds. These are SDBcache files. There is a small bin file and an enormous xml file. Dont want to lose this very useful utility. Has anyone else seen this. Tried reinstalling it on a different drive

 

What were you trying to achieve in LocoSwap?

Looks like you have a corrupt scenario .bin file somewhere, perhaps the leftover of a faulty edit?

What does the SDBCache.bin in your install's Content folder look like?
My scenario database cache .bin is exactly the same size as the .bin in LocoSwap's temp folder. But then perhaps LocoSwap just copies it into its own temp directory?

There is a dedicated thread on LocoSwap, perhaps you will find your answer there?
https://forums.dovetailgames.com/threads/locoswap-tool.61882/

PS: have you tried opening your scenario database cache .bin in TS-Tools, or tried dropping it on Serz.exe to get the .xml with all your scenarios?

 

My SDB cache in sim is pretty small at 10,12Kb. Finding a corrupt scenario would be impossible, I had done a fair few edits lately

 

Wonder if I would be best to delete my main SDB cache and let it rebuild

 

Locoswap has the same problem as TS Tools.
It looks for loco/wagon files but it does not know if the loco/wagon it is replacing works ok.

We place a wagon on the track in the Editor and that's fine
If nothing appears we go checking to see if it has a geo fie or something else missing

When I installed an AP extra stock pack it placed bin files for stock I did not own.
TSTools said I had the wagon but I was missing a lot of files for it so nothing appeared

TSTools and LocoSwap don't know if the loco/wagon/unit has a fault or not

 

Having rebuilt SDB Cache in game the temp folder xml file in Locoswap seems to be holding at 237MB against SDBCache in main game of 11Mb

 

Are you directly comparing the indicated size of serialized .bin files with their source .xml files?

You can de-serialize the SDBCache.bin from the Content folder and get a complete and readable .xml file of 237 MB? Use Notepad ++ to check all tags are closed correctly.

 

OK thanks - at least it seems to have stopped filling my Hard Disk. I did go into a route where I had been working on scenarios replacing stock and deleted the bak files from each scenario. Not sure if that was connected. The SDBCache bin file is now same size in both places so encoraging and xml is down to 68Mb