2020-08-14 03:05 PM - last edited on 2024-05-26 11:27 PM by Karl Ottenstein
ARCHICAD 19-25, Student & Full Archicard, CI Tools, Germany
Mifcom Renderbox AMD Ryzen 9 5900X GeForce RTX 3070 TI 32GB RAM 980 PRO SSD Win10
Thinkpad P52 4K i7 8850H NVIDIA Quadro P3200 (6 GB) 32 GB RAM SSD Win10 Pro
Solved! Go to Solution.
2023-04-20 05:15 PM - last edited on 2024-02-13 07:50 PM by Laszlo Nagy
Try unchecking the preview of the magic wand selection. It worked for me.
2024-02-11 11:29 AM
It's 2024 and this issue is still not solved. Why? Does the Graphisoft team have something personal against urbanists? I really wand an aswer on this one
2024-02-11 11:31 AM
With the uncheck of the magic wand preview, this actually works A LOT better, but it is not a solution.
2024-05-25 11:53 PM
in Archicad 27, the same issue persists, whether with preview enabled or not ( disabling the preview helps but it is still also slow).
2024-05-26 11:11 AM
Paradoxaly, export to dwg, import the dwg. the spline came as polyline, then magic wand ...
2024-05-26 11:07 PM
As you can see in the short video, the algorithm to find the boundary isn’t very clever. It is kind of ballooning, for that reason it can only find the outer edges, but not the inner ones. My assumption is, that the "highlight"-algorithm and the "magic wand"-algorithm are the same. For that reason it (mostly) works for the magic-wand-stuff, but not for highlighting, because it has to start over and over again with every new mouse position.