Next Generation Emulation banner

ATI/OpenGL driver issue

111K views 262 replies 48 participants last post by  mzso  
#1 · (Edited)
#3 ·
Mako Eyes, can you post a screenshot of your [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\OpenGLDrivers\ati2dvag] folder because I had to manually create mine for OpenGL extension viewer to recognise the ICD.
 
#4 ·
I don't understand where these problems are coming from. I can't say I have even come remotely close to such issues using WindowsXP. My X800 runs OGL2 plugins flawlessly using Omega's drivers.
from what i understand it seems to be the catalyst drivers that are at fault.
 
#6 · (Edited)
i wouldnt hold my breath. ive talked to several people who have attempted to get them to do something about this and they have told me they were completely ignored.

edit- and i would imagine there has been a decent amount of other people complaining because (and anyone can correct me if im wrong here because like i said before, im just going off the large amount of talk and what i have heard/read about this) this isnt limited to the OGL plugins, apparently it affects other OGL applications, so they cant use the "not important enough" cop-out.
 
#7 ·
Mako Eyes, can you post a screenshot of your [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\OpenGLDrivers\ati2dvag] folder because I had to manually create mine for OpenGL extension viewer to recognise the ICD.
Here you go. I did absolutely no manual editing. Actually, I haven't even tried using ATi's factory drivers with ePSXe.
 
#8 ·
I suggest making a petition for Ati, bringing all the evidence we have about these problems that connects them to Ati drivers, and see what they do with it. I'll sign :D(I have these problems too)
 
#9 ·
good luck on that one.
 
#10 ·
Thanks Mako Eyes, thats exactly what I have except I had to change atioglxx to atio6axx because I'm on Vista x64. Degeon, see if you have that registry entry, I had to add it manually it enabled the ICD but not hardware acceleration.
 
#11 ·
so you have found a fix for this issue? lol ATI owes you fools a job.
 
#12 · (Edited)
Only a partial fix, look at one of the screenshots in my first post from PC Wizard 2008 v1.84 you'll see that I have no OpenGL hardware acceleration ("software, no"), I believe Degeon can confirm this too. However, on my other computer (P4 Northwood 2.66ghz, 1gb ram, Nvidia FX5200 AGP) it says "hardware, yes".

I don't understand where these problems are coming from. I can't say I have even come remotely close to such issues using WindowsXP. My X800 runs OGL2 plugins flawlessly using Omega's drivers.
You're lucky Mako Eyes, see this: AMD Game Forums - OpenGL with a Radeon X800xt on Vista
 
#13 ·
yes, PC Wizard Shows Software acceleration as well...
hhmmm, I have atioglx2.dll in the value, but im talking XP-ish most of the time. Ati drivers for XP and Vista are "radicaly" different. should I leave it at that?
 
#14 ·
ATi are false advertsing Radeon™ X1600 Series - GPU Specifications


Ultra-Threaded Shader Engine

* Support for Microsoft® DirectX® 9.0 Shader Model 3.0 programmable vertex and pixel shaders in hardware
* Full speed 128-bit floating point processing for all shader operations
* Up to 128 simultaneous pixel threads
* Dedicated branch execution units for high performance dynamic branching and flow control
* Dedicated texture address units for improved efficiency
* 3Dc+ texture compression
o High quality 4:1 compression for normal maps and two-channel data formats
o High quality 2:1 compression for luminance maps and single-channel data formats
* Multiple Render Target (MRT) support
* Render to vertex buffer support
* Complete feature set also supported in OpenGL® 2.0
 
#15 ·
i suppose you could sort of say that. but this seems to be more of a driver issue than it is a card model issue. i believe the cards themselves are *capable* of supporting OGL fully, its just their drivers that have the ****ty support.
 
#16 ·
#17 ·
from what i have heard its just the catalyst drivers. i imagine if you were to test some out you would run into this.
 
#18 ·
I don't know if anyone knew this, but ATi covered up (didn't mention in known issues or knowledge base) that AGP cards were broken (no Direct3D/hardware video decoding) from Catalyst 7.8 to 8.1 hotfix, I think the OMEGA drivers still worked.
 
#19 ·
Go start a class action lawsuit against them.
 
#20 · (Edited)
If I remember correctly Omega's didn't work for me either... I'll wait for a newer driver because his last one is 7-12 me thinks...


It is really weird that the Ati drivers causes these sort of things. I know that they are main suspects in this case but we have to keep an open mind and check other leads as well.
i have a few ideas for "experimentation" to try and isolate the problem
1) Have anyone who have experienced the problem tried using a different VGA and/or main board?

I have tried using an Ati HD 2600 for testing, but it doesn't count(and, obviously, it didn't work)
if possible, we need someone to test it on an Nvidia card and/or replaced main board(with the same model).
if someone replaces something, and the problem appears or disappears any info would be value
Main board:(new/old model and revision if possible), New and old Bios vr. PCI-E or AGP(new vs. Old)
VGA: Compeny(Asus Radeon/nNvidia for example) suffix(GTO, XT etc.) drivers(Official,Omega's. witch vr?)
OS: XP, Vista? 32/64Bit?

2)also, if someone who suffer from these could provide evidence on the absence of the problem on Omega drivers and the registry value 22point8 has aforementioned?(For xp and Vista)

3)the same (question nu. 2) applies with someone who hasn't experienced the problem and we'll need the registry values of the Ati factory Drivers and Omega Driver's Value as well (For XP and Vista)

4) don't we need to name this phenomena?
I say the Triangles of Doom! :p

anyway, I know this may be difficult to accomplish but if more and more people would volunteer to help we may be able to prove/dispute our claim about the drivers. and maybe to find a solution on our own(As Ati, doesn't really care, apparently)
Since I have both Xp and Vista, I'll try Omega Drivers on both OS's.
speaking of vista, did Omega solved the Driver signing problem on Vista x64? normally that OS is designed to allow the installation of Signed drivers only(witch is secure, but may cause problems on some hardware manifacturers)
 
#21 ·
I doubt ATI care about Emulation....
 
#22 ·
Regardless...

Anyway, it seems that Ati haven't heard of customer service much...
that's why I offered these experimentations, so we'll be able to track down the root of the problem ourselves. then, maybe we'll be able to find a solution.
 
#23 ·
Well Schumi-4-eva, ATI should care that their OpenGL doesn't work in ANY applications according to this attached screenshot, it seems to either be done in software, or via directx. This triangle issue is proof of something not working properly in their drivers.

As a developer maybe ATi would listen to Pete, and seeing as there is nothing wrong with his plugins, its their fault.
 
#24 ·
ok guys, I have some good news and some bad news
The bad news is that installing OmegaDrivers(7.12 based) didn't solved the problem
How ever, I believe that I have another evidence piled up against Ati here.
Before I start however I must emphasize that I did what I did because I know what im doing and how the Registry works so don't come to me if you get in trouble because something I've written.
I've messed around a little(thanks 22point8 against for your registry reference)
and I've "forced" my pc to use Windows Xp default OpenGL 1.1 Driver "Opengl32.dll"
by placing opengl32.dll instead of atioglx2.dll(or something)
itw as a gamble, but hey, I tried booting my copy of discworld Noir. it was slow, it was green (?!) but the Triangles were all gone (as far as I've noticed anyway)!
 
#25 ·
I doubt ATI care about Emulation....
like i said, i have heard that this affects other OGL applications outside of things related to emulation. if any of you ATI users have a game like quake 4 you might be able to confirm this.
 
#26 ·
Just reread a support email that makes reference to HKLM/System/CurrentControlSet/Control/Class/{Adapter GUID}/0000/
anyway, I found this very interesting page on the internet, maybe we can fix this ourselves afterall, I don't have this registry entry though, do you?
Loading an OpenGL Installable Client Driver