I have some general questions.

[aaf2tbz]

1. Would you at all be interested in someone adding an arm64 / FEX version of this program. I would provide the necessary build scripts for xtajit (i386 /WOW64) and xtajit64 (Aarch64 -> arm64EC) with FEX core and the necessary build commands. It's a lot more complicated because it is direct binary translation and it's a lot harder to upgrade alongside newer Wine releases.

2. My current wine under MetalSharp (See my account for more information) is outdated. It is wine 11.5. I don't like taking projects and using them as my own so seeing that I help out in this repository I was curious if I could use WineForge 11.16 for my program. I'm a little bit tired of 11.5's instability in some cases. Plus you have added d3dmetal into wine directly which i completely failed to do when I started my project. I would be happy to contribute everything i know about wine here, regardless of whether I can use it or not.

3. Why don't you bundle in DXMT? The license is LGPL-2.1 which means it's free to bundle in with the software, at least any release 0.80.0 and below. I'm also finishing my own DXMT d3d12 integration right now, so would be happy to add that here when it's completed, and it would stay under LGPL-2.1 since I used the 0.80.0 release to integrate all of it. Wouldn't have to worry about any licensing conflicts.

Anyways I know this is a lot to ask about but just curious in what you're doing here and I support these kinds of projects greatly.

[Alien4042x]

I’m definitely interested in collaborating, especially around FEX.

I already have the 64-bit side working in my current implementation, but I’m still having problems with 32-bit applications. For example, the 32-bit Steam installer doesn’t work yet, so I’d be very interested to see how you’re handling the i386/WoW64 side with FEX and how you got that working.

If your implementation can help solve that part, I’d be happy to work together and see what could be integrated into WineForge.

For contributions, the main thing I care about is that changes are focused, reviewable, properly understood, and actually tested. I don’t want to merge large amounts of generated or experimental code just because they compile — especially in sensitive areas like FEX/WoW64 where it’s very easy to introduce subtle problems.

As for using WineForge in MetalSharp, I don’t have a problem with that. The licensing already defines what can and can’t be done, so it’s not really something I need to “allow.” I’d just appreciate clear attribution and a clear distinction between WineForge itself and any changes or additions made specifically for MetalSharp.

Regarding DXMT, I already bundle it through the WineForge Launcher, so it’s already included and available there.

[aaf2tbz]

Perfect! Thanks for the reply. I will look into the i386 / wow64 side of wineforge with FEX for you. Currently I have this working under my arm64 - FEX wine. It's called VKMT-Wine under my profile, the steam installer works i'm just fixing the handoff between the 32bit steamsetup.exe -> 64bit steam.exe, it's a little janked, and it's also wine 11.12 so I'll need to do some upgrades to bring it over to your latest version. Feel free to use it as a point of reference. (I'm currently in the process of finalizing it). Other than that i'm excited to see what we can do here. Thanks for the DXMT info, I only asked because your readme states 'DXMT runtime binaries are maintained separately and are not bundled in this source repository'.

[Alien4042x]

Thanks! I took a closer look at your FEX/WoW64 implementation. Unfortunately, it's too tightly coupled to specific application paths for what I'm trying to achieve with WineForge, so I won't be integrating it.

[aaf2tbz]

No problem! It's more of a proof of concept than anything. I'll be looking into contributing here once I finish some work I've been doing. Thanks for doing what you do!

[Alien4042x]

But we need to figure something out. We really need that 32-bit to 64-bit translation.

[aaf2tbz]

Definitely. I have it pulled in now and working on it generally. For MetalSharp, I usually build -with-vulkan. Curious as to why you chose to not build with vulkan included.