Hints of ArchiCAD 17
I’m always keeping an eye out for news about the future of ArchiCAD
While Graphisoft like most technology companies keeps most of their forthcoming features as closely kept secrets (for good reason), there are hints about the future. For instance, it’s not too late to sign up for the Eco Designer Star webinar. If you can’t wait to watch the webinar, you can follow that link to read some inside information about the forthcoming add-on to ArchiCAD.
Today I caught wind of some other forthcoming changes
ArchiCAD 17 will only support 64-bit systems. This isn’t too big of a surprise since ArchiCAD has been only 64-bit on Macs since ArchiCAD 15. This news is just the PC version catching up. And really, you should be using a 64-bit system these days anyways to get the best performance and have access to more than 4 GB of RAM. Seriously, it’s 2013. In related ArchiCAD on the PC news, ArchiCAD 17 will run on Windows Vista, Windows 7, and Windows 8 (but Vista won’t officially be supported). You’ll notice that Windows XP is not on that list. For all the gritty details about the discontinued 32-BIT support, how this affects the connections between ArchiCAD and Sketchup (hint: don’t worry) and to learn what other effects 64-bit only ArchiCAD 17 will have, read this ArchiCADwiki article.
A big thanks goes out to Illauszky Endre of manuBIM for sharing this on Twitter today. Say your thanks by following manuBIM on Twitter. Not familiar with what manuBIM is doing for our ArchiCAD and BIM community? Here’s a guest post Illauszky Endre wrote for Shoegnome. And two articles I wrote on BIM Engine about some manuBIM objects: floating dimension object and ceiling editor.
patrick may
another reason I’m glad to be working on a mac… its pretty tiring keeping track of what mircrosofts latest flop is… I’ll stick to my Mac osx ‘snow lemur’ edition.
Jared Banks
I just hope one day we get Sabertooth Tiger or Apple buys the rights to the Thundercats and I can load up OS X 10.17 Cheetara.
Yaser Harara
I really think Graphisoft should lessen the tools in future versions, as the most I hate about adding more is missing the idea of “Less is More”, besides the most thing I hate about the “Morph” tool!
They really should have worked on making modeling with walls, roofs, openings (Oh and don’t forget the stair lame tool) better, instead of adding the shell and morph, I’m sure it would have been a little more work, But Nooo, making a new tool is much easier!
Everybody makes new tools, Cadimage, Cigraph, ..etc.
It’s about making the existing tools better, which hasn’t happened since 11.
Jared Banks
This issue is raised with every new release and I know GS is aware of it.
What is the proper balance between refinement and new features? Unfortunately it’s really a losing proposition either way. If Graphisoft focuses too much on new tools, they are blasted for not fixing the old (or even breaking some of the old). If they only fix the old, then everyone moans about there being nothing new or sexy. This is of course the plight of all software developers and not just the makers of ArchiCAD.
And while they do keep giving us new tools (and I personally love that we have the Morph tool now), it’s a misrepresentation to say that the existing tools haven’t improved since 11. There has been a constant stream of refinements, tweaks, and improvements to many of the basics of ArchiCAD throughout the versions (and since 11). Dimensions for example have vastly improved. As have guidelines and the 3D window (to name just a few). And with the Morph Tool object creation has become super easy. That also highlights another subtle point about changes between versions. It’s not just about tools but about functionality within ArchiCAD. Object creation, data coordination, attribute management, etc. are not tools in the palette called ‘toolbox’ but they are just as important as the stair tool, the column tool, or the window tool. Of course there are still the old dark spots–stair tool. But it’s important to look at the bigger picture and patterns of change and development within the program.
Finally… I’m reminded of the post I recently wrote for BIM Engine: We all Have Blind Spots: http://blog.graphisoftus.com/archicad-education/we-all-have-blind-spots Hopefully there are some improvements since 11 that you’re not aware of, and that will pleasantly surprise you. I can pretty much guarantee it.
Jared Banks
I also meant to end with:
That all said, I think we all need to voice our opinions on this issue and make sure Graphisoft knows what us users want and need. So thank you for sharing!
Yaser Harara
Thanks very much Jared,
I never thought of it like this, and I think you have a good point in all what you said here!
Ay
Maybe we should start an Archicad Revolution Page or something
Pingback: ArchiCAD STAR(T) 2013 vs Revit LT 2013 | Shoegnome
Jared Banks
FYI – a direct link to the ArchiCADwiki article about SketchUp Connections and ArchiCAD 17.
Nader
Pleaseeeeeeee
Tell the people in Graphisoft, to improve the library creation and make them graphical ….
I want to make the Revit people jealous
David
Note: Support for GDL Software Tools such as the GDL Web Publisher/Control (GWC) and GDL Object Adapter (GOA) technologies will be ceased with the release of ArchiCAD 17.
http://www.graphisoft.com/products/archicad/parametric_objects/downloads/new_installadapter.html
Jared Banks
David, thanks for sharing this. Can you explain what that means? I’m not familiar with the GDL Software Tools mentioned.
David
The gdl web control for example is the browser plugin that allows you to view gdl objects on bimcomponents.com
So the question is, if the people at graphisoft will make a new plugin or will something more radical change in Archicad 17?
Jared Banks
Oh interesting. I hate waiting.
Mark
I’m wondering when Trimble will buy Graphisoft and expand development.
Jared Banks
🙂 Probably the more important question is will or when Nemetschek start consolidating/integrating/connecting all their software packages? No reason Vectorworks, Allplan, and ArchiCAD can’t all be slowly merging or at least talking to each other natively.
David
let alone Cinema 4D (instancing, AR render engine, deformers, etc)