Selection Bug AC16
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2012-12-10
03:27 PM
- last edited on
‎2023-05-23
02:38 PM
by
Rubia Torres
‎2012-12-10
03:27 PM
I'm having a selection and subsequent editing problem in AC16, newest build.
If I have multiple objects that have an edge or reference line in the same vertical plane I can only edit the object that AC considers the most important, or on top. For instance, if have a slab, then a wall, then a roof - the slab edge, coincides with the wall reference line coincides with the roof edge above, archicad will only let me click to edit the edge of the roof, I can select the wall or slab, but I can not edit that edge, nothing happens if I click it while it is selected. Specifically, if I have to use tab to cycle to an underlying object, that object will not be editible where it's edge or reference line coincides with another element's.... this is a really hard scenario to explain, I'll attach an image hopefully to clear it up.
The point is, this is new behaviour in 16, I didn't encounter such a problem in 15 or earlier and wondered if anyone else has experienced it, or knows of a particular setting that I may have previously checked in 15 and not realised it is unchecked in 16 (though I did a check through the options)
*I now suspect it's a memory problem, I started a new project just for demonstration purposes in which I modelled the above scenario and, of course, everything worked fine

cheers,
4 REPLIES 4
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2012-12-11 01:39 AM
‎2012-12-11
01:39 AM
See if this workaround helps until a fix.
http://archicad-talk.graphisoft.com/viewtopic.php?p=209829&highlight=bring+forward#209829

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2012-12-11 02:26 AM
‎2012-12-11
02:26 AM
We aware of this bug and a fix is coming. I do not have an exact ETA but it should be within this or next month if all goes well with quality control.
Best regards,
Best regards,
Nicholas Cornia
Technical Support Team - GRAPHISOFT North America
ARCHICAD on Twitter
Tutorials
GRAPHISOFT Help Center
Technical Support Team - GRAPHISOFT North America
Tutorials
GRAPHISOFT Help Center
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2012-12-11 02:28 AM
‎2012-12-11
02:28 AM
Ahh that's a good point. That will work on the instances where adjacent/overlapping elements are different atleast.
Oddly, I did a search for this topic before I posted and that thread didn't show up.
So no one in that previous thread stated that they'd already reported it. Is anyone aware of whether it's been reported yet?
Oddly, I did a search for this topic before I posted and that thread didn't show up.
So no one in that previous thread stated that they'd already reported it. Is anyone aware of whether it's been reported yet?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2012-12-11 09:38 AM
‎2012-12-11
09:38 AM
Well, since Nicholas works at Graphisoft Technical Support, I am sure it has been reported.

Loving Archicad since 1995 - Find Archicad Tips at x.com/laszlonagy
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac28
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac28