Invest now!

That’s exactly what I use, works like a charm.

Short answer: Not enough bad reports, compared to older good ones.

Long answer: ProtonDB only takes the latest report of each reporter into the rating. Which means if old reporters come back with a negative report, it will shift the rating quicker, as if only new negative appear.

This game is in a situation where it got a lot of good reports, and in the last 6 months there were less than 80 negative. But the trending tier is already bronze. Probably needs just a few more reports to give it the last push. You can also see in API answer, that the confidence of the good rating is strong due to the many good reports.

Nope, response by a proton dev was

Not ready yet

https://youtu.be/OYt1kqDNlMY

Time for DP to be used on more devices, like TVs and such.

Yes, that was the original name, back in the 90’s.

“oh, i don’t know what this native english speaker is saying, i guess english is still a skill i’m working on”

I’m no native English speaker as well, and that’s how I often think as well. In my mother tongue I know so many words, their meaning and their sound. In English, however, I’m still learning new words now and then, and it opens my world to the language every time. This is true for dialects as well.

Learning a new language is quite hard in the beginning, but it’s so satisfying and world opening when you start to actually use a new language.

edit Ohh, and sorry for my bad English ;)

deleted by creator

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.

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.