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.

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

@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.

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.

SFSE works fine for me, no issues at all. Make sure you download the latest version, to be compatible with the latest Starfield update.

I’ve placed the dll and the exe next to the Starfield.exe in the game folder. And changed the Steam launch parameter to

bash -c 'exec "${@/Starfield.exe/sfse_loader.exe}"' -- %command%

GTAV works better with AMDVLK, as one of the very few games out there. You could give that a shot, but be aware that AMDVLK often gets selected as default, so having AMD_VULKAN_ICD=RADV in your global Env. Variables are a good idea.

And then launching GTAV with AMD_VULKAN_ICD=AMDVLK %command%.

I don’t know if it’s random, the CPU scheduler still decides what thread to use. It will have its own semantics, but I don’t know on what those are based.

It’s not just random, it simply does not even work. Because they set this:

+/*Preferred Core featue is supported*/
+static bool prefcore = true;

And later in the code they do the if condition wrong:

+	if (prefcore)
+		WRITE_ONCE(cpudata->highest_perf, AMD_PSTATE_PREFCORE_THRESHOLD);
+	else
+		WRITE_ONCE(cpudata->highest_perf, AMD_CPPC_HIGHEST_PERF(cap1));

if should look like this:

+	if (prefcore)
+		WRITE_ONCE(cpudata->highest_perf, AMD_CPPC_HIGHEST_PERF(cap1));
+	else
+		WRITE_ONCE(cpudata->highest_perf, AMD_PSTATE_PREFCORE_THRESHOLD);

There is probably even more wrong, looking at the code quality, but this at least makes the preferred core work.

AMD patches for preferred core (prefer those cores which can clock higher) are a mess and ended up not working because of a wrong if condition. Showing that no one at AMD even tested it before submitting. The programmer in the video complains about AMDs developers being incompetent and shows how it’s fixed.