mudi on 13/9/2009 at 15:59
It probably won't work with the Savegames in the ThiefDS folder because of permission problems. Try putting the savegame folder in c:\Users\Public\*somewhere*.
caqo on 14/9/2009 at 07:14
Windows 7 is not the problem.
I'm running Thief 3 on my Windows 7 RTM x64 with no trouble. I think that the problem is when you run the game with a cracked t3.exe file, Thief3 crash.
There's an unprotected t3.exe file that works, they say that the file was released by Ion Storm in the editor pack. I checked the file and it's digitaly signed by Ion Storm and Eidos, so it's not illegal it's use. I also tried the file and Thief3 worked fine.
About the Documents folder issue, it's not true, I ran the game, and then saw the savegames folder created under "Documents" like always.
My sys specs are:
Intel Core 2 Duo E8400
XFX Geforce GTX285 with latest drivers
2GB DDR3 Ram.
Windows 7 RTM 7600 x64
I also can run Thief2 with DDFIX with no issue but fog.
Cheers.
scarykitties on 14/9/2009 at 11:56
Thanks, caqo. I'll keep that in mind.
What's this about a dual core fix for DS? I haven't run across that--does anyone have a link?
mudi on 14/9/2009 at 12:59
Personally DS works for me without a multicore patch (running on a quad-core), except very occasionally the physics of the game seem to 'freeze' (I can still move but things stop working), which I figure might be some sort of multicore problem but not all I have to do usually is go to menu and come back.
scarykitties on 14/9/2009 at 13:16
I'll give the editor t3.exe a try, and if that doesn't help, I'll try re-installing with a new copy I ordered off Amazon (should get it tomorrow).
caqo on 15/9/2009 at 09:05
I just installed the game, then I applied 1.1 patch, and the game runs fine, I played this game on XP till the end and had no issues on a Dual core CPU.
Now I installed it with the same hardware, but in Windows 7 RTM x64, and the game runs ok. The only thing to notice, is that when I did the tutorial mission, The game got partially stuck when I had to lock pick the door... after a while, the lock pick tools appears on screen, and then I got stuck trying to climb the ladder after that door.
I'm going to play the entire game to see if it's buggy.
PD: I also installed the collectors texture packas, that give the game a nice look.
scarykitties on 17/9/2009 at 14:30
I haven't played it through yet, just glanced briefly in the tutorial mission.
Using the editor's t3.exe, all works well. ALchemy hasn't fixed the EAX as of yet (based on the installed program registry key it wants to base T3 from), but it may work if I point it to t3.exe instead of the installation root registry.
rms on 28/10/2009 at 01:34
Hello! I've just clean installed T3+1.1 on a clean install of retail win7, and it is working well. Here are the things to change or watch out for:
Change the compatibility to XP.
On game launch, ctrl-alt-del, and change affinity of both t3.exe & t3main.exe to the same cpu in task manager. This stopped soundloop crashing and other odd behaviours here.
In game options, disable Vsync. This will stop the slow lockpicking/ladder issue.
Don't enable eax, of course.
My system is a dualcore amd, radeon 4870, creative x-fi xtremegamer, all with latest drivers from ati & creative (creative has a onebutton update on their drivers page, use it!). I'm doing all this as administrator, btw, if that matters.
I also migrated my savegames from XP; start a new game in win7 & save, then check where it is putting them; should be under yourusername/public documents or whereever. Just copy the xp savegames to there & overwrite everything.
Just reached The Cradle in time for halloween! Scary!
rms
Fuod on 28/12/2009 at 04:07
I'm not sure if this thread is still being watched but I thought I'd mention that T3 is running perfect on my Dual Core W7x64 machine. All I did was the 1.1 patch, SDK and the imagecfg infinity fix (for both T3.exe and T3Main.exe). I didn't even have to change the compatibility settings.
I am getting random crashes in T3Ed and I can't play any maps I create... But otherwise the game is fine.
