Trainz Plus Beta Update 104016 (PC) and 104021 (Mac)

It happens with all rolling stock from "RGW Class 21S - D&RG Class 145" pack from Trainz Forge. It didn't occur in 103369 and prior builds, so something has changed in 104016.

After further investigation: only this particular rolling stock is concerned, on any route. Why in 104016 and not before?

Quite possibly we fixed a bug these items were relying on to work correctly.

To look into it further for these assets we'd need someone to send in a .cdp with all the required dependencies so we can investigate.
 
This sounds like an issue I reported and then discovered why it was happening. Check that there isn't a value of around 100 for mesh-table-lod-transition-distances, it either needs to be blank or over the lowest lod distance in metres if used with lm.txt. If I'm right deleting the value and leaving it blank should stop this happening.

[FONT=arial, sans-serif]Hi[/FONT] clam1952 - Quick [FONT=arial, sans-serif]Dev follow-up on the LOD issue was "The use of mesh-table-lod-transition-distances and lm.txt together is fine, but the value of 100 is way too short for a train. It should be set to the maximum draw distance at which the train is meaningfully visible (when in line-of-sight), so something above whatever the highest visible LOD is in the lm file."[/FONT][COLOR=rgba(0,0,0,0.9)][FONT=&quot]
[/FONT][/COLOR]
 
Last edited:
we'd need someone to send in a .cdp with all the required dependencies so we can investigate.

They are payware (author is trainboi1).

I just noticed that "Preview Asset" doesn't work (blank) for all of them.
 
Last edited:
This sounds like an issue I reported and then discovered why it was happening. Check that there isn't a value of around 100 for mesh-table-lod-transition-distances, it either needs to be blank or over the lowest lod distance in metres if used with lm.txt. If I'm right deleting the value and leaving it blank should stop this happening.

Thanks! You pointed me in the right direction: all the rolling stock had "mesh-table-lod-transition-distances" tags set to 100. Leaving them blank did the trick.
 
They are payware (author is trainboi1).

I just noticed that "Preview Asset" doesn't work (blank) for all of them.

That's the same problem then. https://forums.auran.com/trainz/sho...6-(PC)-and-104021-(Mac)&p=1776190#post1776190

Ed (edh6) is uploading fixed versions of his assets.
Is due to a misunderstanding of how to use the new tag in conjunction with lm.txt. Needs the creator or user to fix the configs. The error appears to be in previous versions that included the tag not working as it should have.
 
• Yesterday: no "Faulty" assets, then I made a full backup.
• Today: four are suddenly "Faulty" from nowhere (<kuid2:97008:2948412:1>,<kuid2:97008:30044:2>,<kuid2:97008:2948413:1>,<kuid2:97008:2948411:1>) with the same error: "VE179: The kuid '<kuid2:97008:2948409:1>' specified in 'icon3' is not of the correct type". The update of <kuid2:97008:2948409:1> to version 2 doesn't fix the issue. If I start with yesterday's backup (in which they weren't "Faulty"), they still are.

This game starts becoming tiring...
 
• Yesterday: no "Faulty" assets, then I made a full backup.
• Today: four are suddenly "Faulty" from nowhere (<kuid2:97008:2948412:1>,<kuid2:97008:30044:2>,<kuid2:97008:2948413:1>,<kuid2:97008:2948411:1>) with the same error: "VE179: The kuid '<kuid2:97008:2948409:1>' specified in 'icon3' is not of the correct type". The update of <kuid2:97008:2948409:1> to version 2 doesn't fix the issue. If I start with yesterday's backup (in which they weren't "Faulty"), they still are.

This game starts becoming tiring...

This is a reported issue that Windwalkr said will become a warning for end-users, however, it is a real problem that needs to be addressed by the content creators.

This is why this is still in BETA, meaning testing so people like you can report problems and the problems can be repaired.
 
But how to explain that yesterday those assets had no issue, and today they turn faulty as if by magic?
 
I have pointed this out in my earlier post below but got no answer. leave <kuid2:97008:2948409:1> Shed Vanderfield open for edit and they will appear.

<kuid2:97008:2948409:1> Shed Vanderfield built in. This asset obsoletes an icon kuid. <kuid2:97008:60064:1> Trailer-A-Linfox plus others use that kuid number for an icon in its config so flags up as faulty. I think the icon is W2 <kuid2:97008:29081948:2> which is also built in.

}
}
icon3 <kuid2:97008:29081948:1>

obsolete-table
{
icon3 <kuid2:97008:29081948:1>
}

thumbnails
{
 
Last edited:
Weird, same faulty assets here, seeing W2 mentioned, it had an update <kuid:-25:1310> W2 icon. So on the off chance it had something to do with the problem I deleted it, no change other than a couple of additional faulty items, re-installed it, no faulty assets at all, go figure.
 
Last edited:
<kuid2:97008:2948409:1> Shed Vanderfield has also been updated and the obsolete table removed. This has now put a lot of assets back to working again.
 
But how to explain that yesterday those assets had no issue, and today they turn faulty as if by magic?
>>
Possibly a database repair occurred which revalidates the items.

Please remember that there are over half a million different assets, spanning almost 20 years of content creation and we're talking about a handful that are affected.

We don't set out to make items faulty. We fix bugs and optimise things for better performance and sometimes some items are affected. Often the item has never worked as expected by a creator.

We generally try to find a workaround so the asset loads without errors.

Thanks for your help in identifying issues with problems.
 
Cabin controls seem to be a bit wonky in cab mode. Tested with my PB15 Cabin and the F7 one on the DLS and none of the controls seem to function when the cursor is hovered over them.
 
Cabin controls seem to be a bit wonky in cab mode. Tested with my PB15 Cabin and the F7 one on the DLS and none of the controls seem to function when the cursor is hovered over them.

Totally agree. Tried with several different locos placed in Kickstarter as a new session. Mouse control of throttle, brakes etc. was possible but the mouse had to be moved far from the handles to get the mouse-over graphics. Works fine in 104017 but not in 104016 using all the same hardware and settings.

Glenn
 
...and today 14 new "Faulty" assets, all with the VE179 error:

<kuid2:101046:103530:2> Pullman 4 window Bi-Level Coach Amtrak DES
<kuid:101046:103932> Pullman 4 window Bi-Level Coach RI DES
<kuid2:56063:185063:3> 4baycflowhopperNorfolkSouthern292092_ant
<kuid2:56063:185064:3> 4baycflowhopperNorfolkSouthern292066_ant
<kuid2:60238:8086:1> Hot Air Balloon Startup
<kuid:203554:100138> Modern Cars Mod 1
<kuid:203554:100139> Modern Cars Mod 2
<kuid:203554:100140> Modern Cars Mod 3
<kuid:203554:100141> Modern Cars Mod 4
<kuid:203554:100142> Modern Cars Mod 5
<kuid:203554:100143> Modern Cars Mod 6
<kuid:203554:100144> Modern Cars Mod 7
<kuid:203554:100145> Modern Cars Mod 8
<kuid2:359354:104074:1> Pullman 4 window Bi-Level Coach SP standard commuter two tone gray
 
Totally agree. Tried with several different locos placed in Kickstarter as a new session. Mouse control of throttle, brakes etc. was possible but the mouse had to be moved far from the handles to get the mouse-over graphics. Works fine in 104017 but not in 104016 using all the same hardware and settings.

Glenn

I have this problem also. I can't open the windows in the cab, when I am close to the windows, the pointer displays and I can move the cursor around and get the brakes and throttle and horn.
 
...and today 14 new "Faulty" assets, all with the VE179 error:

<kuid2:101046:103530:2> Pullman 4 window Bi-Level Coach Amtrak DES
<kuid:101046:103932> Pullman 4 window Bi-Level Coach RI DES
<kuid2:56063:185063:3> 4baycflowhopperNorfolkSouthern292092_ant
<kuid2:56063:185064:3> 4baycflowhopperNorfolkSouthern292066_ant
<kuid2:60238:8086:1> Hot Air Balloon Startup
<kuid:203554:100138> Modern Cars Mod 1
<kuid:203554:100139> Modern Cars Mod 2
<kuid:203554:100140> Modern Cars Mod 3
<kuid:203554:100141> Modern Cars Mod 4
<kuid:203554:100142> Modern Cars Mod 5
<kuid:203554:100143> Modern Cars Mod 6
<kuid:203554:100144> Modern Cars Mod 7
<kuid:203554:100145> Modern Cars Mod 8
<kuid2:359354:104074:1> Pullman 4 window Bi-Level Coach SP standard commuter two tone gray

the Modern Cars mod issue struck me yesterday as well. Why after weeks of being OK do things become faulty?
 
Again this is odd, Modern cars not showing as faulty here however running errors and warnings gives errors.

Example:
Code:
; <kuid:203554:100138> Validating <kuid:203554:100138>
- <kuid:203554:100138> VE179: The kuid '<kuid2:68787:1696:1>' specified in 'default-mesh' is not of the correct type.
- <kuid:203554:100138> VE179: The kuid '<kuid2:68787:1696:1>' specified in 'default-mesh' is not of the correct type.
- <kuid:203554:100138> VE179: The kuid '<kuid2:68787:1252:1>' specified in 'default-mesh' is not of the correct type.
- <kuid:203554:100138> VE179: The kuid '<kuid2:68787:1674:1>' specified in 'default-mesh' is not of the correct type.
- <kuid:203554:100138> VE179: The kuid '<kuid2:68787:1696:1>' specified in 'default-mesh' is not of the correct type.

Remains not faulty though, looking at dependencies we have:

<kuid2:68787:100339:1> HP_US_Car_08_scenery - building
<kuid2:68787:1674:1> HP_US_Car_07 - building
<kuid2:68787:100346:1> HP_US_Car_15_scenery - track object
<kuid2:68787:1696:1> HP_US_Car_21 - track object
<kuid2:68787:1252:1> HP_US_Car_01 - track object

Which probably isn't helping.
 
In addition: 14 new "faulties" today, but the ones that were yesterday are fine now! How long will they stay so...
 
Back
Top