How: Open up Settings, Go to Graphic Settings (search for it) click the drop down and choose classic app, click add, add DisplayFusion.exe, once added, click on displayfusion.exe in the list again and click on options and choose "Power Saving" as the method. Hopefully this can be marked as solved and stay here for anyone else who is having the problem with Optimus.
Writing that post gave me a few lightbulb moments to try after realizing that it is definitely an issue with nVidia Optimus. I'm pretty sure the MS forum is setup to automatically cut and paste the "why don't you reinstall windows?" answer on every single question. There were some posts in the official microsoft forums about even he windows slideshow causing the same issue, but their responses as usual were worthless. Only thing I can think of is hardware variations, all of the laptops have been intel/nvidia with optimus auto switching. I don't have any other software that does anything with the wallpaper, theming, or window management installed. I mostly ignored it until I had time to search around or post this request.Īlso tried disabling application hooks, and trying the different aero color change modes, but none of those solved the problem.Īre there any new suggestions that I can look into? So far I've only used three different laptops in the last 8 months moving from one to the other with completely clean, debloated installs of windows before installing DF. The transitions suggestions doesn't change anything, I though it might have been Aero color changes, but that doesn't effect it, and the real rub is that this happens on ANY computer that I've had DisplayFusion on, I don't recall which version of windows or of DF when it started.
I have it loading images from reddit for wallpaper changes every 30 minutes, each time, mouse cursor lag, freezing and typing doesn't work, instead it buffers all the text I'm typing, mouse movements and clicks, and then dumps them all at once when the wallpaper changes. I noticed the thread from last year with 1809 and it seems to be the exact same behavior, but none of the suggested workarounds fix it.
0 kommentar(er)
