DO NOT patch 12 with the second patch

Status
Not open for further replies.
Wow ... thanks Ed for the heads-up!!!

Doesn't Auran test these things before releasing it to the public!?:eek:

Ishie
 
Euphod... many thanks... you have no doubt save
me untold hours of grief.

Although I do have a strick policy of backing up all
content before doing any kind of upgrade, this is a
saving grace.

Lucky me... I worked ( on Trainz) till 4 AM last
night so I over slept this morning, and missed the
update. Zec pulled it before I happened to see it.

Again... Thanks for the unknown problems.

AL
 
If there is a lesson to be learned from the above, DO NOT PATCH until you read other people's comments/issues/errors/praise or what have you of the new patch released. As some people have to have the latest patch there is.

I, from painful lessons learned in the past, will only patch/upgrade a version some time later after its release and ONLY IF there is an advantage to be gained from a new patch.

I know, it is easy to say all this AFTER an event happening but haven't we all been there BEFORE with patches in the past? That also begs the question, how is an uploaded new patch getting tested (if at all), just to see if that patch does what it promises to do?

If it ain't broke, why fix it?

VinnyBarb
 
If there is a lesson to be learned from the above, DO NOT PATCH until you read other people's comments/issues/errors/praise or what have you of the new patch released. As some people have to have the latest patch there is.


Yes, good policy, but somebody has to go first! I just consider this one as "taking one for team".:D

You are all welcome...:hehe:
 
If there is a lesson to be learned from the above, DO NOT PATCH until you read other people's comments/issues/errors/praise or what have you of the new patch released. As some people have to have the latest patch there is.

Actually, the lesson is to backup your trainz folder before you patch. Waiting for others to go first is no guarantee, thousands could go before you, but if you're the unlucky folk that has the bizarre hardware configuration that triggers a bug, you'll still be the first to have to reinstall.

If you backup your trainz folder before installing a patch - any patch - then you can quickly restore back to the old folder if something goes wrong, be it a faulty patch, something unique to your PC, or the power going out mid-patch (and no, a UPS isn't really a solution given that trainz SP/patch installs run for hours these days)
 
Actually Zec, this thread can be closed at any time now. I wouldn't want any confusion when the patched are re-introduced, and it seems to have served it's purpose for a few members anyway.

Thanks for your swift response earlier!
 
Last edited:
Status
Not open for further replies.
Back
Top