Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)X
Posts
0
Comments
43
Joined
2 yr. ago

  • Plus, if something seemingly can't be terminated with that, 99% of the time it's a kernel level lockup (e.g. disk IO). At which point you only have 2 options: kill it via a kernel debugger or (the more likely scenario) perform a reboot.

  • Precisely. MS didn't do a very good job maintaining it for Ryzen CPUs recently, though. I remember the whole fiasco with Zen 4, when it just came out, it ran better on Windows 10 than 11.

    Then, more recently, 9950X3D needs manual thread pinning to run some games better.

    Like, come on... this isn't something any user should even be worried about.

    But also keep in mind that "just talking to the hardware" is one hell of a reduction and oversimplification, too.

    Keep in mind, these issues with Ryzen scheduling are fairly new. People yap about NT being an issue when it wasn't for many years and it still isn't even the primary issue (and it usually gets fixed by the vendors themselves in one way or another).

  • In fairness to Windows, the kernel and the drivers are the few of the objectively good things about it.

    Neither NT nor its age are the problem. It should be a testament to how well it works for the things we're using it for today.

    The problem is the userspace. The things that you interact with and see. That is what you're referring to when you mention "the format dialog". Not NT. Win32 isn't a kernel, it's an API that is used to sometimes talk to NT indirectly and give userspace functionality.

    Where NT is truly starting to show its age is with things like scheduling on AMD Ryzen chips with 2 different CCDs. That is a Microsoft skill issue. Had this issue cropped up not even 10 years ago, they would've figured it out. This is what is gonna age NT. New hardware, not new software.

  • Not having CFW isn't the end of the world. It's a slight inconvenience having to press the button at boot and maybe sometimes randomly a game not launching.

    Also, later super slims are using more modern chips and therefore are much quieter and nicer to use.

    Lastly, currently there is a modchip being developed for a qCFW (quasi-CFW) which will allow for basically 99% CFW capabilities on later models anyway, so there is that going for it too.

    Super slims are a hidden gem imo

  • From a glance, this is just a value parser that exports them by symbols and allows you to edit the static values from a file neatly.

    I don't know how practical this is yet since I haven't seen the video, but in order for it to be more practical it needs to be easier to implement and use than other methods to accomplish tweakable values for debugging.

    There are many already:

    • parsing a config/text file in runtime
    • parsing commandline args
    • parsing environment variables
    • using a debugger and a memory watch
    • using external tools that can edit memory

    Now, not all methods are available on all platforms, but, it needs to be better than any of these methods in some way for it to have any point in using it.

    Game devs often have their own frameworks that can communicate with the game via network to tweak exposed values anyway for realtime debugging. Adjust.h from what I can see requires the program to be reset on each iteration.

  • My yugioh brain defaulted to D.D. Crow lmao

  • Ez just nuke processes from the kernel debugger /s

    But, real talk, the only comparable thing would be the emergency restart option (go to ctrl+alt+del screen, hold ctrl as you click on the shutdown button)

  • 🗿

  • Absolute madness. I cringe at the thought of making modern x86 asm code.

    Great work!

  • Anti cheat is like DRM. It's a waiting game more than it is about actual direct protection.

  • Wait, what? Playstation?

  • I probably misremembered something then, 390xx it is then.

    But whatever it may be it is in the AUR 100%.

  • It's very good.

    Basically, there is one maintainer in the AUR (the name escapes me, jonathon I think it was?) who applies the necessary patches to the old NVIDIA drivers to make them run with a modern Linux kernel.

    Of course, there won't be any Wayland support, but the experience is acceptable as long as you temper your expectations in terms of graphics API support. (No vulkan sadly)

    I hadn't used it myself but I know a person who does and loves it. iGPU handles Wayland stuff while the NVIDIA is there for the heavy lifting in Xorg.

  • Unironically, the best bet for them is nvidia 540xx drivers on the AUR with an LTS kernel.

  • Chart

  • There go my hopes and dreams of IRL Solid Vision system and duel disks...

    One day, it will happen with MR.

  • RIP Black Box Games

    (I'm a NFS fan but also a fan of Black Box)

  • Oh you mean Android Studio automagically "updating" your versions so that your build breaks and you spent 3 hours figuring out what just happened without you even touching anything?

  • C++ is at least backwards compatible (for 99% of code anyway, yes I know about some features being removed, but that's an exception and not the rule).