November 2024 - Wine-Devel - list.winehq.org

How could I use my own build vkd3d in wine ?

by zhengxianwei

I want to try modifying and building vkd3d myself, but I’m not sure how to make Wine use my custom-built vkd3d. My development environment is Ubuntu 24.04 + x64.

Nov. 26, 2024

Wine staging 9.22 release

by Alistair Leslie-Hughes

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 9.22 (350 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * ntdll: Implement HashLinks field in LDR module data. * ntdll: Use HashLinks when searching for a dll using the basename. Removed (No longer required). * None Added: * None Updated: * vkd3d-latest Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

Nov. 23, 2024

Re: How to use DLL files from vkd3d-proton in Wine?

by zhengxianwei

Yeah, thank you , it now work. There are other crashes, but they seem to be seperate issue. On Fri, Nov 22, 2024 at 12:32 AM Gabriel Ivăncescu <gabrielopcode(a)gmail.com> wrote: > On 21/11/2024 13:59, zhengxianwei wrote: > > I am a beginner with Wine and currently using it to run Photoshop 23. > > > > > > I noticed that vkd3d seems to lack support for Tiled Resource, which > > causes Photoshop’s compatibility check to fail in displaying the correct > > GPU information. > > > > > > I found that vkd3d-proton appears to implement this feature, so I > > compiled vkd3d-proton and copied the resulting d3d12.dll and > > d3d12core.dll directly into Wine’s directory. I also ensured that the > > required d3d12.dll was loaded correctly. > > > > > > However, when launching Photoshop, it crashes when using certain > > swapchain features. > > > > > > Setting aside the swapchain crash for now, is my approach of directly > > using the d3d12.dll generated by vkd3d-proton correct? > > > > > > > > > > AFAIK, you also need dxgi.dll from DXVK. If it still crashes with that, > it's probably a bug somewhere. >

Nov. 22, 2024

Re: How to use DLL files from vkd3d-proton in Wine?

by zhengxianwei

I directly copied all the DLLs compiled from DXVK into the Wine environment following the README instructions, but the error seems to be the same - it still crashed on swapchain . I googled a bit and found that DXGI is responsible for managing some resources related to the Vulkan swapchain. Could it be that I didn't install the DXVK DLLs into wine directly. On Fri, Nov 22, 2024 at 12:32 AM Gabriel Ivăncescu <gabrielopcode(a)gmail.com> wrote: > On 21/11/2024 13:59, zhengxianwei wrote: > > I am a beginner with Wine and currently using it to run Photoshop 23. > > > > > > I noticed that vkd3d seems to lack support for Tiled Resource, which > > causes Photoshop’s compatibility check to fail in displaying the correct > > GPU information. > > > > > > I found that vkd3d-proton appears to implement this feature, so I > > compiled vkd3d-proton and copied the resulting d3d12.dll and > > d3d12core.dll directly into Wine’s directory. I also ensured that the > > required d3d12.dll was loaded correctly. > > > > > > However, when launching Photoshop, it crashes when using certain > > swapchain features. > > > > > > Setting aside the swapchain crash for now, is my approach of directly > > using the d3d12.dll generated by vkd3d-proton correct? > > > > > > > > > > AFAIK, you also need dxgi.dll from DXVK. If it still crashes with that, > it's probably a bug somewhere. >

Nov. 22, 2024

Re: How to use DLL files from vkd3d-proton in Wine?

by Gabriel Ivăncescu

On 21/11/2024 13:59, zhengxianwei wrote: > I am a beginner with Wine and currently using it to run Photoshop 23. > > > I noticed that vkd3d seems to lack support for Tiled Resource, which > causes Photoshop’s compatibility check to fail in displaying the correct > GPU information. > > > I found that vkd3d-proton appears to implement this feature, so I > compiled vkd3d-proton and copied the resulting d3d12.dll and > d3d12core.dll directly into Wine’s directory. I also ensured that the > required d3d12.dll was loaded correctly. > > > However, when launching Photoshop, it crashes when using certain > swapchain features. > > > Setting aside the swapchain crash for now, is my approach of directly > using the d3d12.dll generated by vkd3d-proton correct? > > > > AFAIK, you also need dxgi.dll from DXVK. If it still crashes with that, it's probably a bug somewhere.

Nov. 21, 2024

How to use DLL files from vkd3d-proton in Wine?

by zhengxianwei

I am a beginner with Wine and currently using it to run Photoshop 23. I noticed that vkd3d seems to lack support for Tiled Resource, which causes Photoshop’s compatibility check to fail in displaying the correct GPU information. I found that vkd3d-proton appears to implement this feature, so I compiled vkd3d-proton and copied the resulting d3d12.dll and d3d12core.dll directly into Wine’s directory. I also ensured that the required d3d12.dll was loaded correctly. However, when launching Photoshop, it crashes when using certain swapchain features. Setting aside the swapchain crash for now, is my approach of directly using the d3d12.dll generated by vkd3d-proton correct?

Nov. 21, 2024

Re: Pending Reviews page

by Rémi Bernon

On 11/14/24 14:38, Alexandre Julliard wrote: > Rémi Bernon <rbernon(a)codeweavers.com> writes: > >> On 11/14/24 11:42, Alexandre Julliard wrote: >>> Folks, >>> In our grand tradition of shaming people into doing work, after the >>> Regressions page I'm proud to present the Pending Reviews page: >>> https://source.winehq.org/reviews >>> As with the regressions page, the goal should be to *not* be number >>> one >>> on the list. But feel free to congratulate Huw anyway ;-) >>> Note that the list is a little overestimated, commenting on the diff >>> counts as a review but simply adding a note doesn't, so you may see some >>> MRs in your list that you have actually commented on already. If people >>> find this thing useful we can try to make it smarter. Feedback is >>> welcome! >>> >> >> Nice! >> >> Does it mean there's now a difference between a MR assigned to you and >> one that isn't assigned? :) > > Not much difference, but hopefully making the unassigned MRs more > visible will encourage people to voluntarily assign themselves to the > ones where they feel they can help. > I think many times it's difficult to look at some unknown code area and believe you can give some meaningful guidance. In addition it seems like that assuming reviewer-ship and approving a MR is considered by many as a big deal, whereas I'm not sure it should be so much. I don't have much suggestions on how to make it less overwhelming but I wonder if using Gitlab merge request tags could help us give more detailed feedback to contributors, and perhaps offer an intermediate step for drive-by developers feedback. We have the Draft state already, and the page already kind of have some another class of 'pending further action' MR, although they are not explicitly classified as such on Gitlab. We could have some additional tags like 'needs tests', or whatever else would useful. I've also been told, and I tend to agree, that it would be good to consider having some sort of 'Acked-by' status, where a MR has been looked at, at least briefly, and looks good but needs further review (not necessarily by the same person). -- Rémi Bernon <rbernon(a)codeweavers.com>

Nov. 19, 2024

Re: Pending Reviews page

by Alexandre Julliard

Rémi Bernon <rbernon(a)codeweavers.com> writes: > On 11/14/24 11:42, Alexandre Julliard wrote: >> Folks, >> In our grand tradition of shaming people into doing work, after the >> Regressions page I'm proud to present the Pending Reviews page: >> https://source.winehq.org/reviews >> As with the regressions page, the goal should be to *not* be number >> one >> on the list. But feel free to congratulate Huw anyway ;-) >> Note that the list is a little overestimated, commenting on the diff >> counts as a review but simply adding a note doesn't, so you may see some >> MRs in your list that you have actually commented on already. If people >> find this thing useful we can try to make it smarter. Feedback is >> welcome! >> > > Nice! > > Does it mean there's now a difference between a MR assigned to you and > one that isn't assigned? :) Not much difference, but hopefully making the unassigned MRs more visible will encourage people to voluntarily assign themselves to the ones where they feel they can help. -- Alexandre Julliard julliard(a)winehq.org

Nov. 14, 2024

Re: Pending Reviews page

by Rémi Bernon

On 11/14/24 11:42, Alexandre Julliard wrote: > Folks, > > In our grand tradition of shaming people into doing work, after the > Regressions page I'm proud to present the Pending Reviews page: > > https://source.winehq.org/reviews > > As with the regressions page, the goal should be to *not* be number one > on the list. But feel free to congratulate Huw anyway ;-) > > Note that the list is a little overestimated, commenting on the diff > counts as a review but simply adding a note doesn't, so you may see some > MRs in your list that you have actually commented on already. If people > find this thing useful we can try to make it smarter. Feedback is > welcome! > Nice! Does it mean there's now a difference between a MR assigned to you and one that isn't assigned? :) -- Rémi Bernon <rbernon(a)codeweavers.com>

Nov. 14, 2024

Pending Reviews page

by Alexandre Julliard

Folks, In our grand tradition of shaming people into doing work, after the Regressions page I'm proud to present the Pending Reviews page: https://source.winehq.org/reviews As with the regressions page, the goal should be to *not* be number one on the list. But feel free to congratulate Huw anyway ;-) Note that the list is a little overestimated, commenting on the diff counts as a review but simply adding a note doesn't, so you may see some MRs in your list that you have actually commented on already. If people find this thing useful we can try to make it smarter. Feedback is welcome! -- Alexandre Julliard julliard(a)winehq.org

Nov. 14, 2024