It generates an answer that looks correct. Actual correctness is accidental. That’s how you wind up with documents with references that don’t exist, it just knows what references look like.

You couldn’t crank your CPU in the olden days, it’d make games run in fast forward.

Nobody wants to deliberately use the wrong compression type when extracting, so modern tar will figure out the compression itself if you just point it at a file. So tar -xf filename works on almost anything. You don’t need to remember which flag to use on a .tar.bz2 file and which one for a .tar.xz file.

And we’re pronouncing it JIMP?

“Hey, here’s a useful thing that I recommend to people: <your work>”

It’s basically a compliment

The benchmarks are against vanilla Wine. A lot of people are using the fsync patches, so ntsync is more about accuracy - things that didn’t work under fsync should work under ntsync.

Instead of choosing between accuracy and performance hacks, ntsync should do it properly.

Yeah, but because pricing jumped like someone set a firecracker off under it’s chair people are actually still using vintage GPUs.

The devs have been working hard to hammer out those troublesome edge cases. There’s a lot less of them than there was a year or two ago.

IIRC Nvidia needs explicit sync support to work reliably. It’s fairly new and might not have landed in some distros, especially the stable releases.

IPv6 has privacy addresses, though. Stuff on my network generates a new random address every day and uses that address for outgoing connections, so you can’t really track individual devices inside my network.

IPv6 has a policy of throwing more address space at stuff to make routing simpler, though.

IPv4 will individually route tiny slices of address space all over the world, IPv6 just assigns a massive chunk of space in the first place and calls it a day.

Well, for starters, unless you’re running a quite old card you should be using amdgpu, not radeon. You seem to have them both loaded.

Post a dmesg?

People are playing it on Steam Deck. Handhelds might not be viable for high end raiding, but there’s a lot more to the game than that.

Reports are mixed.

If you want to post logs, I’ll have a look to see if I see any obvious problems: https://github.com/ValveSoftware/Proton/wiki/Proton-FAQ#how-to-enable-proton-logs

Definitely a very stable genius.

I think you only get the VRR setting if the screen does support VRR. No point asking the user if the system can’t do it.

ERROR: […/src/amd/vulkan/radv_physical_device.c:1877] Code 0 : Device ‘/dev/dri/renderD128’ is not using the AMDGPU kernel driver

This is the smoking gun, btw.

I see you’ve got it working, so I’ll just add a bit of explanation.

AMD GPUs used to use a driver called radeon. It was replaced with the current amdgpu driver. For a while, you had devices that were supported by both drivers and you could choose between the stable radeon driver that was missing features like Vulkan and HDMI audio or the brand new amdgpu driver that had the newest features but was unstable and not well tested.

The kernel has a policy of not unnecessarily breaking things with kernel changes so even though amdgpu has been well tested in the years since, devices from that era still default to the radeon driver and need to be forced onto the amdgpu driver.

I mean, there is, but people have worked hard to set it up so you can just click the button and it all happens.

Or an email client where you double click the link text to select it and press copy, and somehow this puts the link plus a trailing space in the clipboard to be pasted into a browser.