TheDorkProject on 13/2/2013 at 19:18
I'm wondering if this patch will work with the System Shock 2 version from GOG.com to be released 15 hours from now.
Can anyone attest to whether it works on the GOG.com Thief games?
voodoo47 on 13/2/2013 at 20:01
yes, it works for both thief games, and for SS2 as well, see Tafferpatcher, TFix and SS2tool respectively. there is a 99% chance that SS2tool will work out of the box for the gog release of SS2, if not, I'm pretty sure a compatible version will be released within hours.
Fafhrd on 14/2/2013 at 19:26
Apparently the GoG version is already at 2.4. So either Night Dive were the secret benefactors who created the patch, or they decided to say 'fuck it' and risk the legal consequences of releasing it through GoG with the patch already applied.
M1Account on 10/3/2013 at 06:41
I've searched for this and have found basically no info on it.
The changelist in the ttlg thread contains the following line:
Quote:
- Added "Blocks frobs" property, allowing objects to block frobs of objects behind them (e.g. to stop frobbing items through safe doors)
In SHOCK\doc\new_config_vars.txt , there is an entry regarding that as follows:
I believe this feature is preventing me from using a particular speed running strategy, in which certain things are frobbed through a wall immediately after quickloading.
The entry continues:
Quote:
frob line of sight mode, default is 0. This allows enabling of a more strict obstruction check for a potential
frob target, to prevent frobbing through walls scenarios. That does however mean that sometimes objects which
are only partially visible won't be frobbable, like an object on a shelf (made of terrain polys) above head
height, unless you jump or climb onto something, or an object around a corner that's only partially visible.
Use at your own risk, it could potentially break missions that placed "hidden" frobbable objects in such way
that the player can never see more than a small fraction.
Modes: 0 = standard (only objects marked as blocking will obstruct)
1 = all terrain and objects marked as blocking will obstruct
2 = (Shock only) like mode 1 but prevents HUD brackets/info to appear on obstructed objects, unlike
mode 1 where the brackets/info will appear the same way as they do in mode 0, even if the object
can't actually be interacted with. For Shock this mode is recommended over 1 because it's less
confusing. (In Thief this mode is the same as 1.)
I'm not sure exactly what the wording here means. Does it mean that when set to 0, things work exactly as in the original game? Or that there is still a slight difference? Because even when set to 0 (when entered into cam_ext.cfg in the SHOCK folder), I experience a slight difference from what I used to, and from what I've observed in other players' cases. Does anyone know how to disable this feature entirely? It's necessary for speed running, but I don't want to give up all the other benefits of NewDark if I don't have to.
Solar on 20/3/2013 at 01:27
It's been ages, years probably, since I last posted on the boards, but I have to give a major kudos to the author of these patches.
Not only did it let me reinstall Thief 1, 2 and System Shock 2 again, but gave me the motivation to work on my 3D modeling again. A while back, I was remaking Thief 1 and 2's as well as System Shock 2 models (not NPC or creature meshes, just objects.. I suck at characters, lol), and gave up when Windows formated the wrong drive and deleted most my work, including a butt-load of Sonic the Hedgehog models, lol =/
Anyway, I reinstalled 3DSM and plan on giving it a try again, starting with SS2, since I still have most of my previous work. If I do make any progress, I'll post a release on the boards.
Solar on 21/3/2013 at 02:19
Ah, thank you. I had that bookmarked, but forgot all about it
Nameless Voice on 25/3/2013 at 00:14
Quote Posted by Solar
and gave up when Windows formated the wrong drive and deleted most my work, including a butt-load of Sonic the Hedgehog models, lol =/
Any particular reason why you didn't just unformat / recover the drive, if it wasn't actually defective?
Solar on 26/3/2013 at 16:07
Quote Posted by Nameless Voice
Any particular reason why you didn't just unformat / recover the drive, if it wasn't actually defective?
Most of the data was gone. I recovered a few music files and random images, sadly stuff I had backed up and didn't care about. But everything that hadn't yet been backed up, was not recoverable
MrTrip on 24/4/2013 at 19:14
Hey icemann, did we ever finish that second Ancient map or did you finish it by yourself? :P looks like a good time to get back into making FMs....
