data repair

[Herlev]

Hi
how do you do - extended data repair -
in 2019
kind regards
herlev

 

[HPL]

Ctrl + DBR

 

[PhilChorusch01]

Ctrl + DBR

Exactly!

 

[PhilChorusch01]

Be warned when doing an advanced database repair.

Many things that were not faulty would suddenly become faulty in Content Manager! The only way of resolving this is by deleting the faulty asset or it's dependency that is reading faulty after the advanced database rebuild. Delete it and redownload it!

I just did an advanced database rebuild, took me around 4 or 5 hours to delete sudden faulty assets or it's dependencies.

 

[HPL]

Some (if not all) of those newly faulty assets are "dummy" faulties, i.e. if you click "View Errors and Warnings", there's nothing red. A simple DBR then sorts the issue.

 

[PhilChorusch01]

Some (if not all) of those newly faulty assets are "dummy" faulties, i.e. if you click "View Errors and Warnings", there's nothing red. A simple DBR then sorts the issue.

It will still show up with errors and warnings, I'm not 100% sure why. But After deleting them and redownloading the assets/dependencies they become normal again.
After a normal Database rebuild, it doesn't happen! Only with advanced database rebuild

 

[Forester1]

It does seem odd that an EDBR tags un-faulty items as faulty, because it doesn't actually appear to look at them. If you double-click to get the thumbnail/description or Open-Preview Asset, it looks at them and then decides they are OK. So, what does it see that triggers a faulty designation if it hasn't even checked them?

 

[PhilChorusch01]

It does seem odd that an EDBR tags un-faulty items as faulty, because it doesn't actually appear to look at them. If you double-click to get the thumbnail/description or Open-Preview Asset, it looks at them and then decides they are OK. So, what does it see that triggers a faulty designation if it hasn't even checked them?

If I only knew how to answer why assets that were not faulty suddenly become faulty after an advanced database rebuild, it's very strange! Could be a bug in the Steam version of TRS22PE? Not really sure, all I can say is that it's not hard to fix, so there's no real point contacting N3V Games and reporting the bug.

 

[HPL]

Could be a bug in the Steam version of TRS22PE?

Definitely no, as I am running non-Steam Trainz Plus and encounter this bug too.

 

[PhilChorusch01]

Definitely no, as I am running non-Steam Trainz Plus and encounter this bug too.

Thanks for the heads up! Maybe.. Or one can only hope the bug will get fixed.... Some day.

 

[stagecoach]

I think the DBR checks the local folder (with modifications to assets) in the data folder while EDBR checks against the original folder (unmodified assets).

 

[Forester1]

Perhaps. I am seeing the same issue in TRS19, so it is nothing new to 22.