The Global ARCHICAD Community

Stay informed. Get help. Share your knowledge.

Speed/Display issues/unfamiliar error messages, crashes/hangs or any other problems regarding ARCHICAD (Example: I get an error message when the 3D Window is generated, please help!).
Note: If your problem seems to be an ARCHICAD error please always report it to your local reseller!

Moderators: Barry Kelly, Karl Ottenstein, LaszloNagy, ejrolon, gkmethy

#295971
Hi there,

Me and my colleges use AC on WIN10 and have an annoying issue since one of AC20's halftime update (somewhere in 2017) and it goes on in AC21 and 22. It's a cursor size problem, something different from the 4K resoluton issue. In selection mode the cursor size is normal but when I start using any of the relative construction methods the cursor changes to an almost invisible size. Any idea?

cursor.jpg

Thanks,
Csaba

Windows 10
Intel Core i7-4790
NVIDIA GeForce GTX 960
#295989
I can confirm that the cursor does get smaller in 22 and I don't have a hi-res monitor at all.

Have you reported this to your local Graphisoft support team?

Barry.
#295991
Hm. Even the constraint type icon gets smaller for parallel. The crosshair and icon are consistent for the other constraint types though. Still, the default crosshair size is rather small and unlike some of the other crosshair types for other interactions, it has no body and is only two thin lines...



Ling.
#295995
Barry Kelly wrote:
Wed Apr 03, 2019 2:59 am
I can confirm that the cursor does get smaller in 22 and I don't have a hi-res monitor at all.

Have you reported this to your local Graphisoft support team?

Barry.

Yes, I have a few month ago. No answer yet...
For some reason we still work with AC17 too and the strangest thing is that there is no problem with the cursor size in AC17 at all. Very annoying. :roll:
#296130
Hello everyone,

This is a known issue (recorded as bug #236559). It is related to the issue with 4K screens and scaling that has been fixed for AC22, but not the same. As you can see when you start commands like this, you get a custom cursor that includes the cursor and the icon of the command.

Since apparently cursor sizes need to be fixed on Win10 (32x32 pixels), and these were originally created to be much bigger, they get shrunk to a 32x32 size, even though they are originally bigger. We are looking to redesign these cursors to avoid this in the future. Until then, unfortunately there's no way to avoid this behaviour.

Regards,