NoXPhasma

joined 1 year ago
[–] [email protected] 3 points 2 months ago* (last edited 2 months ago)

The ultimate goal of the WIneHQ team is to have their own fully DX12 implementation. The reason why vkd3d-proton exists is that Valve didn't want to wait for it to mature and AFAIK they did have differences in what should be included in vkd3d. Which is why they don't work on the same project.

[–] [email protected] 6 points 2 months ago (2 children)

I'm pretty sure vkd3d-proton does not rebase from vkd3d.

[–] [email protected] 4 points 4 months ago (2 children)

@[email protected] I've found this (scroll down to #5 if it won't scroll automatically). It shows some tools that can be used to change DMI information for different Manufacturers.

[–] [email protected] 11 points 4 months ago (4 children)

This is part of the motherboard and can only be changed with specific tools from the manufacturer. Back in the days there was AMIDEDOS as a dos tool to change it in AMI Bios. You would need to find out, what tool can be used to change it in your UEFI. However, it's possible that those tools are not available to the public.

[–] [email protected] 8 points 1 year ago (1 children)

xone needs to blacklist the xpad kernel driver, which supports all kinds of Xbox controllers, to prevent it from high jacking Xbox One controllers. You will have to install xpad-noone, which is xpad but without Xbox One support and can coexist next to xone.