Closed GoogleCodeExporter closed 8 years ago
Are you able to try running with 32-bit or vista / XP compatibility mode?
Original comment by pokefan0...@gmail.com
on 10 Aug 2011 at 6:07
Those eye give me the creeps :p
Original comment by ExtremeD...@gmail.com
on 10 Aug 2011 at 1:44
Unfortunately there is no difference running under compatibility modes.
Original comment by Veritech...@gmail.com
on 10 Aug 2011 at 9:10
You will have tried running with 32-bit and older ATI driver with same result?
If so, you will have to wait for Gonetz response.
Original comment by pokefan0...@gmail.com
on 10 Aug 2011 at 11:00
I have the same issue with r237. I'm on Windows XP and I have an ATI HD4850.
I have also attach what it looks like on Jabo's D3D8.
Original comment by Aktan...@gmail.com
on 12 Aug 2011 at 6:54
Attachments:
I made a mistake, I meant I used r245, not r237
Original comment by Aktan...@gmail.com
on 12 Aug 2011 at 7:38
So after finding out this issue also happens in SM64, I decided to do more
research and apparently the ATI driver is the culprit. If I use an older
openGL driver from ATI (I tried 11.1), the problem is gone. I'm going to try
to find out which driver version exactly this started.
Original comment by Aktan...@gmail.com
on 20 Aug 2011 at 1:53
ATI drivers 11.4 start to have the problem. 11.3 openGL driver are fine. If
you get the atioglxx.dll file from 11.3, place it in the same directory as the
Glide Wrapper.
Original comment by Aktan...@gmail.com
on 20 Aug 2011 at 2:17
Original comment by gon...@ngs.ru
on 20 Aug 2011 at 12:33
Many thanks Aktanusam, I reverted to the 11.3 driver and everything works fine!
Is it a ATI problem or some new change which Glide64 can't handle properly?
Original comment by fix94.1
on 27 Aug 2011 at 5:58
Well if it works fine on NVidia cards, I would say it's a problem with ATI,
unless both had the same flaw before and ATI just recently fixed it. Really, I
have no idea.
Original comment by Aktan...@gmail.com
on 27 Aug 2011 at 9:14
ATI drivers 11.11 has this fixed, so I would say it's ATI's problem.
Original comment by Aktan...@gmail.com
on 8 Dec 2011 at 10:03
Original issue reported on code.google.com by
Veritech...@gmail.com
on 10 Aug 2011 at 5:12Attachments: