Apple M1 Units - I select items and they always want to move

[Roderick Anderson]

Has anybody noticed this also and found a way to make this behaviour go away?

I select any element (either on plan or 3D view) and if I don't wait for 1-2 seconds after selecting the item, the element will always think I want to move it.  Therefore, if I am trying to work quickly and just select the item and then move the mouse over the the Info Box to edit any settings, the settings will be grayed out because the element is in the middle of a move command !

I've been using Archicad since version 10 and this has now been happening on version 26 and 27, but only if I use any of my Apple M1-equipped Macs.   I use a MacBook Pro and a Mac Studio, both of them with the Apple M1 Max chip and they both behave the same.

Does anyone think of any possible setting in the Work Environment that could help with eliminating this behaviour?  It gets kind of tiring trying to quickly select items, but having to wait a couple seconds after selecting a wall, a slab, an object, etc., because if I don't wait then it'll think I want to move the objects.

[Scraptrash]

---

@Lingwisyer wrote:

Is there any delay between when you select an entity and it highlighting?

---

yes. some delay like 1 sec. I assume it is because it takes some time to initiate the "move" command.

[Barry Kelly]

---

@Scraptrash wrote:

How can we raise this as a bug to GRAPHISOFT?

---

The best way is to contact your local Archicad support.

https://graphisoft.com/contact-us

Barry.

[Laszlo Nagy]

I am regularly reporting the issues raised on the Forums to Graphisoft.

[Roderick Anderson]

@Laszlo Nagy  I can report that last night I used my M3 Max equipped MacBook Pro and I did not notice this behavior at all.  I worked for about 3 hours straight, and the program’s behavior was as I would expect.  It would allow me to select several items by Shift-clicking on them one by one without having to have a pause between each selection.

Quite interesting that the change in chip changes the behavior of the program, but somehow I suspected that this would be the case.

I will keep on testing and if there if any change I’ll report it here.

[Scraptrash]

So I’ll need to upgrade to M3….hold on let me hit the buy button first…😌

[Scraptrash]

Would there be any update from GRAPHISOFT? Is there a way to mark “unresolved” in the topic? 

[Karol Argasinski]

Hi,

same with me - same M1Max, same devices.

[Roderick Anderson]

As an update on my side:

• Mac Studio M1 Max: Still keeps happening, sometimes more evident than others.  But at each work session with this unit it WILL happen no matter what.
• MacBook Pro M3 Max: Still has not happened in the work sessions so far.

[Karol Argasinski]

Hi Roderick,

on my side it is both AC27 and AC26 (INT and Polish language versions). I have the newest macOS Sonoma, but it was happening from the day one for me with Ventura.

[Msilva]

This has been driving me crazy for like two years. Nice to see more people with the same problem.