Seems so, EEVEE render for Blender™ is also OpenGL based, same as Q3engine, so they fixed something in OpenGL driver and it fixed Q3A as well... coincidence maybe 🙂
//3DMark Mesh Shader feature test results
21.2.2
21.2.1
https://abload.de/img/0zjmr.jpg
i assume it's backwards compatibility for other games that use this engine too, and because it's a legend of a game?
I do get jaggies on the sky textures in quake 3 team arena in the vanilla .exe, using Vega 56 my 2060s doesnt have that so maybe the game had some driver regressions and they decided to fix it?
EDIT: Trying other benchmark programs like "FPS Monitor" if you leave the HUD enabled while video render is restarting/reloading you will get corrupted parts of the overlay into the world's textures. This isn't the program's fault it's AMD's driver responding to the hook. MSI Afterburner doesnt because it uses different method. Happens in quite a few games since the Ad 2020 drivers, so that makes sense that AMD is slowly but surely updating their API to prevent hopefully these issues.
@SpajdrEX
After installing this driver and restart amd high definition audio device dont exist in device manager.
I have a hdmi monitor + creative xfi pcie + rx580.
Reverted to the old one and ok. Tried the new one second time and same thing happened.
@SpajdrEX
After installing this driver and restart amd high definition audio device dont exist in device manager.
I have a hdmi monitor + creative xfi pcie + rx580.
Reverted to the old one and ok. Tried the new one second time and same thing happened.
The very same thing happened to me. It just uninstalled the HDMI audio driver and can't get it back for nothing, factory install, it doesn't matter.
Monitor is a Samsung SMFX2490HD and GPU is a RX 480 8GB. Also had to go back to 21.2.1.
@SpajdrEX
After installing this driver and restart amd high definition audio device dont exist in device manager.
I have a hdmi monitor + creative xfi pcie + rx580.
Reverted to the old one and ok. Tried the new one second time and same thing happened.
DocReefer:
The very same thing happened to me. It just uninstalled the HDMI audio driver and can't get it back for nothing, factory install, it doesn't matter.
Monitor is a Samsung SMFX2490HD and GPU is a RX 480 8GB. Also had to go back to 21.2.1.
You can fix this by setting device manager to the By Connections view and removing the "High Definition Audio Controller" that has no subdevice installed, upon the next reboot or forced detection of devices, the AMD or Microsoft HD audio driver will reinstall once the "High Definition Audio Controller" is redetected.
This is likely a Windows bug, since endpoint detections are an OS thing.
I've seen the same thing occur with Realtek on a particular motherboard with a system recently moved to 20h1, the usual output device was just not present (Ghosted too) and forcing the entire chain from the top to be recreated brought it back.
The very same thing happened to me. It just uninstalled the HDMI audio driver and can't get it back for nothing, factory install, it doesn't matter.
Monitor is a Samsung SMFX2490HD and GPU is a RX 480 8GB. Also had to go back to 21.2.1.
You can fix this by setting device manager to the By Connections view and removing the "High Definition Audio Controller" that has no subdevice installed, upon the next reboot or forced detection of devices, the AMD or Microsoft HD audio driver will reinstall once the "High Definition Audio Controller" is redetected.
This is likely a Windows bug, since endpoint detections are an OS thing.
I've seen the same thing occur with Realtek on a particular motherboard with a system recently moved to 20h1, the usual output device was just not present (Ghosted too) and forcing the entire chain from the top to be recreated brought it back.
Astyanax:
You can fix this by setting device manager to the By Connections view and removing the "High Definition Audio Controller" that has no subdevice installed, upon the next reboot or forced detection of devices, the AMD or Microsoft HD audio driver will reinstall once the "High Definition Audio Controller" is redetected.
This is likely a Windows bug, since endpoint detections are an OS thing.
I've seen the same thing occur with Realtek on a particular motherboard with a system recently moved to 20h1, the usual output device was just not present (Ghosted too) and forcing the entire chain from the top to be recreated brought it back.
Thanks for the reply.
Not really on the mood to reinstall 21.2.2 for the 4th time in a day, but I think this info might be useful for my wife's notebook, so way to go!
@Astyanax already tried that, with these drivers the High Definition Audio Controller in system devices, is also ghost so nothing to re detect.
In reedit at least 10 people report the same with cards rx480,rx570, rx580 and XFX Dd Ultra II 5700.
@Astyanax already tried that, with these drivers the High Definition Audio Controller in system devices, is also ghost so nothing to re detect.
In reedit at least 10 people report the same with cards rx480,rx570, rx580 and XFX Dd Ultra II 5700.
That'd make for the device being in a pretty messed up state since the graphics driver enumerates seperately to the hd audio controller.
Not bad, ofc this is with newer driver 😛