!Restored: Archicad mesh to Architerra Terrain?

[Thomas Holm]

I've got a terrain model, made as a mesh in Archicad. Now I'd like to use Architerra's tools to modify this terrain (especially the Plateau and Road tools). I've got Architerra 2.02, AC9 2172.

Questions:
How do I get Architerra to accept my mesh as an Architerra terrain? Is there some preferred procedure to this? Or is it simply impossble? I've tried the Terrain tool as explained by the Help, but the only thing that happens is that my mesh gets deleted (it's exploded to lines and hotspots). No other Architerra tool accepts the mesh as input. Some tools tell me a mesh has to be part of the selection - but it is!

[Fabrizio Diodati]

Dear Thomas,

I checked your mesh and, sorry to say this, the ArchiTerra result is correct!
I don’t know which method you used to build this mesh but there are a lot of duplicates points (overlapping but with different levels) along the perimeter.
ArchiTerra cannot keep these overlapping points during the conversion because they could cause crashes or approximation troubles (the rule we apply is to keep the points belonging to the perimeter).

As you can see in the attached images, where there are two overlapping points with different levels ArchiTerra keeps the lower in the created mesh, where there is no incongruence you have a correct result.

Friendly,
Fabrizio

[Fabrizio Diodati]

And the second image...

[Thomas Holm]

Dwight wrote:
Was the mesh grouped in your project?

No.

Dwight wrote:
it is a little sloppy at the edges...

That's precisely the problem that makes it unusable!

[Thomas Holm]

Fra wrote:
I attached the mesh recalculate for architerra

Thanks Francesco! I would not have thought about that method!

[Thomas Holm]

Fabrizio wrote:
Dear Thomas,
I checked your mesh and, sorry to say this, the ArchiTerra result is correct!
I don’t know which method you used to build this mesh...Friendly,
Fabrizio

Dear Fabrizio,

I obviously cannot complain about your support! I do appreciate all help!

But, I respectfully disagree.

The conversion result might be correct as to Architerra's logic, but I think an add-on should respect the master program's logic, which means that an imported and not edited object should by default look the same (and appear at the same location) as in the master program.

If what you've found are problems or faults in the Archicad-created mesh, it's obvious that Archicad handles them without issues when displaying the mesh. I think the Architerra add-on should do the same. But of course it would be nice to have reports and options to correct problems if they exist. Francisco's method isn't self-evident for an occasional user.

I do agree, however, that Archicad's mesh editing options are poor, and do need som attention from Graphisoft - the wishlist has several suggestions already. If Graphisoft are not interested, I think better mesh editing options within Architerra is an obvious development goal!

Edited: I should add /remind you of/ that I discovered the issue you mention (some zero height points along the perimeter) after I'd imported the terrain into Architerra. But instead of using Francesco's method, I tried to edit the height of each point using Architerra's point height tool. That didn't work at all, as I described before. I still don't know why.

For your information, the mesh was created in two stages.
First I simply traced a scanned contour map (1m equidistance), manually creating polylines for each contour. Then I followed the procedure outlined in http://www.graphisoft.com/support/archicad/archiguide/surveyordrawings.html from step 4 and on.

Later, I got a 2D DWG contour map that I received from the local community authorities. It had 500 mm equidistance, and as I needed this level of detail, I imported the 2D dwg and added the extra contours to the mesh, using the same procedure as above.

I have no knowledge of doubling any contours or the outline. I do agree that something might have happened anyway - you do repeat the same procedure a lot of times, and things happen. Also, weird things sometimes happen when you try to move a node or another in the mesh. Of course, such things should not happen when you use standard procedures.

To my knowledge, I haven't grouped the mesh with or without anything else. When i exported it, I just clicked on one edge or node to select it and then "Save selection as module".

[Fabrizio Diodati]

Dear Thomas,

"The mesh was created in two stages.
First I simply traced a scanned contour map (1m equidistance), manually creating polylines for each contour."

Stop!
At this point, as ArchiTerra user, you should convert that polylines (better if Splines!) into ArchiTerra contour lines… that’s all!
That ArchiGuide tips is for anybody doesn’t have ArchiTerra.

“an add-on should respect the master program's logic”

This was just we did in the previous releases and the users got so many crashes due to those overlapping points that we had to use a filter to avoid to get overlapping points!!!
Of course overlapping points cannot exist in the internal surface of the mesh but they can exist along the perimeter: the ArchiCAD number approximation causes a lot of trouble along the perimeter because sometime it can consider the internal point as an external one and, quite obvious, a mesh cannot contains a point outside its perimeter!

“an add-on should respect the master program's logic”
I fully agree but, just in the same time: “an add-on cannot workaround malfunctions (or “special issues”!) of the host software”.

Last but not least, from my experience as ArchiCAD add-ons developers the fault is always from the add-on side: I cannot say the trouble is ArchiCAD itself because nobody will trust on me (please, don’t misunderstand: the fact we develop add-on only for ArchiCAD is a clear evidence I trust on ArchiCAD!).

Friendly
Fabrizio

P.S. I “saved” your suggestion: the next release will prompt the user by warning about these overlapping points and asking for keeping the lowest or the higher ones…

[Dwight]

Fabrizio.

Thank you for that insight. What a nightmare!

I often sit back and think how easy it might be to create an Add-On. Then I make a moderately difficult GDL object and spend unpaid hours de-bugging it. (Not that I am any good at GDL, but that is how it goes.)

Thanks you again for such a great bunch of Add Ons.

[Fabrizio Diodati]

Dwight,

You say thanks to me?
I will never be able to thanks you enough for your unbelievable LW manual!!!

If someone trusts on my AC experience should immediately follow my advice and buy this book:

The book GS will never release because only Dwight knows what AC LW Engine can do...

Friendly
Fabrizio

[Thomas Holm]

Fabrizio,

I sit here thinking a lot of your troubles would go away if you re-worked the documentation and help files. (And please use a natively English-speaking person- some things are unnecessarily difficult because of translation issues).

Of course, issues in the master program aren't your fault as an add-on developer. Still, you just have to handle them, or you put your user into the marsh.

An example is the new Architerra terrain mesh I got from you. It displays correctly in Archicad, it's placed at the right location. So Iwas very happy!
But when I checked the program's palettes it's becoming weird. They say the mesh is located at the double height (ca +119 m above zero). And it is! When I check the points with Architerras Point tool, it checks out. Each point has a NEGATIVE z-coordinate (i. e. "-57500"). This means that I have to prepare each edit operation I want with some weird calculations to get it right. It's still too much trouble.

There should be a way to do "global" point transformations to a mesh, so that every point displays correct values even after you move the whole thing in the z-direction.

Just an example of a valuable mesh editing addition that a 3rd party developer could do!

I'll give Architerra another chance on the next project. This time, I'm sorry but I think I've struggled to many hours with it in already. I have a deadline for the project.

But I do appreciate your engaged support!

Best regards,

Thomas

[Fabrizio Diodati]

Dear Thomas,

"An example is the new Architerra terrain mesh I got from you."

What do you mean?
I don't remember... I simply replied on this post and I didn't send you anything...

Friendly
Fabrizio

About the translation: Our translator is a young USA girl... and before printing the manual we always ask some user to check the translation. Of course anything can (and should!) be improved!

P.S. "There should be a way to do "global" point transformations to a mesh, so that every point displays correct values even after you move the whole thing in the z-direction" unfortunately this is the way in which ArchiCAD works: the nodes levels don't care about the mesh movements along the Z axis.