Garbage on TNT2 Pro with detonators

[G Man]

Having problems on a TNT2 Pro using detonator drivers. First used the latest and then tried reverting back to some from early last year, but the problem is as follows: In some games, garbage appears instead of the actual items, for example midtown madness 2, where lines and blue see-through textures are seen. The other game is Half Life (Day of Defeat) where it locks up on the loading screen. Does anyone know of a driver fix or anything? Thanks.

[Radical Dreamer]

Possible causes for things like this are

1. The card doesnt support the feature thats trying to be used in the game

2. The card is overheating.

3. You dont have the latest version of direct x

Try using the detonator destroyers, the reinstalling the dets and then install DX9a then make sure that the car is at a reasonable temperature

[FatalException0E]

another possiblity is that the memory on the card is going bad. How long has this been happening?

[G Man]

Thanks for the ideas. This isn't happening on my computer, so when i next use the computer in question I'll try those out and get back to you, thanks.

[G Man]

Update: Tried the following. Firstly, directx 9 was installed, followed by latest detonators. No solving happening there. Also, tried this detonator destroyer, and it claimed it wouldnt function on the O/S (XP). Any more ideas?

[NooNoo]

TNT2 is not a dx9 capable card. I would revert back to dx7

[G Man]

Ah, indeed! Didnt think of that, but believe me it will be tried! Yes indeed! (results pending)

[confus-ed]

Originally posted by NooNoo
TNT2 is not a dx9 capable card. I would revert back to dx7

That as it maybe ! (strictly speaking it ain't !) but as direct x is supposedly backwards compatible with all previous versions, I don't think this will be the cause - if a feature isn't directly supported by hardware (that's what Noo is actually saying) then direct x9 should provide support via software ...

What seems more likely to me is that its opengl errors which have nothing at all to do with direct x (any version) - both your named games are opengl (unless you tell them to use direct x instead) ... so that'd pretty much be Rad's explanation '1' ....

Make sure whatever 'detonator' version you are using is WHQL then you ought to have an opengl ICD which is 'tested' too ...

[G Man]

Good points.... sorry i didnt mention it before, but i tried opengl and direct3d (in half life anyway) and the same problem happened... doesnt make a lot of sense does it? but my mate reckons it only started happening since he installed the latest detonators (which are WHQL by the way)

Sorry bud, but this one is still unsolved :P

[confus-ed]

Okey dokey ... but did you realise that there's probably lots of opengl ICDs floating around on this machine ? Usually there's one put in by the game in its own installation (so in its own directory) and another put in c:\windows\system (I think!?! somewhere 'standard' that windows looks at anyway before the game directory) ...

It's most confus-ing (appropriately for me ) to fathom which one its trying to use ... its not helped by the fact that many games only want to work with one particular version of the ICD, i.e that one installed by it originally, so do all your driver updates etc first then re-install the game & see if that helps ... I'm virtually certain of cause, if a little confus-ed on solution !!!