Red faults in newly updated Fireworks by Palanor?

D

Dinorius_Redundicus

kuid 68213
CM3.3 detects red faults in the latest updates to Palanor's 'fireworks' assets, e.g. <KUID2:118781:28019:3>, trainz-build 2.9.

The repeat-delay tag has only one value when Trainz expects 2 be specified. It's an easy fix to replace 0 with 0,0 but I'm puzzled at how this fault got past the DLS upload process? Is it a case of being OK for build 2.9 but not OK for 3.3? Even so, I thought the DLS automated tests would pick this up and not allow it through.
 
It's not a fault of the asset, it's a faulty error detection rule in ContentManager of TS10. The documentation (and other versions of Trainz) allow 1 or 2 values for repeat-delay.

Peter
 
I didn't know that Peter, thanks.

Do you know if CM also has faults in its fault-detection rules for the trackoffsets tag? For recent updates of a JJS bridge and a JJS tunnel, CM 3.3 complains that the trackoffsets tag should have 2 values, not 1. That makes no sense for single track assets such as these. What local fix removes the error notice but does not cripple the assets?
 
Last edited:
Dinorius_Redundicus said:
Do you know if CM also has faults in its fault-detection rules for the trackoffsets tag? For recent updates of a JJS bridge and a JJS tunnel, CM 3.3 complains that the trackoffsets tag should have 2 values, not 1. That makes no sense for single track assets such as these. What local fix removes the error notice but does not cripple the assets?
Click to expand...

I have been unable to find a fix for this. It also applies to multi-track assets that have more than 2 tracks, such as stations. Either the number of offsets is not 2, or if 2 are supplied then the number of offsets does not match the number of tracks.
 
Exactly. I also tried 2 identical values; 0.01,0.01 . While I got no errors in CM3.3, and the asset loaded in TS2010 Surveyor, there was no track attached.

Trainz is really messed up. As soon as you scratch more than 1cm below the surface, you start discovering all these anomalies that should have been patched.
 
I remember that conversation, but not the very last post. You are very smart to figure out that method. OK, so I have edited kind.txt and I will see now what it does.

It's still a local solution however. If I was to include 'falsely erroneous' assets in a layout and upload it, anyone else with CM3.3/TS2010 will still see those assets as faulty.
 
Last edited:
I just saw these and was getting ready to download them until reading this. Is it possible to repair it and upload to the DLS again?

Dave
 
You must log in or register to reply here.
Back
Top