https://bugs.winehq.org/show_bug.cgi?id=54223
--- Comment #12 from CHECK_1234 CHECK_1234543212345@protonmail.com --- (In reply to Zeb Figura from comment #10)
Does the patch from https://bugs.winehq.org/show_bug.cgi?id=53408#c7 help?
(In reply to Zeb Figura from comment #11)
(In reply to Zeb Figura from comment #10)
Does the patch from https://bugs.winehq.org/show_bug.cgi?id=53408#c7 help?
Which is upstream as part of 8.0-rc4.
⬤ Update 7: DirectX11 to OpenGL Performance Regression Happening Still with Wine-rc4
I manually compiled wine 8.0-rc4 because WineHQ-staging wine repository for Ubuntu in was still in Wine-Staging-rc3.
⬤ Settings:
RX580 locked to 300Mhz core clock and 300Mhz memory clock (By using echo "low"
/sys/class/drm/card0/device/power_dpm_force_performance_level
Quality: Low Resolution: 1280x720 Fullscreen: Unchecked MAX CPU CLOCK SPEED: 2.5Ghz at 0.768V Color Depth: 16 (Increases performance compared to using the Color Depth of "24")
Unigine Heaven Benchmark 4.0 Results:
-------------------------------------------------------------------
Compiled Wine 8.0-rc4 DX11 to OpenGL: Scene 2: 41 FPS Scene 3: 24 FPS
Then at "dlls/wined3d/device.c" I manually removed "case GL_UNIFORM_BUFFER:" and recompiled Wine 8.0-rc4:
Custom Compiled Wine 8.0-rc4 with "case GL_UNIFORM_BUFFER:" Removed, DX11 to OpenGL Scene 2: Around 95 FPS (FPS changing too fast: FPS Reaching over 100 FPS!!!) Scene 3: Around 72 FPS (FPS changing too fast!!!) (This scene seems to be getting worser performance with DirectX11 to OpenGL compared to using DirectX9 to OpenGL for some reason (hopefully this performance regression can be fixed too))
-------------------------------------------------------------------
⬤ Conclusion
I guess this "case GL_UNIFORM_BUFFER:" is causing this DirectX11 to OpenGL Performance Regression and also maybe even wine's default DirectX11 to Vulkan according to comment #0 (winetricks renderer=vulkan, custom compiled wine not working with vulkan for some reason, maybe the way I compiled wine) Performance Regression caused by commit 86f0ae8efb17ce688986971d24c3e25840a2beef https://gitlab.winehq.org/wine/wine/-/commit/86f0ae8efb17ce688986971d24c3e25... for Unigine Heaven Benchmark 4.0.
Sorry for taking too long to test that wine-rc4 was just released, hopefully this performance regression can be fixed by Wine-rc5 for Unigine Heaven 4.0???
⬤ Unigine Heaven 4.0 with DirectX9 to Vulkan (winetricks renderer=vulkan) needing to be fixed???
Also maybe hoping for wine's DirectX9 to Vulkan (winetricks renderer=vulkan) to be fixed (Gives an error box when clicking "RUN" button on "Unigine Heaven Benchmark 4.0" Launcher). But DXVK 2.0's DirectX9 to Vulkan works but there seems to be a performance regression with DXVK 2.0's DirectX9 to Vulkan causing wine's DirectX9 to OpenGL to be faster than DXVK 2.0's Direct X9 to Vulkan according to comment #0.
⬤ Workaround to fix DirectX11 to OpenGL and wine's DirectX11 to Vulkan (winetricks renderer=vulkan) Performance Regression???
I dont know what this "case GL_UNIFORM_BUFFER:" from "dlls/wined3d/device.c" does, but for some reason it is causing this performance regression with DirectX11 to OpenGL (maybe even causing this performance regression with wine's default DirectX11 to Vulkan (winetricks renderer=vulkan) according to comment #0) in Unigine Heaven 4.0 Benchmark.
Maybe a workaround might be maybe removing "case GL_UNIFORM_BUFFER:" from "dlls/wined3d/device.c" entirely from the official wine source code??? Or maybe making it so that "case GL_UNIFORM_BUFFER:" from "dlls/wined3d/device.c" would no be used with OpenGL to DirectX11 or wine's DirectX11 to Vulkan (winetricks renderer=vulkan).
⬤ Hopefully this could be fixed easily!!!
Hopefully this could be fixed easily before wine 8.0 stable gets released. Also maybe hoping for wine's DirectX9 to Vulkan (winetricks renderer=vulkan) to be fixed (Gives an error box when clicking "RUN" button on "Unigine Heaven Benchmark 4.0" Launcher).
-------------------------------------------------------------------
⬤ GOOD NEWS!!!: UPDATE ABOUT COMMENT #8 AND COMMENT #9: USING VULKAN WITH THE COLOR DEPTH OF "16" (PERFORMANCE BOOST!!!) TO BE FIXED IN MESA SO THAT VULKAN NOW WORKS WITH THE COLOR DEPTH OF "16" (PERFORMANCE BOOST!!!) TO INCREASE PERFORMANCE
I MADE AN ISSUE WHERE VULKAN WAS NOT WORKING WITH THE COLOR DEPTH OF "16" AT: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7846
NOW VULKAN WITH COLOR DEPTH OF "16" (PERFORMANCE BOOST!!!) IS NOW GOING TO BE FIXED IN MESA WITH THIS MERGE REQUEST!!!: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20673
SEE THE PERFORMANCE BOOST OF USING THE COLOR DEPTH OF "16" (PERFORMANCE BOOST!!!) WITH VULKAN WITH THIS MERGE REQUEST WHEN I TESTED MSI KOMBUSTOR "(VK) FurMark-MSI" WITH wine-staging 8.0-rc2 COMPARING THE PERFORMANCE OF:
???? Color of Depth "30" (121 FPS) ???? VS ???? Color of Depth "24" (124 FPS) ???? VS ???? Color of Depth "16" (PERFORMANCE BOOST!!!) (144FPS)????
WITH THE COMMENT THAT I MADE AT!!!: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7846#note_1720383
SO PREPARE TO BE ABLE TO IMPROVE PERFORMANCE WITH VULKAN NOW BY BEING ABLE USE THE COLOR DEPTH OF "16" FOR VULKAN!!!
USING THE COLOR DEPTH OF "16" (PERFORMANCE BOOST!!!) EVEN BEATS WINDOWS 10 VULKAN PERFORMANCE ACCORDING TO MY TESTING WITH "Wine-staging 8.0-rc2" MSI KOMBUSTOR "(VK) FurMark-MSI" BENCHMARK!!!:
???? Windows 10: 131 FPS (8 bpc) ???? VS ???? Linux: 124 FPS (Color of Depth "24") VS ????Linux: 144 FPS (Color Depth "16") (PERFORMANCE BOOST!!!) ????
WITH THE OLDER COMMENT THAT I MADE AT: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7846#note_1717152
I CURRENTLY HAVE NO OPTION TO USE THE COLOR DEPTH OF "16" IN WINDOWS 10 TO GET THIS PERFORMANCE BOOST!!!