Trial and error fault finding
Posted: Mon Aug 19, 2013 1:34 pm
Having fun trying to sort out a big problem with my Railworks installation. Got the "not a serialised binary" error when loading quite a few routes. Deleted local content and reinstalled, and still not working. Decided it must be something third party causing a problem. I've got so much third party stuff though that I didn't want to delete totally and start again, especially having to go through loading and testing each bit individually to figure out the problem. Reinstalling all the mods that change default content is bad enough (AP packs etc).
Figured out though that I could play post 2012 routes (e.g London to Brighton, London to Faversham), but not earlier ones (or ones that hadn't been updated since 2012). Came to the conclusion that it must be the Kuju folder at fault, so renamed and verified cache, and low and behold, everything works. I've now backed up my working Kuju folder, and in the process of reinstalling all the mods and checking to see which one is causing the problem (clearly something that modifies the Kuju folder).
Figured out though that I could play post 2012 routes (e.g London to Brighton, London to Faversham), but not earlier ones (or ones that hadn't been updated since 2012). Came to the conclusion that it must be the Kuju folder at fault, so renamed and verified cache, and low and behold, everything works. I've now backed up my working Kuju folder, and in the process of reinstalling all the mods and checking to see which one is causing the problem (clearly something that modifies the Kuju folder).