Problematic Asset Warning - affects the NSE Clocks (read thread for details)

[shaneturner12]

Hi Trainzers,

After reading another thread, it has come to my attention that I need to warn users of (a) potential problematic asset(s)

The asset(s) in question are the NSE Clocks, which I believe are by Bloodnok.

These assets have a fault that may not be reported by Content Manager, as it is triggered by the script inside the asset.

The fault relates to the World.PlaySound function referencing an attachment point (a.sound) that does not exist, or is corrupted.

The symptoms can range from no sound being produced by the clocks (where there should be), to stuttering sound.

There is also the chance of a sharp framerate drop, potentially to less than 1FPS.

Can users of these assets who are experiencing these symptoms try removing them and seeing if that fixes the issue.

Please note that not all users may be affected, as I know the issue affects TS2009 and TS2010 users, but am not sure about TS12 users.

Shane

 

[clam1952]

Shane the OP in the other thread was using TS12.

 

[shaneturner12]

Hi Malc,

I did realise that but the problem will affect users from TS2009 onwards.

Shane

 

[rastis]

G'day! :wave:

I have no problem with the NSE Clock. I get none of the above experiences. I'm running TS12.

Cheers!

Jake.

 

[shaneturner12]

Hi rastis,

Do you get any errors in your Jetlog.txt file related to either a.sound or a garbled name?

Shane

 

[Deano5]

I have those clocks in many routes and have not had a problem with them in any version of Trainz, that I'm aware of.
I'll have to go and double check now just to see. :wave:

 

[shaneturner12]

I'm interested in the results of your check, as I know that it only affects some users.

Shane

 

[p-dehnert]

I have checked both clocks in TS2010 (clocks downloaded from DLS) and TS12 (clocks builtin), and I couldn't find any problems. All clocks had the correct attachment points (checked with PEV's Mesh Text Viewer and a hexeditor). There were no error messages in the jetlog.txt . Peter

 

[shaneturner12]

Thankyou for your response. I have a feeling there's an element of asset corruption going on somewhere.

Shane

 

[clam1952]

I have checked both clocks in TS2010 (clocks downloaded from DLS) and TS12 (clocks builtin), and I couldn't find any problems. All clocks had the correct attachment points (checked with PEV's Mesh Text Viewer and a hexeditor). There were no error messages in the jetlog.txt . Peter

Done pretty much the same here as well on 2010 and TS12 and all seems ok, no problems with stuttering either in 2009 2010 or TS12, has to be another factor involved, as I said in the original thread, maybe something else using the same script or a modified one or different a completely different one with the same name perhaps? Can Trainz handle two scripts with the same name at once?

 

[shaneturner12]

There is another possible piece of the puzzle - the Clock Rule (<kuid2:62310:30041:1>)

Supposedly, this rule enables use of the animated clocks (the NSE clock being one of them)

Shane

 

[NickieFoenshauge]

I think you can leave the Clock Rule out of the equation, Shane. The NSE clock works fine without it. And adding the Clock Rule doesn't change anything.
A corrupted mesh is a more likely candidate, since a missing attachment point 'a.sound' seems to be at the heart of the problem.

 

[shaneturner12]

I think you're right there. Based on previous experiences, it's always been a corrupt mesh when I've used it.

Shane

 

[wgibson]

I was having terrible sound stuttering in TS12 as a phenomenon that crept in month or so ago. Tonight, I disabled the NSE Clocks. The sound problem went away but the framerate is still terrible. If you open the NSE Clock in Content Creator, the files are automatically updated to TS12 and then you have a whole slew of faults pop up.