Can you top this TRS22 Patch ?

K

K3JohnHO

Member
Updating from TRS22 112411 (No errors, No Warnings) to 123794 (10 errors, 390 Warnings)

10 - Failed to download precached data for package 'sc491....

+ page after page of 'present in multiple locations' messages.

+ page after page of 'Checking for faulty assets'.
'Skipping validations as asset is locally obsolete'.

196 seconds elapsed.

I could forgive, well almost, an 'Upgrade' introducing problems, but a 'Patch' should correct problems, not introduce them.

You 'Patch' a hole in a boat but you 'Upgrade' it by replacing the engine with a better one or by adding features etc.

Please add your experience to the thread. Thanks, K3JohnHO.
 
This is not unusual. That patch causes problems probably due to specific conditions in the patched program. N3V has moved on.
I have the 123794 version and no issues. But getting there depends on what the poorly written patch sees in the update process.

Perhaps N3V should validate the to-be patched software BEFORE applying a patch. But that has no cost/benefit that can be seen - so patch and pray.
 
Last edited:
I was considering patching from build 119451 TRS22 Sp1 to Sp 3 Build 123794. The whole process from my observations from various forum posts have left me somewhat dubious. A patch should fix not make worse a program. The benefits do not seem to be worth the effort. Perhaps another patch? Oh woe....:rolleyes:
 
K3JohnHO said:
Updating from TRS22 112411 (No errors, No Warnings) to 123794 (10 errors, 390 Warnings)

10 - Failed to download precached data for package 'sc491....
Click to expand...
This means they patched some DLC packages and the program will rebuild the cache the first time you start TRS22.
K3JohnHO said:
+ page after page of 'present in multiple locations' messages.
Click to expand...
This means the same asset is used in multiple DLC packages. Not a problem.
K3JohnHO said:
+ page after page of 'Checking for faulty assets'.
'Skipping validations as asset is locally obsolete'.
Click to expand...
This is just the Database Repair that the patch runs automatically and means you have both new and old versions of some assets. You can delete most items labeled as obsolete in Content Manager. It saves disk space.
K3JohnHO said:
196 seconds elapsed.

I could forgive, well almost, an 'Upgrade' introducing problems, but a 'Patch' should correct problems, not introduce them.
Click to expand...
N3V patches do both upgrades of content and bug fixes. Would you prefer a patch that ran with no feedback?
K3JohnHO said:
You 'Patch' a hole in a boat but you 'Upgrade' it by replacing the engine with a better one or by adding features etc.

Please add your experience to the thread. Thanks, K3JohnHO.
Click to expand...
 
You can ignore the precache errors. According to Tony Hilliam, the owner and president of N3V, this has to do with the package-version being a higher version than what the server thinks they are supposed to be.
 
wreeder said:
This means they patched some DLC packages and the program will rebuild the cache the first time you start TRS22.

This means the same asset is used in multiple DLC packages. Not a problem.

This is just the Database Repair that the patch runs automatically and means you have both new and old versions of some assets. You can delete most items labeled as obsolete in Content Manager. It saves disk space.

N3V patches do both upgrades of content and bug fixes. Would you prefer a patch that ran with no feedback?
Click to expand...
Thank you @wreeder and @JCitron for your explanations of the meanings behind the various messages during patches & upgrades! :) I found that very useful. I haven't found a similar explanation on the Trainz Wiki (yet). I think it might be a good addition to the https://online.ts2009.com/mediaWiki/index.php/HowTo/Fix_Errors_and_Warnings page if it isn't already captured. If you know or think of a better place for the info in the Wiki please let me know.

NOTE: I won't use Mr. Hillman's name since I feel it needs to be vetted in writing by the N3V Legal office or Public Affairs office. I'm not doubting the validity of the pre-cache errors statement but the adage of "trust but verify" and not wanting to appear to be speaking on the behalf of N3V and its employees gives me strong pause towards attributing statements to people or entities.
 
You must log in or register to reply here.
Back
Top