SEO

[Anonymous]

Is there any way to tell if an Archicad element
is participating in an SEO either as a target or operator ?
Perhaps in a way similar to how one can tell if an object
or wall has been cut by a roof by looking in the settings
of the selected element.
Thank you,
Peter Devlin

[Anonymous]

SEOs are still a bit quirky, and I dearly am wishing for an SEO Manager, but they are MUCH more robust than when they first appeared.

I have seen AC "forget" an SEO here and there. It seems not to like thin roofs as operators, and I have had an occasion where a slab as operand would not stick where it had a hole under the particular roof (if I recall correctly).

I have also had a problem in which I cut the top floor walls to a roof soffit/bottom-chord slab which was in turn trimmed to the roofs above. Though it worked at first, the 3D modeling eventually ground to a halt. Since most of the cut elements were in modules, there were over 1000 operands (most of which were not cut), so this is an atypical, and a bit extreme, situation. I fixed it simply by using a copy of the slab as the operator, and putting it on a hidden layer.

[Anonymous]

Hello Matthew,
Thank you for your post describing your experience with SEO.
I have had all of the problems you describe and it is
good to know that it's not just me.
Have you run into the "incredible shifting target" ?
This is the one where a target element under
certain inconsistent circumstances is displaced to the origin in 3D
but stays in it's correct position in plan. The only way to correct
the problem is to cut and paste the element back into the plan.
Graphisoft is aware of some of these problems and promises
they will be fixed in AC 10.
Thank you,
Peter Devlin

[Anonymous]

Peter wrote:
Hello Matthew,
Have you run into the "incredible shifting target" ?
This is the one where a target element under
certain inconsistent circumstances is displaced to the origin in 3D
but stays in it's correct position in plan. The only way to correct
the problem is to cut and paste the element back into the plan.

I haven't seen this one yet, but I'll keep my eye out for it.

[James Murray]

SEOs are bumpy and require observation. They're a lot better than they used to be. I am a hopeless, pathetic addict.

Some operations fail for no apparent reason. These you can usually redo.

Any geometric inconsistency in either party can cause an SEO to fail. Meshes seem especially vulnerable to this, since they're the most complex to begin with. Roofs where the edge conditions of the main polygon and a hole cause a crossing situation. Any 3D polygon formed by splitting along an edge where you get that dangling node.

While the reliability has improved a lot, the whole interface is still very 1.0. An operations manager is needed, and the palette itself is a total do-over.

[Anonymous]

James wrote:
SEOs are bumpy and require observation. They're a lot better than they used to be. I am a hopeless, pathetic addict.

Some operations fail for no apparent reason. These you can usually redo.

Any geometric inconsistency in either party can cause an SEO to fail. Meshes seem especially vulnerable to this, since they're the most complex to begin with. Roofs where the edge conditions of the main polygon and a hole cause a crossing situation. Any 3D polygon formed by splitting along an edge where you get that dangling node.

While the reliability has improved a lot, the whole interface is still very 1.0. An operations manager is needed, and the palette itself is a total do-over.

Well put, James. I too am addicted to SEOs and so periodically run into the limits and quirks as I occasionally push the limits.

[Anonymous]

Matthew wrote:
SEOs are still a bit quirky...
I have seen AC "forget" an SEO here and there... Since most of the cut elements were in modules...

Just a quick observation and comment from my experience with SEO's...I don't believe archicad will carry over SEOs contained in a MOD file when it is hotlinked into a PLN. If anyone has had success at this please let me know how you did it.

I've had to result to the old "trusty" trim to roofs to work aound this...

Thanks,
Dan K

[Anonymous]

Dan wrote:

Matthew wrote:
SEOs are still a bit quirky...
I have seen AC "forget" an SEO here and there... Since most of the cut elements were in modules...

Just a quick observation and comment from my experience with SEO's...I don't believe archicad will carry over SEOs contained in a MOD file when it is hotlinked into a PLN. If anyone has had success at this please let me know how you did it.

I've had to result to the old "trusty" trim to roofs to work aound this...

Thanks,
Dan K

The SEOs will convey with a MOD file if the elements are all on the same story. It might work if they are all included in a multistory module (I don't recall that one right now).

Linked modules can also be cut by elements in the main file. Groups must be active (not suspended) for this to work (just the opposite of cutting grouped elements).