Walk on the front of your foot, the process require you to intentionally concentrate on your gait which causes it to change

Not that you can do it all of the time, but it is a way to defeat gait fingerprinting.

What was the resolution?

It was a .30-06, a 7.62mm round, similar to an AK-47 (ARs uses5.56mm). They make big exit wounds.

Given how close the round hit to his brain and the fact that it hit a major artery, he likely died due to the hydrostatic shock from the impact.

He likely didn’t even know he was hit, he was seizing immediately and all of his body motion after the impact was involuntary.

You can disagree with political violence and also not be upset that he’s dead.

Conflating the two is disingenuous

Honestly, I’d bet money that the problem is at least partly Denuvo‘s fault.

So many envs and no central documentation makes it hard to handle for everyone.

Ah, I didn’t RTFM completely. I just read a snippet that mentioned the NGX updater and misunderstood the context.

I’ll give it a shot, thanks.

it’s there on others (edges can get a bit shimmery with tsr) but really bad with dlss

Yeah that’s my experience as well. TSR seems to be doing the same thing but it isn’t applying the oversharpening which makes them stand out.

What launch options are you using if you don’t mind?

ENABLE_HDR_WSI=1 PROTON_ENABLE_HDR=1 PROTON_ENABLE_WAYLAND=1 gamemoderun %command%

You have to be using GE-Proton10 or above in order to use Wayland’s HDR. I don’t think you need ENABLE_HDR_WSI (I believe PROTON_ENABLE_HDR makes Proton set a bunch of environmental variables on startup.) but I’m not sure.

Using GE-Proton10-15, HDR works great too.

I did notice the edge flickering artifacts with upscaling. XeSS is a bit higher quality than TSR but it also has the flickering. FSR framegen causes the flickering to happen on some particle effect that they use for atmosphere effects (like pieces of dust floating in the air) so it isn’t very usable currerntly.

The game isn’t perfect, but it’s very playable for me after some settings adjustments. I didn’t have any crashes in 5.5 hours of playtime, but I did notice the shader compiling stutter and there were some spots where you could tell that it was loading a zone if you walked over a specific point and I was in combat at the time so I ran across that point a few times and that caused some framerate issues.

A HUGE amount of the stuttering was eliminated by setting the Textures Streaming Speed to Very High, it looks like this is throttling disk IO for performance reasons. If you have an NVME SSD then I can’t think of a reason not to set it to reason not to set it to very high.

That’s good to know that Steam co-op works. I’ll try it later today, my friends are all running Linux too and didn’t want to buy a copy if it wasn’t going to work. I happened to be home yesterday so I was the guinea pig.

I tried updating the DLSS version (using PROTON_ENABLE_NGX_UPDATER=1), the flickering still occurs. Same with using RENDER_PRESET_K. It almost looks like they’re applying too much sharpening when you’re using DLSS, but I don’t see a way to adjust that specifically.

Playing, on Linux (Arch, btw) with no issues. The defaults were a bit harsh (45fps@4k) but once I ran the graphics setting autodetection and it went to medium with balanced upscaling I was getting 60+ FPS.

I couldn’t connect to the matchmaking servers (my system doesn’t meet the requirements, apparently) but it otherwise ran just fine.

I played it in Proton from the beginning

You get what you pay for.

“It”? Are you conflating the low parameter model that Google uses to generate quick answers with every AI model?

Yes, Google’s quick answer product is largely useless. This is because it’s a cheap model. Google serves billions of searches per day and isn’t going to be paying premium prices to use high parameter models.

You get what you pay for, and nobody pays for Google so their product produces the cheapest possible results and, unsurprisingly, cheap AI models are more prone to error.

It doesn’t take an AI genius to understand that it is possible to use low parameter models which are cheaper to run but dumber.

Considering Google serves billions of searches per day, they’re not using GPT-5 to generate the quick answers.

Exactly.

The model that responds to your search query is designed to be cheap, not accurate. It has to generate an answer to every single search issued to Google. They’re not using high parameter models with reasoning because those would be ruinously expensive.

Same, I enjoyed the gameplay but every item drop was far less exciting because I’d need to pause and consult a wiki before making a choice.

Are you playing on an 8K display or something?

I’m using Deepseek R1 (8B) and Gemma 3 (12B), installed using LM Studio (which pulls directly from Hugging Face).

It isn’t unique, it provides text, voice and video chatting. These are not new services to the world of technology.

What makes Discord stand apart is that they require that your chats, calls and streams are not private and, in exchange for people giving up their private data the users only have to install one piece of software instead of two. It is like a company giving people a ‘free’ phone as long as they or their advertisers can listen into the calls, read the texts and look at the videos on the phone.

The only thing that Discord does is to package the software in such a way that you can’t access it until you give them information about you and then they gate features behind you identifying yourself with a credit card and a phone number.

It’s pretty different.

Heart rate and vision have objectively correct ways to measure them. Bot detection doesn’t.