Unfortunately, I don’t think this would work.

The answer to where you should plug in is directly into your GPU, as streaming the data from your external GPU to your iGPU will cause data throughput issues as it has to constantly stream data back and forth through the PCIE bus. Even in simple games at low resolutions where that wouldn’t be an issue, you’d still be introducing more input lag. That’s why connecting your display to your motherboard is usually considered a rookie mistake.

But obviously, if you’re outputting from your external GPU, that silicon is still being used while rendering on the iGPU, which I believe would erase any potential power savings.

I think the better solution if you really want to maximize power savings, would be to use a conservative power setting on your main GPU, and do things like limiting your framerate/selecting lower resolutions to reduce your power draw in applications where you don’t need the extra grunt. Modern GPUs should be pretty good at minimizing idle power draw.

The problem isn’t the tech itself. Getting a pretty darn clean 4k output from 1080p or 1440p, at a small static frametime cost is amazing.

The problem is that the tech has been abused as permission to slack on optimization, or used in contexts where there just isn’t enough data for a clean picture, like in upscaling to 1080p or less. Used properly, on a well optimized title, this stuff is an incredible proposition for the end user, and I’m excited to see it keep improving.

Interesting. I’ve been using XeSS lately, after seeing better results in DOOM TDA, but now I’m curious if this is worth using instead, and figuring out an FSR replacer on Bazzite to use this.

Hard to blame them. Proton is dang impressive, and if it works, it works.

My guess here is that it isn’t Denuvo, it just seems like it’s not designed for Open World games. These issues all also exist on console, where Denuvo isn’t a problem (although it certainly isn’t helping either). Dragon’s Dogma 2 exhibited a lot of the same poor performance and stuttering nearly a year before MH Wilds came out.

By then, I assume the game was too far into development to change course, with it’s ambitious design and a lot of AI that has to always run in each area adding to the engine issues.

Honestly… I’m not sure how much better they can make it, given how much time they’ve had to work on it, and that DD2 never really escaped its issues too. It feels like RE Engine was just… fundamentally not designed for this, no matter how great an engine it is in its niche.