(SOLVED) 100+ Engines Broken due to Computer Cleanup?

[Jim310]

Last night I had to clear a large number of files off my computer, including a couple files regarding Trainz that were just old KUID and config.txt files. Today when I hopped on Trainz to do some filming, I was horrified to find out that over two hundred of my locomotives and rolling stock had been broken in this file purge.

Many of these red-listed engines didn't even have any dependencies listed as missing, yet they were still listed as missing dependencies. Others were just straight-up faulty. Engines that did legitimately have a somehow-missing asset were restored with the redownload of said assets, but others continue to sit with no change. And because the engines have "missing dependencies," I can't dig into the errors and warnings to decipher the issue. I've tried modifying engines and reverting locos to original forms but, alas, no dice. In particular, my library of GEVOs and AC44s has been hit extremely hard. A total of 126 locomotives were listed as somehow missing dependencies, while simultaneously not missing any dependencies at all.

These aren't just engines I've reskinned or edited on my own, and all of these engines are from only a handful of users. Those who created the engine assets, or bases for the assets, are n8phu, shiotariattrainz, trainut, gliuk28 and davesnow. I am not blaming any of these users or asking what went wrong, because I frankly have no clue.

Any tips on what to do would be greatly appreciated. If possible, I want to refrain from deleting and redownloading these engines if possible.

 

[pware]

Any tips on what to do would be greatly appreciated.

In that situation my first option would be to run a Database Repair.

How did you delete the "old KUIDs" and "config.txt"files? I am guessing that you did not use Content Manager - in any case "config.txt" files are an integral part of installed assets and any that exist outside of Content Manager are just simply isolated text files and their deletion would have no effect on Trainz. Likewise the "old KUIDs" I am guessing were in the form of .cdp files and would also be outside of Content Manager so their deletion would also have no effect on Trainz.

 

[Jim310]

In that situation my first option would be to run a Database Repair.

How did you delete the "old KUIDs" and "config.txt"files? I am guessing that you did not use Content Manager - in any case "config.txt" files are an integral part of installed assets and any that exist outside of Content Manager are just simply isolated text files and their deletion would have no effect on Trainz. Likewise the "old KUIDs" I am guessing were in the form of .cdp files and would also be outside of Content Manager so their deletion would also have no effect on Trainz.

I didn't do anything within content manager. I simply used my Mac's "find large files" function and deleted what was there.

In that situation my first option would be to run a Database Repair.

How did you delete the "old KUIDs" and "config.txt"files? I am guessing that you did not use Content Manager - in any case "config.txt" files are an integral part of installed assets and any that exist outside of Content Manager are just simply isolated text files and their deletion would have no effect on Trainz. Likewise the "old KUIDs" I am guessing were in the form of .cdp files and would also be outside of Content Manager so their deletion would also have no effect on Trainz.

I found a fix. All of these assets had dependencies that were open for edit. Submitting or reverting edits of these dependencies fixed the issue.

 

[pware]

I simply used my Mac's "find large files" function and deleted what was there.

Ahh yes. The old "The computer told me to do it" method. Been there, done that myself many times in my earlier days. We all learn from those experiences.

 

[JCitron]

Ahh yes. The old "The computer told me to do it" method. Been there, done that myself many times in my earlier days. We all learn from those experiences.

Yup. I lost a completed music program ready to burn to CD. Each of the individual pieces was about 450 MB or larger even after cropping. It's good thing I had a backup of the individual pieces prior to making adjustments.