bikerdude on 22/8/2008 at 16:27
Test setup:
Wolfdale E8400 | Gigabyte X38-DS5 | PowerColour HD4870 w/cat 8.8
Creative Xfi Xmusic | G.Skill 4GB memory | 250GB Raid-0 Hdd
WinXpSp3/VistaSp1
Windows Xp Sp3 x86 Cat 8.6Code:
Thief 1/G/2 (v1.33/v1.37/v1.18)
*
Vanilla:T1 - Works - silky smooth
T1G - Works - Mostly smooth, minor jitter/lag.
T2 - Works - silky smooth still has the useal crappy texture issue.
*
Vanilla + Widescreen:T1 - Works - silky smooth
T1G - Works - Mostly smooth, minor jitter/lag.
T2 - Works - silky smooth still has the useal crappy texture issue.
*
DDfix 1.1.1:T1 - WORKS + works with w-screen - silky smooth
T1G - WORKS + works with w-screen - silky smooth
T2 - WORKS - no discernible FPS lag + works with w-screen
*
DDfix 1.3.11:T1 - WORKS + works with w-screen - some jitter/lag
T1G - WORKS + works with w-screen - some jitter/lag
T2 - WORKS, set "UseCompatibleZBuffer=1" in ddfix ini
Thief 2 + Mission X*
Vanilla:T2 - WORKS, crappy texture issue and
lots of jitter/lag *
Vanilla + Widescreen:T2 - WORKS, crappy texture issue and
lots of jitter/lag *
DDfix 1.1.1:T2 - WORKS, smooth, only does 1280*1024 (nb. no fog)
*
DDfix 1.1.1 + widescreenT2 - WORKS, lots of jitter/lag
*
DDfix 1.3.11T2 - WORKS, set "UseCompatibleZBuffer=1" in ddfix ini and some jitter/lag
*
DDfix 1.3.11 + widescreenT2 - WORKS, set ddfix.ini as above , some jitter/lag
Thief 3 (v1.1)
*
VanillaT3 - WORKS smooth
*
Vanilla + WidescreenT3 - WORKS, silky smooth - ((
http://mugon.org/widescreen/thief.html) Mugon Widescreen FOV patch)
*
The above + JohnP texture packT3 - WORKS, silky smooth (even @1680*1050, 4xAA 16xAniso)
Windows Vista Sp1 x86 cat 8.6/8.8Code:
Thief 1/G/2 (v1.33/v1.37/v1.18)
*
Vanilla:T1 - Works - silky smooth
T1G - Works - silky smooth
T2 - Works - silky smooth + the useal crappy texture issue.
*
DDfix 1.1.1:T1 - Broken DX7 error
T1G - Broken DX7 error
T2 - Broken DX7 error
*
DDfix 1.3.11:T1 - WORKS + works with w-screen
T1G - WORKS + works with w-screen
T2 - Broken, even "UseCompatibleZBuffer=0/1" dosent work now :-(
but may work if you set the game to XP compatability mode
Thief 2 + Mission X*
Vanilla:T2 - WORKS, crappy texture issue
*
Vanilla + Widescreen:T2 - WORKS, crappy texture issue
*
DDfix 1.1.1:T2 - Broken DX7 error
*
DDfix 1.3.11T2 - Broken, even "UseCompatibleZBuffer=0/1" dosent work now :-(
but may work if you set the game to XP compatability mode
Thief 3 (v1.1)
*
VanillaT3 - WORKS smooth
*
Vanilla + WidescreenT3 - WORKS, silky smooth - ((
http://mugon.org/widescreen/thief.html) Mugon Widescreen FOV patch)
*
The above + JohnP texture packT3 - WORKS, silky smooth (even @1680*1050, 4xAA 16xAniso)
biker
NB. I have tested a
GTX280 so will be posting (
http://www.ttlg.com/forums/showthread.php?t=122684) the test results as per above on that card.
242 on 22/8/2008 at 21:22
I bet result will be the same as with HD2000 and 3000. I.e. T1/2 unplayable without ddfix.
bikerdude on 23/8/2008 at 08:11
Quote Posted by 242
I bet result will be the same as with HD2000 and 3000. I.e. T1/2 unplayable without ddfix.
Quote Posted by Hiatus
same fps drops are present in vanilla Dark Engine (T1/TG/T2 for sure, SS2 probably as well) game versions.
Cause is that both ddfixed (1.2+) and vanilla game versions use DX6/D3D6 renderer, whereas DX6 driver portion of ATI drivers for these chipsets appears to be broken/buggy (other older games from that era are affected as well, so the problem is wider) - most likely broken function calls for D3D6 or sth like that; another cause could be some vital h/w component removal from the die (see below) resulting in low fps. It's especially pronounced when particle-like effects (like fire/smoke/water/rain/snow etc) are visible on-screen - fps tanks then on HDxxxx.
Remember ddfix 1.0-1.1 which was using DX9 renderer instead of DX6? Using it cures (not sure if 100%) said problems on HDxxxx, so it's a proof that drivers are at fault (or some hardware portion assisting in h/w accelerating these DX6 function was removed from the die in this gen of chipsets - asi s the case with hardware support for 16-bit dithering (it was removed from these chipsets to conserve die size most likely); that would be even worse, as it's not software repairable with needed h/w missing completely).
Yes thats a given, the biggest problem is the very low frame rates that some taffers are getting on Radeon 2xxx, 3xxx are getting and details above.
biker
Thor on 23/8/2008 at 08:23
Quote Posted by 242
I bet result will be the same as with HD2000 and 3000. I.e. T1/2 unplayable without ddfix.
Rofl. Duh!
Anyway good luck on your new card test :cheeky:, hope it passes your judgement well.
242 on 23/8/2008 at 19:17
You should use ddfix 1.1.1 for Thief2, it uses DX 9 so there is no issues with speed on Radeons, but newer ddfix (I use 1.2.7) for Thief1/G because with DX9 versions of ddfix there is a glitch with health bar, and T1/G runs quite playable with DX7 (or whatever) ddfixes.
At least it works quite well for my 3870. No fog in T2 though (because of DX9 ddfix), no fog is better than 3 frames per second ;)
But it's a bad thing if T2 crashed with ddfix. I hadn't experienced crashes, the only problem I had - it was very slow with DX7 ddfixes in many places. Anyway, try 1.1.1
bikerdude on 23/8/2008 at 19:40
Quote Posted by 242
But it's a bad thing if T2 crashed with ddfix. I hadn't experienced crashes, the only problem I had - it was very slow with DX7 ddfixes in many places. Anyway, try 1.1.1
Hmm, I would prefer to use the latest version, but will test DDfix 1.1.1
biker
242 on 23/8/2008 at 19:54
Quote Posted by Bikerdude
Hmm, I would prefer to use the latest version, but will test DDfix 1.1.1
biker
You won't be able to use latest version for T2, you yourself cited Hiatus' post where he descibed why. Unless drivers for 4870 drastically differ from 3870, and they don't. We are left only with 1.0-1.1. option for T2. Of course it would be much better to have fog, but alas. At least it works fluid.
bikerdude on 23/8/2008 at 20:02
Quote Posted by 242
We are left only with 1.0-1.1. option for T2. Of course it would be much better to have fog, but alas. At least it works fluid.
Well Im hoping Timeslip can fix this otherwise I'm sending the card back and Getting a GTX280 instead.
Timeslip..?
biker
Hiatus on 23/8/2008 at 22:22
biker
thank you for testing the card and the report. So it's now confirmed that the situation with HDxxxx is like I expected (and described why in quoted post). Btw Nvidia (with GF8xxx and up) has similar issues in older DX (3-7) games (horribly slow fps in older DX games, as described here: (
http://forums.nvidia.com/index.php?showtopic=74969) for example - read all posts by
filipetolhuizen in this thread for details).
"T2 - WORKS (v1.1.1), Broken (v1.3.11)"
in what way 1.3 is broken in T2? Game crashes (where?) or sth else?
And how severe is fps drop issue in various places in T2/T1/TG (esp. with particle effects visible on screen) - what is fps in these situations (is it really <10 fps)?
Please load T2 OM
Framed and check fps at the very start of that mission (it's a demanding place - good for testing performance of various graphics chips and CPUs). Also test fps in some recent resource demanding FMs.
About your findings: please describe your findings/give link to this thread on Rage3D forums, in these 2 relevant threads:
(
http://www.rage3d.com/board/showthread.php?t=33927065)
and
(
http://www.rage3d.com/board/showthread.php?t=33929691)
do mention there that with HDxxx latest D3D6 versions of ddfix (1.2 and up) are broken, too (so we don't even have working 3rd party fix any more).
Don't forget usual ATI support form here: (
http://support.ati.com/ics/survey/survey.asp?deptID=894&surveyID=486&type=web) (ATI Catalyst Crew Feedback) - describe the issue and link to here.
btw Timeslip recently (on 20th of August) updated his home page ( (
http://timeslip.chorrol.com) ) with new entry - but no mention about thief/ddfix in it, unfortunately. Looks like he abandoned any development of ddfix (like planned v1.4 etc), at least for now (see my enquiry about it here: (
http://www.ttlg.com/forums/showthread.php?p=1749591#post1749591) - with no anwser from Timeslip - btw do you have email/PM contact with him - IMO we should contact Timeslip directly via these means and not wait till/if he visits this forum). But as I said, I don't think this issue (I mean low fps issue for D3D6 renderers on HD2xxx+) is fixable on ddfix level (except for switching to higher D3D version, like D3D9 which Timeslip already did in ddfix 1.0-1.1), because this is driver/hardware level problem, which also affects other DX games from that era (and Nvidia with their GF8xxx+ has similar problem as ATI with HD2xxx+, curiously - probably the result of die/driver code cuts for DX10 parts from both vendors).
The best (most compatible with current DX9/10 and future graphics chips/drivers and so the most future proof; it would fix low fps issue, too) solution would be of course ddfix version with D3D9 (like 1.0-1.1) and even D3D10 (Vista+ only) renderers, but without known bugs/issues from these 1.0-1.1 versions (which made Timeslip revert to D3D6 in 1.2+), and feature equivalent with 1.2-1.3 versions. But would obviously require quite a lot of work from Timeslip (1st, to try to fix said bugs and 2nd, to (re)implement features later added in 1.2-1.3) and it's uncertain he would be able to resolve issues with D3D9 renderer which he was not able to resolve last year, when developing 1.0-1.1.
So for good compatibility with older games I recommend to do what I did and get ATI X1950 Pro/XT/XTX which is the last chip from either ATI/NV with relatively good compatibility/support for older games (both on hardware and software/driver level).
===
1 more related req to you: please get MS DXCapsViewer app (some new 9.xx version) either from recent MS DirectX SDK (you don't have to install it - just unpack it with Winrar/7-zip etc and look for DXCapsViewer.exe file) or standalone DXCapsViewer.exe v9.xx from the web (if you can't find it, PM me), and check whether HD4xxx reports it supports Dithering.
how to: run DXCapsViewer, in View menu select "All caps", go to Direct3D9 Devices -> your HD4xxx -> D3D Device Types -> HAL (not Reference!) -> Caps -> Raster Caps; on the right check whether D3DPRASTERCAPS_DITHER says Yes or No. (Do the same check for Geforce 8xxx+ you got). Even better, save reports from whole tree (with "All Caps" option checked) to a file (for both ATI/NV) and upload them, so we can compare them.