Did you disable vsync for the open drivers? Catalyst tears by default you know
I've yet to see a single case where this is actually a good thing for the consumer. Without fail, the OEM supports 1 to 2 versions of Catalyst that came out when they were selling the hardware, and then they stop all support. After a couple of years without updates, those drivers inevitably start showing their age with performance problems and bugs in newer games.Laptops are frequently a special case because the OEMs often want customized drivers and as a consequence end up deciding that managing driver releases and updates themselves is the way to go, but AFAIK that has historically only applied to Windows drivers.
Presumably, the OEM's are paying AMD lots of money for this, because otherwise they are just making themselves look bad for no reason.
If you are brave enough to hack the drivers, you can get the standard desktop drivers running on laptops. It's just not officially supported by anyone.
.. or you run a proper OS, and the OEM can go screw itself, right?
But yeah, the windows AMD laptop situation sucks. I can't see either how that can be spun as a good thing.
Now there is solution of MP3 and H.264 "problems" for every Linux distribution. I just not understand why distribution developers not provide same solution for floating point and S3TC problems to end-users. There is report to Ubuntu Team for example: https://bugs.launchpad.net/ubuntu/+s...sa/+bug/823062
One needs a standard API layer that translates to whatever software is in a distro. Use ZIP format for the package (free to use by anyone) and some kind of autorun language.
Linux standard base is not the answer. Stuff like Wine is, because it's a one-stop-shop for getting a plethora of (Win32) API software to run. 25 Xlib games not running on Wayland? Just port the layer.