GSdx 1.0
(04-07-2016, 07:07 PM)tsunami2311 Wrote: MSAA dont work in opengl unless gregory fix that
Nope, it's actually blocked out now so that it can't be selected in OpenGL Tongue
Reply

Sponsored links

AMD GPU show garbage now in OpenGL mode. A lot of black texture. On latest buildĀ https://github.com/PCSX2/pcsx2/commit/b9...27cba92502

[Image: 85ff89b0-fd60-11e5-955c-1bb718dc7757.png]
Reply
For all AMD users, if you're driver is still broken you can read/complain on this thread https://community.amd.com/thread/194895
Reply
(04-08-2016, 05:24 AM)tabnk Wrote: AMD GPU show garbage now in OpenGL mode. A lot of black texture. On latest buildĀ https://github.com/PCSX2/pcsx2/commit/b9...27cba92502

Keep an older GSDX build for now until we can build the GSDX_Legacy version on the build bot or AMD fixes the bug, the project files still need updating currently.
[Image: ref-sig-anim.gif]

Reply
A gentle remainder/push on the AMD team could help too Tongue2 They did the fix the 27th of January. I expected the fix delivery to be around 3 months, so hopefully they will release it soon. However, I'm afraid that AMD perf will dive again.
Reply
Why is this an AMD bug? A git version from two days ago is fine, and now it's completely ruined unless you set the BUA to Ultra(which makes it unplayably slow).
Reply
(04-08-2016, 12:23 PM)FlatOut Wrote: Why is this an AMD bug? A git version from two days ago is fine, and now it's completely ruined unless you set the BUA to Ultra(which makes it unplayably slow).

It's an AMD bug because 2 days ago that extension would automatically disable on AMD cards but as we are forking GSDX to take advantage of newer tech that extension is now mandatory, but it works on every manufacturers cards except AMD.

So it is an AMD bug and they have apparently fixed it, but it still hasn't materialised in the drivers.
[Image: ref-sig-anim.gif]

Reply
(04-08-2016, 12:35 PM)refraction Wrote: It's an AMD bug because 2 days ago that extension would automatically disable on AMD cards but as we are forking GSDX to take advantage of newer tech that extension is now mandatory, but it works on every manufacturers cards except AMD.

So it is an AMD bug and they have apparently fixed it, but it still hasn't materialised in the drivers.
Intel iGPU has the same issue.
Reply
(04-08-2016, 12:58 PM)FlatOut Wrote: Intel iGPU has the same issue.

Which Intel iGPU? is it 4th Generation (4000 series) or higher?

Regardless, AMD have already acknowledged it's a bug, if Intel are having the same issue they need to fix it too.
[Image: ref-sig-anim.gif]

Reply
(04-08-2016, 01:08 PM)refraction Wrote: Which Intel iGPU? is it 4th Generation (4000 series) or higher?

Regardless, AMD have already acknowledged it's a bug, if Intel are having the same issue they need to fix it too.
Yes, it's a 4600.
Reply




Users browsing this thread: 3 Guest(s)