Layout error at 47 minutes every time

Open your jetlog.txt file and see if there are any entries at 47 minutes that might help you determine what is causing it.

Bob
 
Hi ixion,
I had the same problem in my large TRS2004 layout, the fault turned out to be a piece of faulty content.
I had used a trackside whistle board that had a script to make the AI driver blow the horn/whistle when he came to it.
I deleted the faulty kuid, used the 'delete missing assets' option when surveyor complained, then no more crashing when running trains.
Hope this helps,
Lindsay
 
I've had bad assets do this as well as faulty hardware. My computer had a bad DIMM and would get cranky as the system got warm. This chip was never bothered by anything else. I found this when it finally died because I started getting memory faults on system startup.

John
 
Several years ago I had the same problem. Here is how I fixed it: First of all, you have to see on what you get the problem: If you have a map, and several sessions, do you have the problem on all of them? or on one session in particular. With this you separate the culprit from rolling stock to fixed assets (ie.-scenery items). If you have faulty scenery items, make a copy of the map, open it and start deleting one by one starting by the latest items you added. At some point the stoppage will cease. Then go to the main original map and delete the offending asset. If the problem is in a sesion, start deleting one by one pieces of rolling stock until everything works. I found that in one situation, it was not a piece, but the fact that it was in the wrong place or coupled to another. This sounds impossible or stupid, but deleting it and then slowly adding the same, may solve the error. Alternate: Make a copy of the sesion, add one loco and one car. Run it pass the 47 minutes, and if so, add slowly rolling stock until... well you know what I mean. This is just elemental trobleshooting, but takes time. Let us know how it goes
 
Back
Top