Unna Oertdottir on 25/3/2019 at 13:09
fortuni reported some issues in the FM (
http://thiefmissions.com/m/WaterArrowInTheFire) A Water Arrow In the Fire
Some blackjacked guards couldn't be frobbed (but not all of them). This happened in a clean installation with Bullet DromEd as fortuni told me.
I checked this and loaded the savegame in DromEd. Everything was okay. I was using ND 1.25, with Tafferpatcher and also ND 1.26 with T2fix to check it.
Then I installed T2 again, this time I applied the (
http://www.taffersparadise.co.uk/thieffiles/thief2-nd-v26-update.zip) NewDark.zip patch only.
Ups. Some guards couldn't be picked up this time and there's a big "missing" folder in DromEd, even metaproperties are missing. What happened? The FM doesn't have it's own gamesys.
Why doesn't this happen on a install with TP and T2fix?
I was trying something and copied dark.gam into the FM folder. Guess what? It's working correctly now.
voodoo47 on 25/3/2019 at 13:39
not going to check myself, but everything points at his install with manually applied ND being the 1.07/1.18 hybrid, and the FM probably only works with the 1.18 gamesys (both TP and T2Fix make sure it's installed). so yeah, no wonder he's having problems.
the moral of the story is that you should only be running a manual Dark install if you really, really know what you are doing. like, really really really.
Unna Oertdottir on 25/3/2019 at 14:00
What exactly do you mean by
?
Dates of gamesys, etc. I need informations.
And why is the gamesys working if I put it in the FM folder? Is this the hybrid factor?
I found out there's a
bad gamesys for this mission date 7/18/2000
good gamesys for this mission date 3/27/2000
the older one is better
voodoo47 on 25/3/2019 at 14:20
basically, a couple of 3rdparty groups re-released the game some time after the original release, usually as a bundle with TG and T3 on a dvd. unfortunately, they've messed up and didn't patch the T2 build properly, omitting a couple of files (the gamesys, all osms, and some crf updates as well). and somehow, this version ended up being distributed via steam and GOG - the GOG build has been fixed up with the latest update, but steam remains broken (and using oldDark). I've posted a (
https://drive.google.com/open?id=1CRMBxok2FEPhMNoXrezLVtF9ZFHu8KEY) small package earlier that has NewDark and all the missing patch files included, and can be used to fix the hybrid up into a fully working condition (not really necessary as T2Fix does the same thing when everything is unchecked, but hey, maybe some people are still on dial-up).
so anyone using a manually updated steam version (or GOG version until quite recently) is playing a broken, incomplete version of the game, and been doing so for
years. it's even possible that we now have some FMs that will not work properly with a fully patched install because they have been made on the hybrid. one could end up with psychosis trying to sort this out.
//yeah, the dates are messed up, the "older" file is actually the proper 1.18 version.
fortuni on 25/3/2019 at 14:36
Quote Posted by voodoo47
so anyone using a manually updated steam version (or GOG version until quite recently) is playing a broken, incomplete version of the game, and been doing so for
years.
I downloaded a clean copy of T2 from GOG on 26/02/19 and initially had patched it with the manual ND1.26 but a few days later Unna told me about Bullet Dromed which I then installed overwriting the manually patched 1.26, it was with this install that I had problems with frobbing the KO'd bodies.
I played this mission last year with an older d/l from GOG that was patched with tafferpatch and ND1.25 but has no problem then.
Today I used the same installer from GOG (26/02/19) to give me a fresh T2 install and patched that with Jax64's T2Fix and had no problems with frobbing KO'd bodies.
Could repatching Bullet Dromed over a manually installed ND 1.26 have caused this issue?
It's not a big deal if it only happens with this mission but has this oddity been reported with other missions?
Unna Oertdottir on 25/3/2019 at 14:41
My T2 version is sitting on HDD for 18 years now. I copy it whenever I need it. I has a "new" gamesys.
TP and T2fix are installing the "old" gamesys which is the correct one - for this mission. But why? I played hundreds of FMs with this gamesys. This looks like a special incident.
Unna Oertdottir on 25/3/2019 at 14:59
Quote Posted by fortuni
Could repatching Bullet Dromed over a manually installed ND 1.26 have caused this issue?
There's no gamesys in Bullet DromEd. You could copy the working installation (rename it) and apply Bullet DromEd again. Test the guards in the mission.
voodoo47 on 25/3/2019 at 15:34
I really have no time to be diving into this, but feel free to find out what exact combination has caused the problem. so I'll just point out the obvious - you shouldn't be running a hybrid install, it's just not a good idea no matter how you look at it. at the moment, if you have installed T2 via GOG Galaxy, or patched it up with TP or T2Fix, all the 1.18 files are installed properly, and you should be good to go. if you haven't, you probably are running the hybrid, unless you installed the game from the first release cds and used the original 1.07 -> 1.18 patch yourself.
fortuni on 25/3/2019 at 15:38
Quote Posted by Unna Oertdottir
There's no gamesys in Bullet DromEd. You could copy the working installation (rename it) and apply Bullet DromEd again. Test the guards in the mission.
Nope, guards still unfrobbable when reinstalling Bullet DromEd with gamesys included in install.
But patch with T2Fix and problem goes away, so that's our solution. :D
