Railworks America

Since using the 64bit version of TS2019, I regularly get the following error when editing scenarios, usually upon saving, sometimes when loading. Anyone else getting these? I looked at the typical dump and it says it is being sent to DTG for analysis.

I've only received this error once since using the 64bit version. The sim crashed while opening the 2D map in the route editor. The error has not reoccurred since the incident.

I get them too when I play the 64 bit version. They got so bad that I had to go back to the 32 bit version. I haven't a clue on what they mean, I just hope that DTG gets around to fixing it soon.

Brickrail782 wrote:I get them too when I play the 64 bit version. They got so bad that I had to go back to the 32 bit version. I haven't a clue on what they mean, I just hope that DTG gets around to fixing it soon.

Ahh......It might not be a DTG problem. I have never had this problem except after hitting the restart button about twenty times when doing repaints. Problem was much worse in the 32bit version.

I should clarify that I have not had the error in the middle of a route editing session; only in scenario editing, usually upon saving. I do 99% route editing, rarely scenario editing, so it is not currently a big deal to me, and I too hope that DTG will get around to looking at it.

gwgardner wrote:I should clarify that I have not had the error in the middle of a route editing session; only in scenario editing, usually upon saving. I do 99% route editing, rarely scenario editing, so it is not currently a big deal to me, and I too hope that DTG will get around to looking at it.

Just as a point on exactly when this happens do you usually save with the F2 key as you are going along? Also is it doing the save even though it crashes or are you losing the recent edit?

Your question made me reconsider my previous statement that I've not seen it with the route editor. I have a couple of times, and in each instance the save was completed. The error occured apparently immediately after the save.

With my latest attempt at scenario editing, the scenario was not saved prior to the ctd.

There's no pattern I can discern except that it almost always occurs upon saving. I don't use F2 much, as I've found it unreliable. I use the arrow key at the bottom right.

I got this three times today while Scenario editing. The first crash was when I saved via F2, exited, then did a Tools/Clear Cache/Restart....crash. When opening the same scenario to continue editing...crash. Restarted, then drove a Standard scenario on that map...no problem. Tried to edit the original scenario....crash. Deleted the crash files, Rebooted, deleted the scenario, started a new scenario, F2 saved, shutdown restarted, edited scenario - no problem, no crash, so, i’m Confused.....

Assuming they're getting lots of crash reports on this, surely they are/will be working on it. In the meantime, I'll keep on route editing.

[later]

There's a long thread on this problem at UKTrainsim. DTG is definitely looking at it. People getting the access violation in a variety of situations.