Of the other changes that stand out in this new version: The driver is used in the WSL2 layer to run graphical Linux applications on Windows.Ĭontrollers Intel GPUs are enabled by default to support Adaptive-Sync (VRR), allowing you to adaptively change your monitor's refresh rate for smooth, stutter-free output.įor EGL, the "dma-buf feedback" mechanism is implemented, which provides additional information about the available GPUs and allows you to increase the efficiency of data exchange between the primary and secondary GPUs, for example, to organize output without intermediate buffering. The classic xlib library has been excluded from the main build, instead it is recommended to use the gallium-xlib variant.Īlso, we can find that in this new version of Mesa 22.0 the D3D12 Gallium driver with an OpenGL layer on top of the DirectX 12 API (D3D12) provides compatibility with OpenGL ES 3.1. In addition to this “Amber” branch also moved SWR controller, which offered an OpenGL software rasterizer based on the Intel OpenSWR project.
Hi kd-11, thanks for your report, this issue has been solved, the fix has been released in the current driver.The new version of Vulkan 1.3 has already been released and these are its newsĪnother novelty that stands out is that the classic OpenGL drivers that do not use the Gallium3D interface has been moved from the main Mesa composition to a separate “Amber” branch. Hello, thanks for your report, we will investigate this. The sample works fine on all other drivers I have tried. The error is not real, as can be demostrated with the attached sample and source code. When the texture is created with mutable storage, readback works but when immutable is used it does not.Īlso note that while the trigger is a pack operation, setting the unpack state to swap bytes also will cause the GL_OUT_OF_MEMORY error. Compiled binary is provided for convenience as well as the source. A sample application is attached which attempts to isolate the problem. The core of the problem is that when a texture is created with immutable storage, pixel transfer operations with endianness swap will always fail with GL_OUT_OF_MEMORY. I have tested this on several AMD cards from the 7000 series to the RX 480 and 580. I have encountered a rather interesting bug with pixel transfer operations.
Here's the discussion for those interested: ĭiscussion transcription for those who can't open the link:
Please update your driver to Adrenalin 19.4.3 or newer. This fix first shipped on AMD drivers 19.4.3, so you should update your drivers to at least that version if you intend to use RPCS3 with OpenGL and you have an AMD GPU.įor those who don't get to see this piece of information, RPCS3 should throw a fatal error if this bug is hit on older drivers and tell users Memory transfer failure (AMD bug). This bug impacted RPCS3's performance on AMD GPUs while using OpenGL because pixel transfer operations with endianness swap on the GPU always failed on the affected drivers, so we had to manually byteswap texel data on the CPU. AMD just finally fixed one of the driver bugs u/kd-11 (our lead graphics developer) reported to them exactly 1 year ago.