Tree SagoPalm 01) How to Fix It From Being Faulty?

[SparkedGMD]

<kuid2:523:19723095:1> Tree SagoPalm 01 is built-in to T:ANE. Not sure why it is not in the newer versions, but I exported it to CDP and imported it into TRS19.
<kuid:581273:102018> by daylightrain was not findable. Even Frank_Dean said he could not find it. I think I scanned the route in Surveyor looking for an orange wireframe, and if I found it I either put down a substitute that looked good or just hit "Delete Missing Assets". Maybe Daylightran knows what/where it is.

(<kuid2:523:19723095:1> Tree SagoPalm 01) How to Fix It From Being Faulty?

Cuz i tried fixing it accordingly and it didn't work

 

[HPL]

You didn't mention what version of Trainz you are using. It is "Packaged" (from "TANE - Additional Assets") and isn't "Faulty" in Trainz Plus.

 

[JCitron]

Did you try Revert to original in Content Manager?

Right-click on the faulty asset.
Choose Revert to original.

Hopefully, this will fix your problem; it usually does.

 

[SparkedGMD]

You didn't mention what version of Trainz you are using. It is "Packaged" (from "TANE - Additional Assets") and isn't "Faulty" in Trainz Plus.

Im Using TRS22

 

[SparkedGMD]

Did you try Revert to original in Content Manager?

Right-click on the faulty asset.
Choose Revert to original.

Hopefully, this will fix your problem; it usually does.

I tried it did nothing

 

[Dinorius_Redundicus]

(<kuid2:523:19723095:1> Tree SagoPalm 01) How to Fix It From Being Faulty?

If the fault messages refer to missing texture files, it's probably because you opened the Built-in asset for editing. Merely opening such an asset leaves it in a state with its .texture files exposed and they are not suitable for submitting into CM.

Even if you make no edits, re-submitting the asset in that form now triggers faults like this;

The faults arise because CM expects textures being submitted to be in the form of image files (eg. TGA, PNG, BMP, etc.) paired with corresponding .texture.txt files.

The trainz utility PEV Images2TGA can extract the required .TGA images and texture.txt files from each .texture file. The result of applying Images2TGA to the sago palm asset is shown below. The asset can now be submitted back into CM and it should no longer trigger VE65 faults.

Note that while Images2TGA does not delete the original .texture files, they are actually no longer needed or used. CM combines the pairs of TGA and .texture.txt files into new .texture files.