hello is alex23 still around?

[boomer_aus_00]

hi i've got a error that come up with the "SAR 500 Class #500" <kuid:193148:1435> now the errors are only warning:

Warning: This asset uses an obsolete trainz-build number. Trainz-build numbers below 2.7 are no longer supported.
Warning: Progressive meshes are no longer supported by Trainz. Though these meshes may work in Trainz, it is recommended that you switch to a LOD mesh.
Warning: Progressive meshes are no longer supported by Trainz. Though these meshes may work in Trainz, it is recommended that you switch to a LOD mesh.


but the thing is that when i do a EDR it comes up in the faulty & then i go to check the errors it goes back fine no problems no warnings or faults but when ya go to look again in cheack warnings thoese warning are still there & just wondering if you could update this to have no warning it might stop it from ending up in my faulty list after a EDR

 

[shaneturner12]

Warnings can be ignored, as they do not prevent the asset from working, unlike errors.

An EDR quite often causes false positives - there is nothing that can be done to prevent this.

Shane

 

[boomer_aus_00]

Well when i puting it on my layout the game crashers then ya got to wonder? i've also got another one that does it!!! it all works fine untill it get close to that content then boots me back in to the desktop not all the time but so far it's been twise & both times it been close by to this content take it off i don't have no problems i've wondering if it has hidden errors? the other one is the "NSWGR BCW Cattle Wagon".

 

[shaneturner12]

I would strongly suggest that you check your Jetlog file, as the issue is likely to be script related.

Shane

 

[boomer_aus_00]

& what am i look for i don't read script? to me what in it that file is only the build-in kuilds from TRS2010 when i 1st put them in & did the EDR after that it's nothing else in there what can understand of it anyways

 

[shaneturner12]

That may be part of the problem, as certain TS2010 built-in content is inherently faulty. You may want to keep a copy of that Jetlog though as the user you are after may want to see it.

Shane

 

[boomer_aus_00]

i'll copy it to back it up & then del all warning from the other one & see if it get anything else