#Small mac pointer for windows 10 update
#Small mac pointer for windows 10 windows 10

Until ArchiCAD becomes DPI aware, it seems I need to sacrifice this functionality and/or throttle some GPU rendering performance on one of my Nvida Cards

The only reason I have been using the onboard Intel GPU at all, was as a way of offloading some demand on my Nvida GPU - I use 4 Nvidia connected GPUs for GPU rendering in Octane Render - every extra bit helps, and it is nice to be able to read my emails and perform other graphically undemanding tasks on the secondary monitor (with no slowdown) while all 4 Nvidia GPUs are 100% dedicated to the rendering. It may be that if my Intel GPU had been connected to another 4K monitor, that the issue would not have arisen as the default DPI scale factor windows calculates during boot up would then have been correct for 4K resolution, but in my case it had been connected to a lower resolution secondary monitor. With the Intel GPU disabled, suddenly the ArchiCAD mouse pointer responds to the HDPI registry setting, and looks as it should. If present, the motherboard onboard Intel GPU needs to be **fully disabled** in BIOS (set GPU boot priotity to 'PCIE', NOT 'Auto' or 'CPU'), otherwise windows appears to interrogate this GPU during boot, which impacts the default DPI scale factor windows thinks needs to be applied to non DPI aware applications like ArchiCAD, and also seems to prevent windows from responding to the registry HDPI scale factor setting for ArchiCAD - for reasons unknown. Hi all - I have found what seems to be the issue that prevents the HDPI registry setting workaround from surviving past the first system reboot - and a solution: What have others done to solve this serious problem?

#Small mac pointer for windows 10 windows 10

Rolling back to or reinstalling an earlier version of Windows 10 are not good options in my case. Before you try other solutions, it is wise to rule out the issues with your mouse. Here are some common reasons for mouse lag in Windows 10 ordered by importance. (perhaps a compromise or carry over from the way custom mouse feedback is implemented for the Mac platform?) However, you can try different methods one by one to rule out some common causes of mouse pointer lag in Windows 10.

#Small mac pointer for windows 10 update

This seems to stem from ArchiCAD's non compliant method of handling the custom mouse pointer DPI scaling rather than anything with the OS - as is demonstrated by nearly ALL other applications that predate the windows update being unaffected. Is anyone else finding that on a 4K screen, following the recent Windows 10 Creators update, that the ArchiCAD mouse pointer is now insanely small? (for all ArchiCAD versions)ДЄrchiCAD is the only application so affected, and while increasing windows UI scaling, and increasing windows mouse pointer size to maximum within Windows Control Panel generallyworks as expected for everything else, the mouse pointer once moved over the ArchiCAD application window) becomes so tiny it is barely visible - and certainly the ArchiCAD dynamic pointer style context feedback is utterly undetectable.