TRS04 Fatal Error Problems

[Paddington]

The last time I had problems with Fatal Errors I decided to upgrade my PC but stick with 2004.

Things settled down but now the Fatal Error has returned. Could someone enlighten me as to what is happening please?

The attached pic (when I can work out how to attach one) shows the fault error as it came up. The discussions on Forums would direct me to think that it came up because of a v.recent download.

I had saved a back up so nothing was lost apart from my patience, but I removed the suspect loco and tender and re booted things OK. I had been running DirectX, so I tried Open GL, but the same "Error" came up but with some different numbers.

I then went to a Test Track layout that I use and inserted the suspect loco on that.....and it rebooted and ran on that layout OK!

So where to from here?

The original layout to which the loco was being added has been added to with scenery and roads etc. as one does, so have I reached a "saturation point" ? Is this Fatal Error the only danger signal. How can I prove it?

I am using a ATI Radeon HD 2900XT card with 512MB memory. I can provide other details if necesary.

Thanks

 

[Paddington]

Looks like I cannot file attachments!

HELP !!!!

 

[Euphod]

There are several theories about the fatal error syndrome. Most seem to indicate a bad piece of content, usually with a script that isn't agreeing with Trainz. 2004 had some problems with scripting, but other causes could be a memory leak, heat, or a bad stick of RAM.

 

[Paddington]

Thanks Euphod for replying.

The bad scripting you mention I presume would have also have shown up when the same loco was placed and run OK on the Test Track, right?

 

[Euphod]

Thanks Euphod for replying.

The bad scripting you mention I presume would have also have shown up when the same loco was placed and run OK on the Test Track, right?

Well, you could assume that, but I'm guessing it may depend on whether or not the loco was in a position to have to use the script. Perhaps on a test track that is unsignaled or has no industries attached it will not display an error, but if you mix it up with other scripted items, there may be a conflict.

 

[Paddington]

Thanks again for the ongoing advice.

However, the Test Track in this case included signalling, two crossover (Diamonds actually) Control Commands a double track loop and 2 branches and 3 trains.

 

[jost62]

Hi Paddington,

perhaps http://forums.auran.com/trainz/showthread.php?t=39214 may help you?
What I observed and what was confirmed by others: There exist "Killing Items" that seem to work perfectly as long you are in a session. But when you close the session and open it later again, then you get a fatal error during the loading process - you can never open the session again (unless you know the killing item and delete it in your download-folder).
If I understood correctly you placed the suspect loco and tender on a new layout, closed it and reloaded this new layout successfully? In my understanding this means that the loco and tender is not the problem. If your problem is as described (No problem while building and saving, but fatal error while reloading), then it could be another item. In my case it was just a nice little house/shed that nearly killed my beloved layout.
Good luck!

 

[Paddington]

Hi jost62
Have not looked at the thread that you referred to as yet, but I see that there are a few threads about these sorts of problem. May I clarify the situation.

I went into Surveyor and placed a loco and tender which I had downloaded from DLS by FTP. I had checked the loco and tender for correct dependencies using TrainzObjects.

I saved the modified Session and then tried to open the same in Driver. It would not boot up.

I then tried to open the same Session in Surveyor, but it would not boot up.

I then deleted that Session.

I then went into Surveyor and opened a different Session (called Test Track) and loaded the same loco and tender, saved the Session, and backed out. I then opened this Session in Driver OK and the loco and tender ran.

I have presumed from this that the fault is not in the downloaded loco and tender, but in the Session to which I was trying to add it!

Any further comments?

 

[jost62]

Yes, that sounds similar to the fatal error I had. The fault is not in the downloaded loco and tender, but in one or more other item(s) in the Session to which you added it! Did you add other items before you added the loco? As I said (and you will find the kuid in the thread I pointed you to) in my case the killer was a nice little shed.

 

[Paddington]

Have looked at the threads and taken the point that the fault may be in another item!

Believe that the addition of the loco and tender were done on a separate occasion without other items being added etc.. but will check again with the downloads and changes again.

I should have mentioned before that the loco and tender in question are:-

GWR Castle Defiant kuid 116296:1930:2
GWR Castle tender kuid 116296:60029:2

Thanks

 

[Paddington]

Have spent time today with a technical TRAINZ person who reviewed the problem and proceeded to remove the items added to the session prior to the loco being added. He also checked all the parts of the loco and tender to ensure that there wasn't anything out of place.

We could not find anything peculiar apart from a few oversized photos and one or two mis-titled items, but when all was put back the same problem occurred. We even tried just the loco or tender on their own, but both conditions would not open either in Surveyor or Driver.

We even tried adding different locos and tenders to the layout in place of the supposed faulty one, and they worked OK. It seems that this particular Castle loco and tender are not compatible with this layout!!

 

[johnwhelan]

The last time I had problems with Fatal Errors I decided to upgrade my PC but stick with 2004.

Things settled down but now the Fatal Error has returned. Could someone enlighten me as to what is happening please?

The attached pic (when I can work out how to attach one) shows the fault error as it came up. The discussions on Forums would direct me to think that it came up because of a v.recent download.

I had saved a back up so nothing was lost apart from my patience, but I removed the suspect loco and tender and re booted things OK. I had been running DirectX, so I tried Open GL, but the same "Error" came up but with some different numbers.

I then went to a Test Track layout that I use and inserted the suspect loco on that.....and it rebooted and ran on that layout OK!

So where to from here?

The original layout to which the loco was being added has been added to with scenery and roads etc. as one does, so have I reached a "saturation point" ? Is this Fatal Error the only danger signal. How can I prove it?

I am using a ATI Radeon HD 2900XT card with 512MB memory. I can provide other details if necesary.

Thanks

TRS2004 does not protect against two scripts writing or reading from the same bit of memory. Individual items on a clean install run fine. TC3 has much better protection, TRS2009 is even better.

Trying to resolve these is extremely difficult which is why these days if you find this sort of problem with my items in TRS2004 my solution is please upgrade to a more robust version. My TRS2004 items will work on a clean install with nothing other than the default content and even that may not be true depending on your video card drivers etc.

Cheerio John