Faulty asset question. (FIXED)

[Tumble Trash᠌ ⁧⁧ Official]

I have several assets and they work, my father has the same ones, yet his say faulty? I think it might be corrupted files due to a crash. Any ideas on how to fix?
Had to delete some coupler files that were conflicting with ones in use.

[Tumble Trash᠌ ⁧⁧ Official]

Originally posted by wolfpredator:

Your theory would be spot on! If the internet connection was or hand been interrupted chances are the files has become corrupted during installation

Probably the best solution to fix this would be to delete the faulty assets in Content Manager, navigate to your Trainz data folder, the default location is

C:\Users\%username%\AppData\Local\N3V Games\trs22 then open the Build xxxxxxxxx folder, open cache \ open internet delete all those files

If nothing is fixed after the above step, try! Remember to delete the Cache \ Internet files again*

Delete this file from the cache folder

assets.bku

Delete these files from the Build xxxxxxxxxxx folder

asset-cache.tdx
assets.tdx

WARNING: Deleting the above files will log you out of Trainz, meaning you will need to sign into Trainz again and any custom settings will also be reset

Please let the database rebuild before clicking on "Start Trainz"

You may also need to delete and re-download some assets that was not previously faulty or missing dependencies has suddenly become faulty or has missing dependencies.. Not sure why this is an issue after rebuilding the database, it can be annoying at times.. What I do is load the game check the sessions first, then locomotives, then rolling stock, then consists and finally routes "I always keep a note of the routes that's already missing assets" but overall, the routes still works, as for any locos or rolling stock that appears faulty or missing dependencies, these will never work unless we can fix them either by re-downloading them or reverting to original and a basic database rebuild

I hope at least one of the solutions I've provided above helps out
Best of luck

Forgot to update here, turn out, there were some old couplers that had been installed at some point that was conflicting with the ones that were needed. Deleting these files fixed the issue.

[wolfpredator]

Excellent!