by Chacal » Fri Dec 21, 2012 12:11 pm
I will reply tonight with my specs.
I have been getting the issue while modifying cloned scenarios for the Colton Northern route.
Here is what I did:
- in RW Tools, I cloned each default C N scenario, swapping rolling stock.
- in RW scenario editor, opened each cloned scenario, making a few changes in the timetable view, saved, closed timetable view, clicked on the "play" icon, exited, repeated.
This went well for the first 6 scenarios, then at the 7th it took 2 minutes to save the scenario. At the 8th it took 5 minutes. At the 9th I lost patience and killed the process,
Then when I tried to play the scenario I had the "malformed xml" error. I deleted the 9th scenario and had the same error. I deleted all my cloned scenarios and still had the error. I looked at a few cloned scenarios and they had only 3 or 4 empty provider nodes.
So this behavior is pretty much what everyone described in forums already, except that it seemed to start after some time and get worse and worse, leading me to suspect a kind of memory leak. Also, it is consistent with what Mike Simpson posted on trainsim.com: he suspects the problem is caused by the rw scenario editor, but compounded by serz.exe, which gets confused by the xml error and starts looping.
Over the hill and gathering speed