Sorry to take us back a bit, but I missed a direct question and it would be rude not to answer it...
sprulish wrote:Gary have you had similar issues and are you suggesting that installing a fresh new copy may help with these issues?
No, the only issue I've had is one I went looking for--when corroborating the "diamond/slip crossing" issue when using the 64bit world editor.
Yes to the question about a new instance of Steam/TS--that's the only way you can be sure of running a 100% up to date copy of the game, without the complication of any old files. Testing with just default content also rules out the possibility of a 3rd party or edited file being a factor--going back to earlier versions of the game and the 'it will fall over once 3GB of RAM is used' reports illustrates the effect of a single dodgy .bin file--I could (probably still can) cause the game to crash with RAM usage under 1GB by having a purposely crippled .bin file installed--simply the removal of
any single < character.
If a clean, default copy works without problems then adding your goodies a bit at a time and testing would show if one of the extras introduced the problem. To use Derek's car analogy comment from earlier...
One wouldnt buy for example a brand new car and then be told " if we have missed something when building your car then fix it yourself but let us know how you fixed it afterwards so we can fix any future ones we build"....would they ??
by testing, and deciding that the game is bust and it's DTG's fault, with all your additional stock in place is like taking that car back to the garage and complaining that it doesn't work right after you've stiffened the suspension; changed the exhaust for a sports one; re-mapped the engine; uprated the brakes...... DTG aren't asking us to trouble-shoot every issue we find, and many could be issues that are due to any changes in the shared components of the game rather than being specific to the 64bit iteration, but to simply report those issues--they can't fix anything until they can replicate it.
Moving back to where we are now we find that the issue with the scenario we're dealing with is a
one time instance of a Microsoft Windows error message generated when running a Just Trains produced scenario on a Just Trains produced route....yeah, definitely one for DTG
