December 2023 - Wine-GitLab

Re: [PATCH v4 0/6] MR4522: winewayland.drv: part 10.3: Vulkan swapchain presentation
by Snowiiii (＠Snowiiii) Dec. 3, 2023

Dec. 3, 2023

On Sun Dec 3 09:10:50 2023 +0000, Shmerl wrote: > Just sharing a test result (running Cyberpunk 2077 with winewayland > using Wine+esync+vkd3d-proton). > ![cyberpunk_wayland](/uploads/ffaf0f3ec94fe2e8d921d97d03cb23d7/cyberpunk_wayland.jpg) > Note: Mouse input is broken as expected. Adaptive sync / VRR works fine. > DE: KDE Plasma 5.27.9. can you compare native wayland vs Xwayland ? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4522#note_54771

1 0

Re: [PATCH v4 0/6] MR4522: winewayland.drv: part 10.3: Vulkan swapchain presentation
by Shmerl (＠shmerl) Dec. 3, 2023

Dec. 3, 2023

Just sharing a test result (running Cyberpunk 2077 with winewayland using Wine+esync+vkd3d-proton). ![cyberpunk_wayland](/uploads/ffaf0f3ec94fe2e8d921d97d03cb23d7/cyberpunk_wayland.jpg) Note: Mouse input is broken as expected. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4522#note_54769

1 0

Re: [PATCH v4 0/6] MR4522: winewayland.drv: part 10.3: Vulkan swapchain presentation
by Shmerl (＠shmerl) Dec. 3, 2023

Dec. 3, 2023

FYI: Tried running Cyberpunk 2077 with this (Wine + vkd3d-proton) and it's just producing a black screen. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4522#note_54768

1 0

[PATCH 0/4] MR4586: oleaut32/tests: Remove some of the function availability checks.
by Nikolay Sivov (＠nsivov) Dec. 3, 2023

Dec. 3, 2023

Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4586

2 4

[PATCH v2 0/2] MR4585: Draft: dsdmo: Add stubs for distortion and gargle effects
by Vijay Kiran Kamuju (＠infyquest) Dec. 3, 2023

Dec. 3, 2023

Add stubs for distortion and gargle effects in dsdmo. -- v2: dsdmo: Add Gargle effect stub. https://gitlab.winehq.org/wine/wine/-/merge_requests/4585

2 2

[PATCH v15 0/1] MR4428: cfgmgr32: Add CM_Register_Notification stub.
by Etaash Mathamsetty (＠etaash.mathamsetty) Dec. 2, 2023

Dec. 2, 2023

Fixes the crash before the loading screen in Farlight 84 when not running on a steam deck. -- v15: cfgmgr32: Add CM_Register_Notification stub. https://gitlab.winehq.org/wine/wine/-/merge_requests/4428

2 1

[PATCH 0/2] MR4585: Draft: dsdmo: Add stubs for distortion and gargle effects
by Vijay Kiran Kamuju (＠infyquest) Dec. 2, 2023

Dec. 2, 2023

Add stubs for distortion and gargle effects in dsdmo. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4585

4 4

Re: [PATCH v13 0/1] MR4428: cfgmgr32: Add CM_Register_Notification stub.
by Vijay Kiran Kamuju (＠infyquest) Dec. 2, 2023

Dec. 2, 2023

Please add the function signature to the header file, add missing definitions. Also correct the function signature in the code. https://learn.microsoft.com/en-us/windows/win32/api/cfgmgr32/nf-cfgmgr32-cm… -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4428#note_54757

1 0

Re: [PATCH v3 0/1] MR499: tests: Print the line number of the probe when a test fails.
by Petrichor Park (＠petrathekat) Dec. 2, 2023

Dec. 2, 2023

On Sat Dec 2 17:59:48 2023 +0000, Petrichor Park wrote: > Doing this would require changes to other test harness machinery; > specifically it would stop printing any context if the shader fails to > compile, or if there's some other problem. > It would require a lot of changes to everything the harness could handle > to provide better feedback in each case; I think that's kind of out of > scope of this MR and probably out of scope for the harness in general. (the change is to remove the `vkd3d_test_push_context` call on L1439, and then I'd need to remove the matching `vkd3d_test_pop_context` call that's somewhere) -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/499#note_54756

1 0

Re: [PATCH v3 0/1] MR499: tests: Print the line number of the probe when a test fails.
by Petrichor Park (＠petrathekat) Dec. 2, 2023

Dec. 2, 2023

On Sat Dec 2 17:59:48 2023 +0000, Giovanni Mascellani wrote: > Right now this prints both the line where the section starts and the > line there the `probe` directive here. This feels a bit too much. Doing this would require changes to other test harness machinery; specifically it would stop printing any context if the shader fails to compile, or if there's some other problem. It would require a lot of changes to everything the harness could handle to provide better feedback in each case; I think that's kind of out of scope of this MR and probably out of scope for the harness in general. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/499#note_54755

1 0