Midwest Grain 2.0 crashes

My TRAINZ is crashing on the newly downloaded JR route Midwest Grain & Terminal (2.0) at the same spot each time: Heading south from the northern end of the route, just as the loco passes the very first grade crossing, it crashes. Anybody else have that problem? I am running a JR GP 40 CSX loco and 5-6 Evans hoppers. What gives?
Also, what are the "Road Name Overides" at the grade crossings? I have never seen them before. There is a "switch" there also with a relay box connected. I have no idea what that setup is doing. I actually modified another version of the route and replaced the grade crossing setup with a simpler version, but it still crashes at the exact same point.

Thanks.
 
Last edited:
Hi Connel.

As in crashing do you mean with an error, or is this a derail?

I've run the route and I have merged the route into a creation of my own with no problems at all in that section.

John
 
I get a big note that states: Trainz has encountered an error and has shutdown...do you want to send an error report...and everything shuts down. (Been away for a few days)

Thanks.
 
Is it at a particular amount of time (same or very similar each time) after you start the session? If so, check your graphics settings.

Shane
 
Connel

I have exactly the same problem. I purchased the content expansion for V 2.0 to show my support for JR and all the free things I have downloaded. Running the "Return to Freedom" session using all AI causes a program crash just after the caboose passes the first crossing. I tries changing from windowed DirectX which is my normal mode to full screen Open GL and got exactly the same result. Running just looking at the mini-map, the consist gets well beyond this point but if I try to click on the problem consist the program immediately crashes.

Must be something in the Route itself if you are running a different session with the same results. I didn't find the route all that exciting so I have just ignored the problem and wrote it off as a donation to JR.

Glenn

edit: I decided to give it one more test. I started the problem consist going using AI and then switched to the other AI driver coming from the south. I left it running with no problems for 5 minutes and then switched back to the other consist. It had got past the first intersection and has been running fine. There must be something funny with the ATLS at the first intersection which only is triggered when the focus is actually on the consist crossing the intersection.
 
Last edited:
Okay. I had nothing else to do today and I must enjoy hitting my head against a brick wall. I don't understand why this works (another day perhaps) but there are two problems.

1. There is an ATLS controller set to channel 99 (use findobject). It should be set to 999 since all the rest of the assets at this junction are set this way. Make sure to also change the name of the asset or it won't be saved properly with the route info.
2. Delete the Searchlight Signal D-HP just before the first road junction.

These both need to be done to get the consist through the first intersection. In the "Return to Freedom" session the next problem is a driverless consist ahead which needs to be moved.

Did they ever test this session before its release??

edit: Signal needs updated JR Smart Signal Library V 1.65 which wasn't included with dependencies.

- Glenn
 
Last edited:
Okay. I had nothing else to do today and I must enjoy hitting my head against a brick wall. I don't understand why this works (another day perhaps) but there are two problems.

1. There is an ATLS controller set to channel 99 (use findobject). It should be set to 999 since all the rest of the assets at this junction are set this way. Make sure to also change the name of the asset or it won't be saved properly with the route info.
2. Delete the Searchlight Signal D-HP just before the first road junction.

These both need to be done to get the consist through the first intersection. In the "Return to Freedom" session the next problem is a driverless consist ahead which needs to be moved.

Did they ever test this session before its release??

edit: Signal needs updated JR Smart Signal Library V 1.65 which wasn't included with dependencies.

- Glenn

well, when they publish a fix, version 2.1 of the route, then I will worry, not going to lose any sleep over one little thing... BUT, thank you for detailing this problem's root cause.
 
As I recall with the first release of MWG there was game crashes happening and not always in the same place for everyone, but it was because of not having the latest Signal library. I have run all sessions from the first release and the latest 2.0 versions with no problems. From past experience the miss channeled Atlas controller should not cause any game crashes and is really just a little miner thing as it will also not effect the session other than the crossing will just not work. As far as the "Return to Freedom" session the only driverless consist I can find is the one on the Cargill Balloon track which is nowhere in the way and the tank train in the same area with no driver commands is not in the way as well. I am quite sure several members of the JR team tested these sessions and of cores they worked fine with the exception of the overlooked controller which is easy enough to be missed.
 
As I recall with the first release of MWG there was game crashes happening and not always in the same place for everyone, but it was because of not having the latest Signal library. I have run all sessions from the first release and the latest 2.0 versions with no problems. From past experience the miss channeled Atlas controller should not cause any game crashes and is really just a little miner thing as it will also not effect the session other than the crossing will just not work. As far as the "Return to Freedom" session the only driverless consist I can find is the one on the Cargill Balloon track which is nowhere in the way and the tank train in the same area with no driver commands is not in the way as well. I am quite sure several members of the JR team tested these sessions and of cores they worked fine with the exception of the overlooked controller which is easy enough to be missed.

I was just trying to recoup some of the $30 I had invested in purchasing the content package which included the sessions. I am a newbie without your past experience and I expected that someone at JR would have tried downloading the payware onto a "clean" copy of TS12 to make sure it would work and that no updated libraries were missing.

The driverless consist was MY bad! I had accidentally left it there earlier when I was using my cloned copy to try to figure out what was going wrong.

I think JR provides a great service to the Trainz community providing quality freeware - I just feel they should handle their Payware a bit differently.
 
To be fair to JR, their libraries change frequently so it would not be feasible to re-compile every single piece of payware they have to accommodate that kind of change. Bear in mind that they also distribute some their content via Simulator Central as well.

Shane

P.S. Why is this thread not in the Jointed Rail section in the first place?
 
Thanks for everyone's comments and help. I went back to JR website and downloaded the Signal FX and that seemed to cure the problem ! I have run several trains at various speeds thru the suspect area and no problems. I do have a few questions, however: What are "signal offsets" and what do they do? What are "Road name overides" and what do they do? I am in the process of ditching all the grade crossings and triggers on the route and simplifying all that stuff. I do NOT run automobile traffic on any routes because it looks and runs like crap, so I don't need traffic stoppers and such. I just want to know what that other stuff does, so as not to mess up something I know nothing about.

Thanks, again, for all the help.
 
Back
Top