ATSF SD45 Glitched

Spookasaurus

New member
I”m having an issue where I can’t use the base in game Atsf Sd45. Every dependency is installed and isn’t faulty or broken, but I’m not able to see or use the loco. Not sure what caused this or how exactly to fix it.
 
Which ATSF SD45? There is a gazillion of them made by many content-creators. If you provide the KUID number, this would make it easier for us. You can find this information in Content Manager.
 
Which ATSF SD45? There is a gazillion of them made by many content-creators. If you provide the KUID number, this would make it easier for us. You can find this information in Content Manager.
He's talking about the built in JR one.
 
He's talking about the built in JR one.
It doesn't matter. He still should provide the kuid regardless.

If this is the built-in one, then he needs to check the Content Store for updates. There were a bunch of updated routes and sessions recently. Initially, I only downloaded a few of them and ended up missing dependencies myself. I didn't check to see what, except for what was on my own routes. I then checked again for more updates because these were all packaged. Sure enough, there were a few more to download and after that, the missing dependencies disappeared.
 
It doesn't matter. He still should provide the kuid regardless.

If this is the built-in one, then he needs to check the Content Store for updates. There were a bunch of updated routes and sessions recently. Initially, I only downloaded a few of them and ended up missing dependencies myself. I didn't check to see what, except for what was on my own routes. I then checked again for more updates because these were all packaged. Sure enough, there were a few more to download and after that, the missing dependencies disappeared.
It is the built in Yellowbonnet (kuid2:45324:100140:2), and I’ve figured out that it’s the cab shell that’s faulty (kuid2:45324:91102:2), and the asset isn’t supported in the build.
 
I have a TS19 too, have not had any updates in the last six months and also have no problems with the built-in: <kuid2:45324:100140:2> ATSF SD45

Dependenses too:

 
Since this is a built-in asset. Right-click on the faulty cab. Choose revert to original and that should fix that. If not, run a database repair.
 
Since this is a built-in asset. Right-click on the faulty cab. Choose revert to original and that should fix that. If not, run a database repair.
So I got the asset back to functional and so I went to look at the locomotive in the collection screen, and it shows untextured ground? I’m not sure exactly why this specific loco is giving me such a problem, everything else is working perfectly.
 
If the locomotive is working fine, then it's okay. The untextured ground may have something to do with the data loading up.
 
So I got the asset back to functional and so I went to look at the locomotive in the collection screen, and it shows untextured ground? I’m not sure exactly why this specific loco is giving me such a problem, everything else is working perfectly.
Relative to untextured ground:
Look in the launcher where the installation folder is located: Launcher - Settings - Installation.
Delete all the contents of the cache folder located in the installation folder. You can leave one file performance.conf to save the graphics settings.
And run a database repair again.
 
Relative to untextured ground:
Look in the launcher where the installation folder is located: Launcher - Settings - Installation.
Delete all the contents of the cache folder located in the installation folder. You can leave one file performance.conf to save the graphics settings.
And run a database repair again.
Which file is the installation folder?
 
Got rid of the files and went back in to look and see if it fixed anything, and Im still seeing this when I go to view it.
https://ibb.co/VgFkSy1
Run a database repair.
Close Trainz if it's running.
Back at the Launcher or while in Content Manager, click on the Developer menu on the top and choose Repair database.

The process can take from a few minutes to a bit longer.

Once completed, open up Content Manager, if you closed it.
Change the filter to Faulty.
You do this by selecting Installed at the top and then choosing Faulty from the list.

If there are any red assets, select them all by clicking on one and then pressing CTRL+A at the same time.
With your assets selected, right-click on them and choose View Errors and Warnings.

You'll see a progress bar appear.

Once finished, close Content Manager and wait a minute.
Open up Content Manager and check the Faulty assets again. There should be nothing.

If there's nothing, start Trainz and see if that works.
 
Run a database repair.
Close Trainz if it's running.
Back at the Launcher or while in Content Manager, click on the Developer menu on the top and choose Repair database.

The process can take from a few minutes to a bit longer.

Once completed, open up Content Manager, if you closed it.
Change the filter to Faulty.
You do this by selecting Installed at the top and then choosing Faulty from the list.

If there are any red assets, select them all by clicking on one and then pressing CTRL+A at the same time.
With your assets selected, right-click on them and choose View Errors and Warnings.

You'll see a progress bar appear.

Once finished, close Content Manager and wait a minute.
Open up Content Manager and check the Faulty assets again. There should be nothing.

If there's nothing, start Trainz and see if that works.
So I ran an error and warning in the dependencies area and it’s missing texture files. Does it have to do with the effects library in any way?
 
I don't remember but the missing texture is why the asset doesn't load.

Highlight the asset.
Right-click
choose Rever to Original.

Being a built-in locomotive, it should revert back to normal doing this.
 
I don't remember but the missing texture is why the asset doesn't load.

Highlight the asset.
Right-click
choose Rever to Original.

Being a built-in locomotive, it should revert back to normal doing this.
So I got the asset to 0 errors and 0 warnings, and I tried previewing it to see if it works, and the window immediately closed.
 
Back
Top