Thief 1.33, NVIDIA 7300 GT, and Windows 7 x64. No known issues so far. - by TheKeeper
sNeaksieGarrett on 18/11/2013 at 05:15
Quote:
Actually, the software renderer does not work. I just tried it and it plays way too fast. Very entertaining though. The movies do not work either.
This is exactly why people use TFIX/tafferpatcher in the first place since it corrects issues like this. However, having said that, your situation is a bit different. I don't know if anyone's tried using software mode with NewDark, or whether that's even possible. Despite this, I can still suggest a method to remedy the "plays too fast" problem if you insist on keeping Thief as it is without any "patches."
You either need to A.) Enable vsync or B.) Alt-tab out of thief and open task-manager, right click the thief2.exe process and
set affinity so that only one core gets used. This method is temporary and there are other methods to solve it, but this is the quickest easiest method, other than using one of the fan patches to permenently fix this problem. Or at least, when talking about Thief in Hardware Mode.
Oh, one other thing, you really don't need to (and it's also frowned upon in these forums) post more than once in a row. You can edit your original post if need be.
TheKeeper on 27/11/2013 at 00:28
Quote Posted by sNeaksieGarrett
This is exactly why people use TFIX/tafferpatcher in the first place since it corrects issues like this. However, having said that, your situation is a bit different. I don't know if anyone's tried using software mode with NewDark, or whether that's even possible. Despite this, I can still suggest a method to remedy the "plays too fast" problem if you insist on keeping Thief as it is without any "patches."
You either need to A.) Enable vsync or B.) Alt-tab out of thief and open task-manager, right click the thief2.exe process and
set affinity so that only one core gets used. This method is temporary and there are other methods to solve it, but this is the quickest easiest method, other than using one of the fan patches to permenently fix this problem. Or at least, when talking about Thief in Hardware Mode.
Oh, one other thing, you really don't need to (and it's also frowned upon in these forums) post more than once in a row. You can edit your original post if need be.
The solution is to rewrite the timing code. Believe it or not, this has been a problem for some time now. Bad timing code even affected those with 286 machines when they moved up to a 486. I chuckled to myself when I read about it in an old CompuServe archive. Vertical synchronization doesn't fix the problem. At least for me it doesn't. When Thief went gold, I don't even think 1ghz processors were even on the market. I could knock the Dark Engine but the Unreal engine suffers from the same problem. I don't think anybody foresaw the great leap in processing power that was to happen.
Aside from the bad timing code, there is no good reason why I should not be able to run the game using Direct Draw rather than Direct3D.
As far as the second cpu goes, it locks Thief. If I don't disable it I cannot play at all.
Aside from the inability to play the cut scenes inside the game and having to disable the second cpu, the game plays fine using Direct3D.
sNeaksieGarrett on 27/11/2013 at 04:59
If by "timing code" you're referring to something related to CPUs, that's not a simple solution, nor is it one that I would know anything about, or even suggest. Enabling v-sync is a far easier, simpler solution. However, you've said it didn't work, but it was worth a try in my opinion. The next solution would then be to try another method of slowing the game down.
Since you don't seem to be too committed to working on getting software mode to function, I'm not going to suggest anything else unless you'd like further help. However, having said that, I would still recommend checking the Thief FAQ thread.
