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%

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

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.

deleted by creator

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.

Posting the required version to run the game is not trivial, as this is nothing we can just know, and it can also change with game updates. There is the Steam Deck verification information, which includes a Proton version, but this information is not reliable at all. Valve set Proton Experimental on all games that have not being tested, even on Linux native(!), so we can not take that.

However, we are thinking of changes and collecting ideas at the moment and any constructive idea and critique is welcome. My personal idea about the working Proton versions to show is to simply have a graph, showing the available proton versions with a color code, depending on the reports and their rating. For example:

And yes, people are reporting incorrect fixes, but this is the nature of user content. And it’s impossible to curate them all, it’s way too many. But you can always report a false/dangerous report on the discord or IRC (I wish we’ve had a report button on the page).

The rating is calculated by the report of the users, there is no manual rating done. GTAV works for most people, but some, so it ends up being Gold.

However, these Medal ratings are carried over from the WineHQ rating, when ProtonDB was nothing more than a spreadsheet on Google Docs and was also used when Ratings were considered by the reporters itself. But this turned out to be a bad idea, as people tend to give platinum ratings, despite naming issues in their reports.

So the attempt was to remove the manual rating and instead ask the users about their experience with several talking points and consider by that a rating. This would still use the old medal system, which of course does not work well for such system. That’s why a new tier system, which is more a representation between very good and very bad, was created, and you can see it on the dashboard (Change the Rating System to ProtonDB Click Play). However, this was considered as an internal test, but then the main developer was pulled away from ProtonDB for other work and all went basically to a hold.

Now the developer is back at work on ProtonDB and this will hopefully lead to a new and better rating system.

I hope this will shed some light on why it is what it is, and that no one is really happy about it.

Source: I’m one of the administrators on the ProtonDB discord.