NewDark - Thief 2 V1.19 & System Shock 2 V2.4

The Few on 28/9/2012 at 14:32

Thief2.exe just crashes for me on start - nobody else seems to be having the problem? :confused: The game is the current Steam version.

Problem Event Name: APPCRASH
Application Name: thief2.exe
Application Version: 1.9.0.0
Application Timestamp: 505eed10
Fault Module Name: thief2.exe
Fault Module Version: 1.9.0.0
Fault Module Timestamp: 505eed10
Exception Code: c0000005
Exception Offset: 0028a248

Thanks for any hints!

Hiatus on 28/9/2012 at 14:36

Quote Posted by voodoo47

confirming. the readme states your Thief2 needs to be patched to 1.18, and the T2 demo is some special build, somewhere on the road between T1 and T2 if I remember correctly, so if the 1.18 is a requirement, then you (we) are out of luck.

Original exe for that demo is thf2demo.exe (2 479 616 bytes) and its version is "Thief 2 1.01 Alpha" (hit Alt-Shift-V while in-game or check in .exe properties), so this is an early T2 build (final shipped version was 1.07, and of course 1.18 in the official LGS patch), rather than T1 one (.exe size is somewhere in between T1/TG .exes and later (1.07-1.18) T2 .exes).

But it shouldn't matter as thf2demo.exe is not used anymore (can be deleted anyway) - Thief2.exe (1.19) is now run instead. Maybe it's Thief2.exe (1.19) incompatibility with Dark.gam or .osm files versions included in the demo (maybe even something in invluded .mis file itself)?

I'll try renaming Thief2.exe (1.19) to thf2demo.exe and see whether it helps (doubt it, though). Will report back.

If anyone manages to get T2 ~demo~ version ("Uninvited Guest") work with 1.19 patch, please let me know how (Now the game starts and loads mission ok, but all AIs in the level are frozen, and game crashes when frobbing crates etc - so it's unplayable in that state).

===

EDIT:

"I'll try renaming Thief2.exe (1.19) to thf2demo.exe and see whether it helps (doubt it, though). Will report back."

NOPE, it didn't work, as expected - AIs still frozen as before..

LarryG on 28/9/2012 at 14:54

Quote Posted by The Few

Instructions for Installation and Application of the 1.19 Patch Including DromEd:

Quote Posted by R Soul

After trying out the patch I wanted it in a clean install so I wouldn't have old config files from older things like ddfix. Here's what I did:
Installed Thief 2 to a new folder (c:\games\Thief2_119)
Extracted all of the files from Dromed.zip (from one of the T2 CDs, allowing it to overwrite everything)
Installed the Thief 2 1.18 patch (remember this updates mis files and other resources too)
Installed Dromed v1.18 (which was unnecessary because the new patch overwrites it, but never mind)

That's the default installation - no mods or unofficial patches.

edit: Next step: Installed the Dromed Toolkit (menus.cfg and .cmd files)

Then I extracted the contents of the new package, in this order:
new_dark.zip
contrib.zip
editor.zip

Because you have zips within a zip, make sure you extracted the contents of them, rather than the zip files themselves.

If you are still getting crashes, then post the diagnostic files that are written to your directory (such as Thief2.log and any crash dumps). With luck someone will be able to figure out your problem from those.

The Few on 28/9/2012 at 15:11

Ok, maybe I should have mentioned that I'm totally new to Thief modding (in contrast to everyone else here, it seems ;) ) - so do I need that DromEd stuff if I only want to play? I don't have the CDs anymore I'm afraid...

Next problem is: How to install a Steam game a second time to another directory? Re-install and simply copy the directory somewhere else? I'm no heavy Steam user, just took the chance when the trilogy was offered for 6 Euros, so I wouldn't have to dig for those old CDs. So I never tried a second install of a Steam game.

Also the Steam is pre-patched (DDfix) it seems - could that be the problem?

Thanks! :thumb:

voodoo47 on 28/9/2012 at 15:13

isn't steam putting the game data somewhere in the program files folder? that is a big no-no for all dark engine games.

//ddfix is not an issue, as the exe is overwritten with the new one. also, there should be a thief.log file in yout game folder, try posting that.

LarryG on 28/9/2012 at 15:30

Quote Posted by The Few

No worries we were all young once.

1) if you only want to play you don't need any of the DromEd stuff. But ... you may still want it because it can be useful, and you never know, you might get bitten by the modding bug. So I recommend installing it all if you have the disk space to do so.

2) This is probably the simplest approach for you to take (others may disagree and chime in):
[INDENT]a) reinstall a clean T2 from your official media. Since yours is from Steam & mine isn't I don't know exactly what that means for you. But you want a clean installation with no customizations to start with.
b) read and apply (http://www.ttlg.com/forums/showthread.php?t=131106) Tafferpatcher: unofficial complete patch for Thief 2 to your current T2 installation. I suggest this because, while it may put in some stuff that's obsoleted by 1.19, it should guarantee that your base is now a correct 1.18 patched version. Start Thief2.exe and test it to make sure everything works as expected.
c) read and apply the "Instructions for Installation and Application of the 1.19 Patch Including DromEd" (above). Start Thief2.exe and test it to make sure everything still works as expected.[/INDENT]

That should do you.

Edit: (http://www.ttlg.com/forums/showthread.php?t=114292) DromEd ToolKit (should you decide to install DromEd)

Ryu Connor on 28/9/2012 at 16:32

Quote Posted by MoroseTroll

3DNow! - yes, it has been depricated in the modern Bobcat and Bulldozer-based AMD CPUs. But MMX is still available on every CPUs released since 1997.
Well, AVX is a relatively new instruction set (and it requires WinVista SP2 or Win7 SP1), so yes, it's quite clear for me why the new exe-files do not support it. But SSE1-4 are much more widespread instruction sets, so I suppose the author(s) just had no time to implement them.
Maybe.

Sorry, I should clarify the context of deprecated. I don't mean removed from the CPU, I mean it's functionality has been replaced by SSE and AVX. You're not supposed to write programs with it anymore.

(http://msdn.microsoft.com/en-us/library/windows/desktop/ee418798(v=vs.85).aspx) 64-bit programming for Game Developers

Quote Posted by "Microsoft"

The x87, MMX, and 3DNow! instruction sets are deprecated in 64-bit modes. The instructions sets are still present for backward compatibility for 32-bit mode; however, to avoid compatibility issues in the future, their use in current and future projects is discouraged.

As an aside are you sure this new executable doesn't use SSE? It's by no means a smoking gun, but the sshock2.log does CPU identification and names SSE versions available to it.

Code:

: CPU: arch=x86-64 , fam=586 , cpus=8
: SIMD: SSE=3 , 3DNow=0

sNeaksieGarrett on 28/9/2012 at 16:38

Steam recently added a feature through its beta (don't think it's in the stable release) in which you can tell it where to install your game. Doing this is meant for installing to a secondary hard drive, but you may be able to tell it to install to the same drive but in a different place than program files. I haven't tried it myself, but you'll see it when you go to install a game in the pop up. Keep in mind that the option may or may not pop up, I've heard that the functionality is not available for every game in your Steam library. In order to get the feature I'm talking about, you'll have to opt into the beta program. Steam> Settings> Beta Participation, click Change

I wonder though, for those of you who have a steam version of the game, have you tested to see if the game will run by moving the directory outside of the steam folder?

Nameless Voice on 28/9/2012 at 16:42

Quote Posted by voodoo47

Steam installs to Program Files (x86), though, which isn't as heavily restricted as the standard 64-bit Program Files folder is.

ZylonBane on 28/9/2012 at 16:49

First thing I did when I installed Steam on my system a couple years back was to move the install folder to a secondary drive. Nicely solves these sort of problems.