NEC Route Crashing frequently...

[ktain.ny]

Some of you may recall the TS12 built-in, 'NEC Wilmington-Philadelphia'. A fantastic route. And great for operating electric commuter equipment.

I found a reupload on the DLS, and installed in onto my copy of Trs19. For some reason, after getting a train out of the 30th St. Station area and onto the mainline, and up to speed, Trainz crashes to the desktop.

I've really never had a consistent problem with this game as far as crashing goes, never in TS12, or T:ANE. I have the newest SP and I'm about to update my drivers to see if that solves the issue.

If someone else wants to maybe give it a go and see if they experience the same phenomenon, you definitely should.

 

[JCitron]

This sounds like you have a faulty asset or have faulty assets somewhere in the vicinity.

What's happening is the asset will pass the fault-checking in Content Manager but is mangled internally in some fashion. There could be a corrupted texture or a mesh that causes the program to crash when the asset comes into view. The problem is which one is causing this. Is it something you already had installed, or is it a dependency for the route you downloaded?

I ran into this on a route I had many years ago in TS12. The route would drive fine until I reached a particular spot and looked left out of the cab. At that point, I was instantly looking at the desktop without warning. If I looked right, I could bypass that place with lots and lots of stutters meaning I got something like 3 fps until I passed that point.

Being a forested route, I suspected it was a tree that had a faulty mesh or texture that was causing this, but which one? The problem is I couldn't even look at that area in Surveyor without getting zapped quickly to the desktop! At that point, I was ready to give up but was in luck because TANE was just coming out and I held off thinking it was a TS12 thing. I figured at the time I could just import the route into TANE and that would fix the problem not knowing that the old Speed Trees weren't compatible because that was before that lovely bombshell was dropped on us. Once TANE was ready and the Speed Trees had to be replaced, I went about the process of replacing a gazillion Pofig and Mcguirel trees. I worked through batches using picklists and bulk updates. As soon as I clicked on one of Mcguirel's Maple trees and placed it, it placed fine but disappeared suddenly and the route did a CTD. I lucked out in that I had just saved and only lost a few dozen tree replacements instead of a lot more. It took a couple of attempts to get around this, by placing the tree and looking away quickly so not to trigger the crash.

 

[Lewiscc65]

I have made a route that CTD in TRS19 Platinum build 116678. It crashes at different times and at different locations, so I am having a hard time finding out what is causing it. I loaded it into TRS22 build 116492 an no crashes. That really threw me for a loop. I do not have an older build of TRS19, so I do not know if it is the build or not. It may have something to do with being a + in TRS22 and not in TRS19.

 

[ktain.ny]

Thanks for the reply John,

I'm having a similar to Lewis. The route crashed maybe 5 minutes after leaving Wilmington, DE, and a 10 minutes after leaving Philadelphia, PA. Different areas I have no clue how I'd find the asset,

I almost want to just... install T:ANE, port everything in, and call it a day. Really disappointing, I love that route :/

 

[G.M.]

It's better not to give up but to find assets that are faulty or use many threads


if you go to the Launcher screen, /Developer\ tab
-do clear logs
-show logs and keep this open while playing a session
-if you have 2 monitors it can be dragged on another monitor
or you play the session not full screen and can see both, switch between


Play the session and check for items that spam a lot


Things that can use many resources, bring down a session:
-NSE clock (and other clocks that tic every second)
-Clicketyclack triggers
-complex crossings like ATLS etc.
-Any sound using asset (a weak spot in trainz)
-Portals if used many on big routes
-complex path finding scripts
-trains with too complex scripts with many threads
-over the top content without LODS, the moment it loads, Trainz gets a hickup


if you find an item that clearly spams, try to put it on a layer that can be turned off
turn the layer off and see if performance increases.


if base, built-in or DLC items are faulty report them at n3v
hope this helps

 

[ktain.ny]

Hey G.M.,

Thanks for the reply and suggestion. I'm going to load up my session for this route, open the log thing in my second monitor and post a screenshot of what comes out.

 

[JCitron]

Hey G.M.,

Thanks for the reply and suggestion. I'm going to load up my session for this route, open the log thing in my second monitor and post a screenshot of what comes out.

You can highlight the text, press CTRL+C and copy it then CTRL-V and paste it. It's easier to read and see than a screen shot.

 

[ktain.ny]

So... I may have fixed the problem.

I switched the compatibility mode from 'maximize compatibility' (default) to 'show errors on legacy calls', to see if any of the dependencies showed up as faulty in CM. None did, so I switched back to 'maximize compatibility'.

I booted up the route and decided to run through with the dev settings window open. I completed several runs from Philadelphia to Wilmington with no crashes. In freelook, I panned over the entire length of the route, the complete 30 miles, and didn't experience a single crash.

Maybe it's just one of those instances of this game being fussy. If I get another crash, I'll be back with the dev logs.

Thanks again for the help guys.