Fair enough. But the fact I can’t even use it to connect to my homelab proxmox cluster kinda has to be a dealbreaker for me. Even a trial period to allow me to try and experience everything would be sufficient in my opinion. On the fuzzy thing, I’m using gnome desktop, with latest gnome shell in debian sid, on an Nvidia 20280 using the proprietary driver (latest in debian experimental). It’s connected to three 2k/1440p monitors running at 144/60/60hz. If that helps at all. The tooltips are most notably fuzzy. It looks like it’s being antialiased multiple times or something?

Locking basic homelab functions behind a $50/year license means it is purged. Sad, because it had potential, though it suffers from a weird text scaling issue that means everything is just very slightly blurry.

I used to hear tv tubes, power supplies and all sorts of high frequency noise. These days I mostly just hear tinnitus. EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE

I have the original 512. I’m going to have that custom shell. I am a sucker for consumption… I must consume…

I remember watching it when it reached closest approach back in the 80s. Here’s hoping I can live to 95 and see it come back again

Max11 is all my code. Why doesn’t it work???🤔

Sadge

This bug was fixed in a patch when phantom liberty launched? I haven’t seen it since that patch anyway.

Downgrade to the 510 Nvidia driver. Runs absolutely solid on my rtx2080. It should be noted that this crash seems to be quite correlated to the rtx20x0 cards - my speculation is that something about dlss is a bit borked on them since they’re the first dlss 2+ cards. It’s not even exclusively Linux either, reports indicate that there’s some sort of overlay (I blame the call overlay myself) that is tanking fps on windows as well. The 510 driver works great because dlss isn’t available for it as I understand it.

I remember the transition from a.out to elf. Fun times!