I shall yoink that, thank you very much.

Not a bad idea actually, totally didn’t think about that.

Maybe even a PCIe pass through to a VM could do the trick if you’re desparate lol (with Linux living in a separate drive)

Orrrr maybe even try FreeBSD… (or mac OS, but eww gross don’t test that)

The only thing I can think of is to try the drives in a different system and see how they behave (same OS and configuration).

If they behave the same then that rules out everything except the drives themselves and the OS.

Considering how you mentioned the behavior is better in Windows, it sounds like a software issue, but you never know until you try.

FWIW I’ve also had memory issues with XMP.

Turns out that ASUS firmware is omega pepega and decided to go against AMD’s specifications even for XMP profiles.

CLDO VDDP was stuck at the same voltage as SOC. Per AMD it has to be up to VSOC - 0.1V

So, after manually setting that, and other VDDP and VDDG voltages, it magically started working perfectly.

So do check voltages anyway even if you found a bad stick. Mine endured through the crappy firmware thanks to it being Samsung B-die.

Also check this for more info in general (I recommend this even if you won’t OC, just the memtest alone is a huge section)

https://github.com/integralfx/MemTestHelper/blob/oc-guide/DDR4 OC Guide.md

I tested with OCCT to find even more errors, so either do that in a mini windows environment or do one of the Linux tests to check memory some more. Memtest86+ isn’t enough.

I remember way back, around 2013, asking Gigabyte Mobile for the kernel source of one of their devices (Mika M3) via their business support.

Needless to say, they obliged! They uploaded it and then gave a link to an FTP server and credentials to use it.

So sometimes it’s just worth asking.

I couldn’t compile it fwiw, because it was missing key Mediatek components, but eh, what can you do…

It kind of still is because of Webview2. Games such as Forza Motorsport (not that you’d want to play that crap) depend on it for Xbox login purposes even if you bought the game on Steam. The game depends on the system Edge libraries and doesn’t ship its own.

Display and processor? If the answer is yes or maybe, then Doom can run on it.

First of all, thank you very much for your service.

Secondly, you’re crazy lmao

I am pretty sure TianoCore is also used by AMD systems as a reference as well.

Here’s a similar situation that happened in 2019 at Lenovo’s site

https://support.lenovo.com/cl/es/solutions/LEN-22660

AMD systems are listed as well.

As for most board vendors nowadays, I think they barely do anything with the code itself and just create the setup utility and boot logos. It is highly likely that they’re affected too.

Aren’t AMI, Insyde and Phoenix providers for 98% of PC (be it board or OEM) vendors though?

And AFAIR, TianoCore is basically used everywhere by everyone as a base except maybe Apple.

Come play Unreal with us then hehehe

If you’re so sure senator, why don’t you back it up with a source?

I had bad grades in maths. I do programming myself. Not for a living but out of passion.

They’re not necessarily related one to another. Sure, there is maths involved, but it’s not integral. What is integral, is digital logic. That is the most fundamental aspect.

I don’t think that’s gonna work because this is a thing that he needs

https://github.com/elFarto/nvidia-vaapi-driver

You’re welcome! :)

I’ll try to make sure it works on Linux too!

You are correct! You have to put the dinput8 overrides for the plugin (ASI) loader so that the widescreen fix and other stuff can load. (This is the same for all Black Box NFS games basically)

Also, if you’re installing from the original media, you have to update it to 1.3 and then put the no cd patch. In this case I can only recommend the MrDJ repack because it does this already.

However, I highly recommend updating the WS fix and checking out now and then for updates because we do still maintain and develop it. (Not very often but hey, life is life)

That being said, I am also working on improving another plugin of mine, called XtendedInput, which brings native XInput to the game. I’ve already tested it with the Steam Controller and it works nicely. It’s currently a bit fiddly for MW because I hadn’t implemented ingame configuration, so you do have to edit ini files for custom maps and deadzones. (Hopefully I will someday, right now I am stuck on other stuff)

It needs to be accurate and fast, indeed. The code being old isn’t a problem unto itself, but rather the side effects of it.

It is fine for all intents and purposes today. But, there is some inherent difficulty associated with decisions brought years ago when some of the code was originally written, making portability quite a challenge.

I wasn’t making a comment on its age, mind you. I don’t necessarily think it’s that big of a problem and probably can be fixed easily. If anything, it has gotten way better thanks to the departure from the plugin system and various other optimizations over the years.

Well, stenzek is the developer of DuckStation and the person behind the new Qt UI and many new fixes on the backend of PCSX2.

But, I will agree that we do need a new emulator. The emulator called “Play!” is a really good candidate and looks promising. Seeing how it runs on ARM beautifully, I can’t wait to see how far it goes.

PCSX2 runs fine for most people today, but the foundation is a bit too old for its own good. This is why you don’t see too many ports of PCSX2 to other plaforms. They have improved massively by ditching the entire plugin system a few years ago, but that alone isn’t enough to make it more portable and easy to run.

While I understand that Wayland is broken for the purpose of PCSX2, I am unfortunately biased against the developers here due to the horrible experiences I had with them.

If anyone will take up the task of fixing this, be warned that they absolutely do not cooperate with you on the PRs that they receive.