I shall yoink that, thank you very much.

I honestly vastly prefer using IDA and Windows specific tools (x64dbg) over gdb. IDA can interface with gdb so it can act as a frontend which can be handy for visualization.

I have the same issue on one of the controllers.

There are some hall effect sensor kits on Aliexpress but that requires extensive work to set up and install.

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.

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.

This goes for inter-developer communication too. Be nice to one another. Someone just wants to help sometimes.

What?

1. Power management on certain chips is simply better than anything Linux has to offer (AMD Zen+ mobile for instance)
2. Modular driver architecture with drivers that aren’t complete jank to manage and install. A lot of people see this as a pain point, but in reality it’s not such a bad thing, especially nowadays.
3. This is a given, but as lots of stuff runs on Windows (namely older games), you can only really make stuff for Windows on Windows. So if you need to develop Win32 software, you really have to use Visual Studio for proper development. Mingw cross compile exists, I know, but that’s never going to be as good.

Number 3 is keeping me on Windows. I make mods for old games and I need Visual C++. I almost got the compiler to run under Wine but who knows how it would behave if it did run.

Jak and Daxter is still theirs.

Well, Cross Duel was something completely unique and was more like an RPG than the regular game.

Yu-Gi-Oh Cross Duel suffered the same fate. Dead not one year after release.

Now it’s in the hands of a custom server, barely usable thanks to DRM that was hard to bypass.

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

nice >:]

Basically yep. That’s my best guess as well.

Probably a misplaced apostrophe, as is common with most people online. Same with “it’s” (short of “it is”) and “its” (possessive).

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.