February 2024 - Wine-GitLab

[PATCH v2 0/1] MR5145: Draft: opengl32: speed up wow64 mapping
by Etaash Mathamsetty (＠etaash.mathamsetty) Feb. 24, 2024

Feb. 24, 2024

My hardware is Ryzen 7 4700u with the integrated graphics Flatout (Direct3D 9): 3 fps to 40 fps (renders correctly) Unigine Heaven (OpenGL): ~17 fps (renders correctly) Unigine Heaven (Direct3D 9): 20-30 fps (renders correctly) Unigine Heaven (Direct3D 11): 20-30 fps as well (renders correctly) Elder Scrolls IV (Direct3D 9): 20 fps (broken intro videos, ingame rendering looks correct, old mapping code works just fine in the intro videos) BeamNG Tech Demo 0.3 (Direct3D 9): 2 fps (renders correctly, but still runs poorly) These numbers are from my memory, I will update them with the more accurate numbers when I get home. Unfortunately, we lose the ability to get lucky with the mapping just happening to be in the 32 bit range. -- v2: opengl32: speed up wow64 mapping https://gitlab.winehq.org/wine/wine/-/merge_requests/5145

2 1

[PATCH 0/1] MR5145: Draft: opengl32: speed up wow64 mapping
by Etaash Mathamsetty (＠etaash.mathamsetty) Feb. 24, 2024

Feb. 24, 2024

My hardware is Ryzen 7 4700u with the integrated graphics Flatout (Direct3D 9): 3 fps to 40 fps (renders correctly) Unigine Heaven (OpenGL): ~17 fps (renders correctly) Unigine Heaven (Direct3D 9): 20-30 fps (renders correctly) Unigine Heaven (Direct3D 11): 20-30 fps as well (renders correctly) Elder Scrolls IV (Direct3D 9): 20 fps (broken intro videos, ingame rendering looks correct, old mapping code works just fine in the intro videos) These numbers are from my memory, I will update them with the more accurate numbers when I get home. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5145

2 2

[PATCH v8 0/8] MR662: vkd3d-shader/ir: Introduce a better CFG structurizer, part 2.
by Giovanni Mascellani (＠giomasce) Feb. 24, 2024

Feb. 24, 2024

~~This applies on top of !656, the last three commits belong here.~~ -- v8: vkd3d-shader/ir: Sort each loop by block label. vkd3d-shader/ir: Dump the loops in the control flow graph. vkd3d-shader/ir: Keep track of loops by header block. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/662

3 9

[PATCH 0/1] MR5146: d3dcompiler: Enable semantic naming mapping in compatibility mode.
by Nikolay Sivov (＠nsivov) Feb. 24, 2024

Feb. 24, 2024

This was implemented in vkd3d 1.10. Another known feature that has to be enabled with compatibility flag is d3d9 style sampling functions. We currently don't do that, making them supported unconditionally. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5146

2 1

Re: [PATCH v2 0/1] MR5140: wbemprox: Protect tables with a critical section. - approved
by Alexandre Julliard (＠julliard) Feb. 23, 2024

Feb. 23, 2024

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5140

1 0

Re: [PATCH v2 0/1] MR5100: advapi32/tests: Use CRT allocation functions. - approved
by Alexandre Julliard (＠julliard) Feb. 23, 2024

Feb. 23, 2024

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5100

1 0

Re: [PATCH v4 0/1] MR5134: server: Use the startup info to connect the process winstation. - approved
by Alexandre Julliard (＠julliard) Feb. 23, 2024

Feb. 23, 2024

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5134

1 0

Re: [PATCH v2 0/5] MR5135: Explicitly request debug info in critical sections. - approved
by Alexandre Julliard (＠julliard) Feb. 23, 2024

Feb. 23, 2024

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5135

1 0

[PATCH v3 0/2] MR661: Draft: tests: Introduce custom test driver.
by Francisco Casas (＠fcasas) Feb. 23, 2024

Feb. 23, 2024

Basically !427, but in the form of a custom test driver script. If I am not mistaken, for the driver script to run properly it is necessary to run "autoreconf" in the source directory and call the configure script again in the build directory. The output when running tests would be the same we currently have except for tests that don't PASS, in that case, detailed information for each failing line will appear. Make a failing test to try it! -- v3: tests: Get detailed information on failing tests. tests: Copy autotool's testsuite driver script. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/661

2 2

[PATCH 0/1] MR5143: taskschd: Return success from Principal_put_RunLevel.
by Vijay Kiran Kamuju (＠infyquest) Feb. 23, 2024

Feb. 23, 2024

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=49877 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5143

2 1