NoXPhasma

joined 1 year ago
[–] NoXPhasma@lemmy.world 3 points 3 weeks ago* (last edited 3 weeks 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.

[–] NoXPhasma@lemmy.world 6 points 3 weeks ago (2 children)

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

[–] NoXPhasma@lemmy.world 4 points 2 months ago (2 children)

@vaionko@sopuli.xyz 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.

[–] NoXPhasma@lemmy.world 11 points 2 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.

[–] NoXPhasma@lemmy.world 3 points 1 year ago

I've never had that issue that deleted ISOs would stay on the USB, not sure how you've managed to achieve that. Maybe you didn't actually delete the files but put them to the recycle bin?

[–] NoXPhasma@lemmy.world 2 points 1 year ago

but I have used the video encode hardware on AMD cards via VAAPI and it was competent and much faster than x264/x265 on the CPU.

Yes, it's faster than the CPU, which is no surprise, but the quality is incredibly worse than NVENC. I switched to AMD earlier this year and I knew that the AMD video encoder wouldn't match NVENC, but the difference is much bigger than I've ever thought.