Problems with Nexusdj's class 323 trains

shaneturner12

Tutorial Creator
Is anyone aware of a problem with nexusdj's class 323 trains that causes fatal errors?

I am having a problem when in an area with multiple trains (can be as low as 2) where one is a class 323 (I have a friend with the same problem) - I can reproduce the fatal error on request.

The item(s) in question are the 323202 DMSO and PTSO LM Lively. (not sure if it is relevant, but I am using the 'Class 323 Enginesounds' engine sound, not the default one.

What really baffles me is that they were working fine for a while then the problems started. (I have even had problems with them with the payware Class 170 trains)

Unfortunately, I cannot re-download them due to the Skodatrainz closure (they are not on the DLS although other 323 models).

Further information is available on request (I am just getting my system specs together, and will post on a seperate post on this thread).

Unfortunately, I need to use these trains due to the route I am building requiring them for realism - it's a UK route including a very basic version of the Cross-City line (until nexusdj releases the class 350s at least)

I apologise if I have posted this in the wrong place etc.

Shane
 
Because of the time it is taking to get the info required, here is the basic spec:

Acer Aspire 5542 system
4GB RAM (3.75GB available)
AMD Athlon II 2.0Ghz X2 M300 (dual core)
ATI Radeon HD 4200 Graphics (256MB dedicated mem., up to 1919MB shared mem. - Hypermemory)

250GB HDD
DVD multi drive
DirectX 9.0C
ATI/Realtek High Definition sound card
 
Can you be more specific about the error :

First off what version of trainz are you using ?

Have you altered the config file in anyway ?

Is the fault happening when the unit is next to certain trains or all trains ?
 
Trainz Version: TRS2006 build 3099 (SP1)

Edits: Only changed enginesound to <kuid:402672:1398> (BR Class 323 enginesounds)

Happens: mostly with class 390 trains (I think they are made by jivebunny)(pantograph?) but can happen at any time - I even had it happen with a class 170 Turbostar (snowsignal version).

This may be related or unrelated but I have had previous graphics issues with the 323s (and jivebunnys 390s, but that is a different problem) where carriages with pantographs do not always appear.

The problem only happens in Driver.

Error code ends in 'FC' (If you need the full error code I can get it from jetlog.txt)

If you need any further information, let me know.

Shane

EDIT: Error code is @005F8B6C (from jetlog.txt - this is the fatal error code)

I have replicated the error: http://shaneturner12.awardspace.co.uk/fatal test for 323.cdp (contains 2 323 trains and a class 390 train) - the link to download it (the class 390) is somewhere on this forum (If I can find it, I will post it here)
 
Last edited:
Sorry to seem persistent, but are there any possible solutions or any ideas of what is causing the problem with the class 323s?

Shane
 
Not sure , I've not had any other reported problems with the LM 323 (there are a few screenshots on here from other users of the unit) .

If your also having problems with the 390 then you need to have a look if there are any files that both trains share . Have you altered any of the 390 config files ?

Try changing the config file back to the original sounds that I had used to see if that cures the problem .If not try altering the pantograph config entry to use strings original :Kuid:84860:57221 .

Have you downloaded any of the other 323's off the DLS , Do you get the same problems with these ?
 
OK, I will try the suggestions given (sorry if I am a nuisance)

The Class 390 trains are using their original config files.

Can you send me the kuid for the original engine sounds for the 323 in LM lively? I seem to have lost the original (backup) config files.

I will let you know how I get on (my friend also has the same problem, I will get him to try the suggestions as well).

I have only been able to test the 323 LM trains although my friend also has the Centro lively trains - I will get him to test them for me.

Shane

EDIT: The problem appears to have been fixed (only had to change the pantograph as per your suggestion - the enginesound edit was innocent) - just waiting to hear back from my friend on whether his problem is solved. If so, it is the pantograph that is at fault.

(Just checked in CMP, the affected pantograph seems to be in use across all the 323 trains)

I am very thankful if it stays error-free

Just out of interest, have you got anywhere with the Class 350 trains (London Midland)?
 
Last edited:
The 323 trains are on the DLS - AFAIK users are not allowed to send .CDPs of assets unless it's their own asset(s).

Also, it's best to start a new thread rather than digging up old ones.

Shane
 
Back
Top