Spymaster on 24/8/2005 at 16:05
Umm... well... I have problems with Terces now :mad:
I bought a new PC (well, upraded my old for the PCI-E):
PIV 2400 mHz
Leadtek WinFast GeForce 6600 256/128 PCI-E
512 RAM
Audigy 2 ZS
Windows 2000
And the game crashes when I:
a) enter the clocktower drain pipe courtyard (behind Terces)
b) enter the SQ side alley leading to Terces
What is really strange is that 6 series have pixel shader 3.0, but Thief says I have pixel shader... 1.4 (!))
I have 71.89 drivers, will check newer versions.
Spymaster on 24/8/2005 at 16:32
Didn't try the Omega - the 77.77 helped. However, Thief still says:
Quote Posted by THIEF "CHECK GRAPHICS CARD" FUNCTION
NVIDIA GeForce 6600
Driver version: 6.14.10.7777
DirectX version: 9.0c
Pixel Shader: 1.4 (so 3.0 = 1.4, right?) :tsktsk:
Ready to play!
Well, I can play Thief now. Also the game gets (like in hammer score) +0.25 amusement bonus for that.
EDIT: And 0.50 frustration penalty :rolleyes:
EDIT 2: (Read the FAQ) Great, now in areas with lots of effects (lots of dynamic lighting, light coming thru the window etc.) the game slows like on my old GeForce 3ti :mad: And the manual says:
Quote Posted by Thief DS manual
GeForce FX 5900 Ultra (highest in the manual) 56.72 No problems reported, game ran fine with details on high
It is not a big problem, but I expected the game to run OK.
Pootzwacke on 29/8/2005 at 19:16
I had this reboot bug as well... and I'm happy to say I've found several workarounds. Note that I was also in the position of not being able to proceed with the game, since the first transition between Stonemarket Plaza and Stonemarket Proper was the one that crashed the system. :) I'm now happily on to the first Pagan mission. I still crash occasionally, but it's down to a minor annoyance rather than a game-breaking brick wall.
First of all, it's definitely a combination of things - there absolutely is a save/load bug in the game itself, but it's triggered by particular events most of the time. I personally believe that the crash is related to either the loadzone portal itself, or possibly the "blue mist" *TEXTURE* in these loadzones (and that this part of it is a driver issue).
So, here's what you do.
1) Never overwrite savegames. Always save to a new slot. If you use Quicksave, the next save you make should be a "normal" save so that the Quicksave isn't overwritten. This solves a lot of the problems by itself. Overwriting savegames causes junk data buildup and eventual corruption. The Eidos forums mention this step... I ignored it, but it turns out it's definitely the right thing to do. :)
2) When you approach a zone portal with the intention of going through it, do the following: move into another nearby room or area, far enough away to insure that a) the doorframe/load zone itself isn't visible from your position (even the blue mist particles!), and b) that you're not in a zone from which you can SEE the area where the portal is. Put a few walls and doors between you and the portal. When you save, you can then return and try the level transition. (What I'm trying to say is that you should move far enough away that you're in a different Unreal Zone Portal area from which you can't see the Zone Portal area containing the level load zone. ACK!)
3) Don't walk forward into the portals - *back* into them. This seems to make a difference for the graphics driver part of the bug. Basically, if you're not looking at the blue mist when you hit the zone trigger, you're not rendering the zone portal or the blue mist, and it seems not to trigger the bug nearly as much.
4) To prevent crashes, don't load a game straight from the menu during gameplay (using Menu>Load Game or Quickload)... instead, die. Letting yourself be killed (by a guard, or drowning yourself, etc) causes the Load screen to come up anyway - but the game seems to "clean up" some things in memory when you do it this way, and a crash on the next load is less likely. This has been a BIG factor for me.
(Here's a very minor related spoiler - though probably one you'll want to know about, as it involves fun extra content that you might otherwise miss!):
[SPOILER]Please note that the first time you "die" in a City area, you'll be sent to the Prison level, which is a fun little escape mission. After you've done this once, dying will bring up the Load screen as usual.[/SPOILER]
The cause of the crash on load screens seems to be a video mode change between the game and the menu. When the "Loading" screen first comes up (the one with Garrett's face and a picture of the level being loaded), there's a brief flicker when the process first starts (it usually makes dots and dashes flit across the screen for a second, like when your monitor changes resolutions)... and that's when it crashes if it's going to. If you see that momentary glitch, it means that the mode change was successful and all will be well with the load; if it crashes, I bet you ten donuts you'll find that it's at that exact step when the system reboots.
Hope this helps... I think you'll find that taking these steps will make the game playable and allow you to continue on. :)
-Pootzwacke
tqwert2 on 4/9/2005 at 17:10
I was having this same problem and figured out is being caused by my sound card driver. I played the game originally early this year and had no technical problems. Then I recently tried to play again and was getting the constant hard crashes on level transitions or moving towards certain areas. After a lot of frustration I figured out that in the time between the two play throughs I had installed the Creative "beta" driver designed especially for Doom 3 (which make that game have, by far, the best sound in any game ever). This is apparently incompatible with Thief 3, because when I rolled back to the regular Sound Blaster driver, the crashes immediately stopped.
fedra on 16/11/2005 at 13:19
I allready overwrite the game savings).
What I should do?
I don't want to play it again to that point because I allready did 3 times?
SECOND
Do you have that jerky graphics to?
I mean, in some places the image (textures) looks like Duke Nukem. Very sharp and poor (low resolution).
If I try to rise the quality in game's options I can't see much diffrence.
Also sometimes I have very low fps.
I have AMD 1800+, GForce 6 (A 6200 TD), 256 + 512 SDRAM and NForce 2 MBO.
:nono:
242 on 16/11/2005 at 13:36
I think all those problems with sudden restarts or crashed are because of incopatible video drivers.
I haven't had a single crash so far (finished TDS 3 times), but I use R9800Pro + Catalyst 4.9. As it seems to me the graphics actually are quite smooth on R9800Pro, some visual jerkyness is caused by body awareness system rather than low FPS.
van HellSing on 17/11/2005 at 08:33
Some time ago I had a similar problem, which involved my PC restarting randomly when loading a map. Turned out to be mobo/integrated sound card driver problems. Everything works fine after a driver update.
fedra on 6/4/2006 at 21:31
Quote Posted by van HellSing
Some time ago I had a similar problem, which involved my PC restarting randomly when loading a map. Turned out to be mobo/integrated sound card driver problems. Everything works fine after a driver update.
I am still unable to play the game.
And since 2005 I made a lot of updates to my drivers.
I want to remember you that the restart is happening only when I try to enter a specific area.
In the moment I steped in that area. BOOM. :angel: Restart. :angel: :p
fedra on 19/7/2006 at 10:35
Quote Posted by fedra
In the moment I steped in that area. BOOM. :angel: Restart. :angel: :p
There are any updated info about how to fix this bug?
:wot: