NoXPhasma

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.

If Amazon is unable to make sure you got no fake Plus if they are the seller, how in the world would they make sure the Select is no fake?

I've used df -h and that showed only this three partitions. I've only skipped the tmpfs mounts.

Additionally, to what was already said, the size of storage is giving in Decimal (1000B based) while after formatting it is often shown in Binary (1024B based), which makes the storage look smaller, which it isn't.

And the most of the storage is coming from software stored in your home, not the OS itself. The OS only occupies around 3.3GB on the 5GB root partition:

/dev/nvme0n1p4  5.0G  3.3G  1.5G  69% /
/dev/nvme0n1p6  230M   41M  173M  19% /var
/dev/nvme0n1p8  466G  115G  351G  25% /home

They are both exactly the same, Select is just a rebrand of Amazon. Don't buy Select unless it is cheaper. And yes they work fine, have the Evo Plus 512.

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%

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.