It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
Thief seriesGame Killing Direct3D error(34 posts)solved(34 posts)solved
(34 posts)solved
Pages:
1
2
3
This is my favourite topic
Posted January 31, 2012
Well, not a good start for Thief Gold. I can launch the game, navigate menus, even start a new game, however, that new game only makes it as far as the goal summary just after opening cutscene, then fails. If I try to start actually playing the game, it produces the following error:

ERROR: Direct3d device driver does not accurately report texture memory usage.
Contact your 3d accelerator vendor for updated drivers.

My 3D card is a GeForce 7600GS with current drivers. The only in-game settings change I have made is switching the character detail from low to high. Full hardware specs:

Windows XP
P4 3.0GHz HT
3GB RAM
GeForce 7600GS 256MB
SB AudigyLS

Any ideas on this one?

EDIT - Though shadearg's first post is marked as the solution, read through the whole thread for the full details of the solution, especially the correct offsets to hex edit.
Post edited January 31, 2012 by cogadh
This question / problem has been solved by shadeargimage
Posted January 31, 2012
avatar
cogadh: [...]
try adding line safe_texture_manager to cam.cfg
Post edited January 31, 2012 by Thiev
Posted January 31, 2012
avatar
cogadh: Any ideas on this one?
Install DDFix and the Dark Engine Resolution Patch as detailed in sections 3 and 4 of my Windows Vista/7 compatibility guide:

Thief: The Dark Project - Windows Vista/7 Compatibility Guide

The process in these sections should be exactly the same for Thief Gold. I will be updating the guide for the GOG version soon.
Post edited January 31, 2012 by shadearg
Posted January 31, 2012
avatar
Thiev: try adding line safe_texture_manager to cam.cfg
No joy. Is there a particular section of the cfg it should go in? I just added it to the end of the file.
avatar
shadearg: Install DDFix and the Dark Engine Resolution Patch as detailed in sections 3 and 4 of my Windows Vista/7 compatibility guide:

Thief: The Dark Project - Windows Vista/7 Compatibility Guide

The process in these sections should be exactly the same for Thief Gold. I will be updating the guide for the GOG version soon.
Thanks, but I'm not going through the hassle of hex editing my exe when first off, we don't know what changes GOG might have made to the executable already which could make those instructions invalid and secondly, GOG already says this works without it and therefore they need to fix it.

EDIT - And based on the below response, it appears I may have no choice but to use it...

EDIT 2 - And now it doesn't really matter since it appears those hex editing instructions don't apply to the GOG version of the executable... either that or I'm using this crappy hex editor completely wrong.
Post edited January 31, 2012 by cogadh
Posted January 31, 2012
avatar
cogadh: No joy. Is there a particular section of the cfg it should go in? I just added it to the end of the file.
No, my bad. It's the solution we used for Thief 2 but apparently not applicable for TG.
Right now, DDFix is the easiest way to bypass the bug but I'm looking into it.
Post edited January 31, 2012 by Thiev
Posted January 31, 2012
avatar
Thiev: No, my bad. It's the solution we used for Thief 2 but apparently not applicable for TG.
Right now, DDFix is the easiest way to bypass the bug.
So this game is not actually compatible without using hackish fan patches? That's not what you are advertising.
Posted January 31, 2012
avatar
cogadh: EDIT 2 - And now it doesn't really matter since it appears those hex editing instructions don't apply to the GOG version of the executable... either that or I'm using this crappy hex editor completely wrong.
I'll update this post with the corrected offsets for the GOG version in a few minutes.

Edit: The corrected offsets for the GOG version are as follows:

0x215526 - Change 'r' 0x72 to 'f' 0x66
0x215527 - Change 'a' 0x61 to 'i' 0x69
0x215528 - Change 'w' 0x77 to 'x' 0x78
Post edited January 31, 2012 by shadearg
Posted January 31, 2012
you know, the wonderful thing about the 'net is that whatever your problem is, there is a good chance that somebody already has a working solution -all you have to do is look around for a bit.
Post edited January 31, 2012 by voodoo47
Posted January 31, 2012
avatar
voodoo47: you know, the wonderful thing about the 'net is that whatever your problem is, there is a good chance that somebody already has a working solution -all you have to do is look around for a bit.
That's great, except it doesn't address the real problem: I shouldn't need to do that at all, I should only need to do that if I want to enhance the product that GOG is selling, which should already work at the very least. It definitely shouldn't still have a compatibility bug that the original retail release had, otherwise what are we really paying GOG for? Not to mention, it doesn't work as long as I can't get DDFix running and I won't get it running without specific hex editing instruction for the GOG version of the executable, which to my knowledge, don't exist yet.
avatar
cogadh: EDIT 2 - And now it doesn't really matter since it appears those hex editing instructions don't apply to the GOG version of the executable... either that or I'm using this crappy hex editor completely wrong.
avatar
shadearg: I'll update this post with the corrected offsets for the GOG version in a few minutes.

Edit: The corrected offsets for the GOG version are as follows:

0x215526 - Change 'r' 0x72 to 'f' 0x66
0x215527 - Change 'a' 0x61 to 'i' 0x69
0x215528 - Change 'w' 0x77 to 'x' 0x78
You sure about that? I'm not seeing the "raw" in those offsets, so I don't see what I'm supposed to be changing.
Post edited January 31, 2012 by cogadh
Posted January 31, 2012
avatar
cogadh: ...
ddfix ddfix ddfix
Post edited January 31, 2012 by TheJoe
Posted January 31, 2012
avatar
cogadh: It definitely shouldn't still have a compatibility bug that the original retail release had, otherwise what are we really paying GOG for?
We pay GOG for release of old forgotten and/or abandoned franchises. Dedicated communities work their butts off to fix problems that the developers didn't have clearance or budget for, and GOG is really good about providing us legal release of the proper versions that can utilize these community fixes. It's obviously not ideal, but that is a service I will gladly pay for.
avatar
cogadh: You sure about that? I'm not seeing the "raw" in those offsets, so I don't see what I'm supposed to be changing.
I hope so, or I don't know what the hell I just bought ;)

It may be easier to search for 'ddraw.dll' (no quotes) and change the very first instance from 'raw' to 'fix'.
Post edited January 31, 2012 by shadearg
Posted January 31, 2012
avatar
cogadh: It definitely shouldn't still have a compatibility bug that the original retail release had, otherwise what are we really paying GOG for?
avatar
shadearg: We pay GOG for release of old forgotten and/or abandoned franchises. Dedicated communities work their butts off to fix problems that the developers didn't have clearance or budget for, and GOG is really good about providing us legal release of the proper versions that can utilize these community fixes. It's obviously not ideal, but that is a service I will gladly pay for.
We don't just pay for the same broken game that we could find on any number of E-Bay sites or at the local thrift shop, we pay GOG for compatibility. The "About Us" page, point #4 :
4. All games are Vista and XP compatible.
Thanks to our handsome programming team, the classics are now Windows Vista and Windows XP compatible. Now you can use your lightning-fast PC to unleash the full potential of those games you just couldn't play properly on that busted old 386.

When we don't get it, we aren't getting what we paid for.

avatar
cogadh: You sure about that? I'm not seeing the "raw" in those offsets, so I don't see what I'm supposed to be changing.
avatar
shadearg: I hope so, or I don't know what the hell I just bought ;)

It may be easier to search for 'ddraw.dll' (no quotes) and change the very first instance from 'raw' to 'fix'.
It was a bonehead on my part. My hex editor was displaying the offset base in decimal instead of hex, so when I searched for those offsets, it found a completely different grouping.
Post edited January 31, 2012 by cogadh
Posted January 31, 2012
avatar
cogadh: It was a bonehead on my part. My hex editor was displaying the offset base in decimal instead of hex, so when I searched for those offsets, it found a completely different grouping.
Cool, glad you got it sorted. I hope this fixes your problem.
Posted January 31, 2012
There's no need to manually hex edit the executable; there's already pre-patched versions for ddfix. Here is the link to the .exe for Thief Gold. :)
Posted January 31, 2012
avatar
PastramiX: There's no need to manually hex edit the executable; there's already pre-patched versions for ddfix. Here is the link to the .exe for Thief Gold. :)
Unless that was created today, that's not the GOG version of the executable, so it won't work correctly.
Pages:
1
2
3
This is my favourite topic
Community
Thief seriesGame Killing Direct3D error(34 posts)solved(34 posts)solved
(34 posts)solved