im having the same issue. ( i think) i have a 3070ti and just one screen and its just trainer manger not dying light 2. dying light is using about 48 - 60 when playing with out trainer then some times just some time the trainer/manger uses over 50% GPU witch then tanks the game. i will try to get a screen shot when it happens. but as i said its just some times. i will reply to this post with screen shot of when it happen.
hello i have some pic.
as you can see when the game is in the background the GPU drops to 0% but the trainer is still using just under 30%. and when playing game
i will keep playing to see if it will get worse and then add more pic.
pic in zip folder.
1. Pic of task manager with trainer running
2. Pic of pic with out trainer running
3. Pic of task manager with out trainer
4. Pic of game setting
The registry key disables DirectX for all WPF applications which fall back to software rendering then (which is slower). So its definitely DirectX related issue. It can only be a monitor / graphic card driver setting or another software which injects something into all directx processes it finds. This is typical for overlay tools, or even Nvidia Geforce Experience (if any of you use that, try to disable that too).
In next Aurora update I've added an option to disable HW acceleration just for Aurora, so this registry key isnt needed then.
When it comes to myself, I don't have this issue. I have a Nvidia 2080 with the standard driver settings. No Geforce experience and my monitors are running at 60hz only. I dont have freesync or gsync. I also dont have HDR.
Thanks so much for taking time to find a fix for this.
Hate when issues that are specific to programs, number of monitors, refresh rate and maybe other stuff come up.
So hard to replicate and find fixes for.
But 0x90 you prove yet again the CH is best by finding a fix within short time.
The registry key disables DirectX for all WPF applications which fall back to software rendering then (which is slower). So its definitely DirectX related issue. It can only be a monitor / graphic card driver setting or another software which injects something into all directx processes it finds. This is typical for overlay tools, or even Nvidia Geforce Experience (if any of you use that, try to disable that too).
In next Aurora update I've added an option to disable HW acceleration just for Aurora, so this registry key isnt needed then.
When it comes to myself, I don't have this issue. I have a Nvidia 2080 with the standard driver settings. No Geforce experience and my monitors are running at 60hz only. I dont have freesync or gsync. I also dont have HDR.
This solved my problem as well. Thanks so much!