Forum Replies Created
-
Posts
-
Perhaps you should consider copying or renaming the .exe to this_ain’t_hard.exe and assigning it to the profile you want to use.
Turning off your monitor save’s energy, but that’s about all. Your gpu doesn’t care if it’s got power or not, it’s still going to output the signal.
I changed the .csv file and saw no difference in fps, RAM usage, or VRAM usage. I even set the values to zero and saw no difference. As far as I can tell, the budgets are ignored.
I think Gears5 is dx12, so despite being an Unreal Engine 4 game, no existing profile for that engine will work. You can try one of the four dx12 profiles that do exist (Death Stranding, Horizon Zero Dawn, Red Dead Redemption 2, and Cyberpunk2077).
@Ralf
I updated my drivers to 460.79 but the real problem was in the setting for cuda gpus. I had set it to my second gpu to force to to do video encoding, not realizing that it would have an impact on games that are dlss capable.
I know you don’t really care about multiple gpus, just an fyi about what was causing my issue.
I think the game was pushed out the door before it was ready for prime-time. It took me several hours just to get the game running on my rtx gpu (had to downgrade my video drivers). I’ve fixed that but vorpx only hooks the game about 10% of the time; usually it flatlines.
So I’ll probably wait until it’s stable enough to actually be playable.
You need to make sure the game starts up in G3D mode. If you start it with Z3D and then switch, the G3D will get messed up.
I already uninstalled the av once but went back because Windows Defender kept complaining about a registry entry but didn’t fix the underlying cause.
I already used solution 2 up to ig-20 but was hoping there was an easier way to address the other 80 possibilities. Maybe I can just turn real-time protection off.
Thanks.
I’m certainly not an expert on the matter, but from what I’ve read, the latency settings are not very effective when compared to other methods of reducing latency, like capping your framerate to prevent the gpu from getting overloaded.
I’d think that ultra low latency would override the setting for pre-rendered frames. I don’t know why you’d want to run a headset with ultra low latency turned on though.
Since I changed pre-rendered frames from the default value, I get better framerates, practically no stuttering, and can run games at higher resolutions (including 4K, which was impossible before).
Anyway, my cpu/gpu don’t like the default value. Years from now, perhaps decades, when the mythical RTX 3080 emerges from the shadows, I may change it back.