(she/they)

Hi! You can call me Tadpole. I enjoy maps/geography, sci-fi and speculative fiction, classic and sports cars and motorsports, and retro and retrofuturistic technology from the 70s-90s. Also a racing, role-playing, indie and retro video game connossieur.

I am a certified lurker.

  • 1 Post
  • 42 Comments
Joined 9 months ago
cake
Cake day: September 26th, 2023

help-circle









  • I’m a pretty big fan of an online-only game that was killed while I was still in diapers, and I can only play a limited debug build of it that was leaked by a disgruntled developer who was mad the game was shut down. I often wish I had been able to experience it the way it was originally intended to.

    I don’t have The Crew, but what I’m seeing lines up very closely to my situation, so I relate to it. And this is a cause I most definitely support, so I really hope this works out. I hate when games end up as permanently lost media…







  • Yes, for over a year now (since early December 2022, don’t remember the exact date).

    My experiences with it seem to constantly be different than that of most users, because Wayland was a direct upgrade for me - I couldn’t play games properly on X11 at all because they would stutter and freeze really badly even when Vsync was disabled and the game reported to be running at 60 FPS, but Wayland fixed the issue altogether for me.

    …Granted, I’m on an AMD card. If I was on Nvidia it’d probably be another story entirely. :x




  • For what it’s worth, I’ve had Linux spew similar CLI errors when booting up complaining about a critical CPU problem, when the problem actually was that it was reading data off of a dying hard-drive. (Removing said drive, as well as replacing it with a new, healthier drive, made the issue go away.)

    Not saying your problem is actually a dying storage device, but that it’s possible the issue might not actually be your CPU itself.