Sketch up import

[Anonymous]

How do i import a sketchup file into ArchiCAD

[Aaron Bourgoin]

Ferenc,

Your latest post requires some reading between the lines.

Well, at least the ball is off my court:

>>>>>>>>>>
Unfortunately we're not in a position to provide the SDK. As you
mentioned, the ArchiCAD plug-in development didn't go very well. We need to focus our development efforts on situations with a good track record. It is not personal. We simply have too much on our plate to pursue second chances. We wish you well in your efforts.
<<<<<<<<<<

Now, let's hope the "replacement project" first mentioned in 7/22/04 on the SketchUp forum will go beta soon (as expected on 9/22:).

BTW. I was offering the update as no cost to @Last...

I would intuit from your post that something catastrophic has happened to the SketchUp to ArchiCAD conversion project.

Can you elaborate further? Is there a relevant post or other thread I've missed?

[Dwight]

Does this mean it is over for SketchUp To ArchiCAD Nine, then?

[stefan]

I guess the development is done elsewhere and if they find it interesting they will finish it.

It exists for AutoCAD and although it is not marketed very much, the simple fact that it exists is a proof that there was a demand for it.

That said, for pure geometry, one can import SketchUp files as DWG files. It works fine in AutoCAD, although you don't get the walls or windows that way. So there is a real use for a more intelligent import plugin.

I hope that the "marriage" between SketchUp & ArchiCAD doesn't end up in a divorce. It would be another missed opportunity for ArchiCAD. And it are sometimes these "connections" that can build up the credibility for a CAD-tool. Hey, if it works for AutoCAD it might work for ArchiCAD too.

[Anonymous]

That would be a shame, because I am trying to follow a course of developing my schematic designs so that I can import them into ArchiCAD. I have read that SketchUp is the application of choice for "designers" in larger firms who turn it over to the CAD department for final CDs. I tend to think in a similar vein, that I want fewer bells & whistles during SDs & DDs and a more intuative 3D interface while designing. But once that stage is completed, ArchiCAD's capabilities are very much needed.

+pablo

ps: I would be willing to help support some type of beta-testing??

[Anonymous]

Well, the project was ridden with changes in schedule, and the Mac OSX installer was definitely needed rework.
Those were mostly, but not exclusively my fault: it was my first hardcore development project after 13 years of support role, and several assumptions in marrying the ArchiCAD API with the SkUp SDK didn't work out, so the code ended up a patchwork of "plan b"-s and "plan c"-s.
for the 8.1 update I had to rewrite a nice part of it, and at that point the German and French version was done (stopping short at the French and German version of the installer).

I think the functionality was pretty much on target, and the ADT version is largely the same spec as the ArchiCAD plug-in. I was foreseeing only minor adjustments on that side (merge function, defining materials for the colored- not painted surfaces, handling the offsets of windows-doors with arbitrary local origins, distinguishing between doors and windows either by layer names or componentnames, maybe skylights -if API allows...)

I guess my ego set aside, we will see if the replacements (first mentioned in July) will come up with a beta soon, and how much better it will work.
If not, I my guess would be that the guys in Colorado see the up-to-date ArchiCAD plug-in more a liability than an asset.

Well, it's their call, after all the promised GS-@Last marketing cooperation fell through, and they might have felt serious disappointment after their investment into financing the plug-in and putting up with me...

Without the SDK the SkUp4.0 compatible version is problematic, I can do the ArchiCAD 9.0 version, but it will only read 3.1 files.
The open formats (VRML, RenderMan) lack the intelligence (components, component behavior, association with surfaces) necessary for the plug-in. I don't know if that information could be obtained via RubyScript introduced in 4.0.

Question is if the current functionality works good enough for the AC users to warrant an update. On one on one (after the installation issues were dealt with) I had positive feedback, but it definitely wasn't an avalanche.

[stefan]

I thought the plugin did what it had to do? It's not perfect, but it was usable and workable.

Strange that they are shooting it off then...

[SeaGeoff]

Everyone who cares should post a courteous request here.

[Anonymous]

Thanks Geoff,

Great idea, hope it will work out one way or another.
I think your post is very polite and appropriate.

I would also appreciate if you (and maybe other users too) could find some time to offer feedback, improvement ideas and criticism on the current 8.1 based plugin. Please send it DIRECTLY to me.

I remember the installation problem, but by now we might have more experience than right after the beta testing.

Best Regards,
Ferenc

[Djordje]

This is not good.

Autodesk ditched Architectural Studio. Next, they are buying SketchUp.

So ArchiCAD is once again left high and dry?

This could have worked sooo sweetly ...

Oh well ...



Yes, geoff's idea is the right one.

[Anonymous]

May i add a suggestion.
It might be usefull.

Instead of making an add-on to export to Archicad,
they could make a general export to IFC.
Much easier i think and highly portable.

I am not aware of how IFC is imlemented (i guess some xml structure) but i suppose if its saved as an IFC structure Archicad can import it (and not only archicad)..

What do you think?