2011-05-02 05:10 PM
2011-05-08 12:28 PM
NCornia wrote:
......
But, if the wishlist area is in fact to matter then you should get as many people to vote as possible on each request. Use the most popular areas of the forum, such as "Working in ArchiCAD", which contains nearly a third of all posts on the entire forum, as a funnel to really push people to vote. Link and re-link to the wishlist as it applies to each post. If someone has a question about stairs, post a message that says, "By the way, to all reading this post, vote here '()' on this feature, your voice matters!"
.........
Hopelessly optimistic for the future of ArchiCAD.
Cheers!
2011-05-08 01:10 PM
NCornia wrote:
.....
I do not know how much weight this forum holds in Graphisoft's decision making, how much time they spend here or really the percentage of the entire Graphisoft user base that the regular posters (and irregular posters if you count Dwight ) here represent. My guess is that we represent a small minority, but nonetheless a very important minority as some of the most accomplished ArchiCAD users reside here I am sure. I also feel that posting things in an any online forum is not the most proactive way to get your voice heard anyway. I mean who comes here on a regular basis but the diehards? And don't get me wrong, I love it. I have become hooked over the past year to ArchiCAD and this forum and love all the posts and contributors. But in the end I know the forum is a small community and not necessarily the bull horn that is going to get the major attention from Graphisoft or the world at large.
But, if the wishlist area is in fact to matter then you should get as many people to vote as possible on each request. Use the most popular areas of the forum, such as "Working in ArchiCAD", which contains nearly a third of all posts on the entire forum, as a funnel to really push people to vote. Link and re-link to the wishlist as it applies to each post. If someone has a question about stairs, post a message that says, "By the way, to all reading this post, vote here '()' on this feature, your voice matters!"
..........
2011-05-08 02:42 PM
Scott wrote:Spot on. why doesn't this exist in AC or even a dedicated standalone application.
This is a great point, but without any experience in software programming, and some basic GDL skills, it seems the core is not so much the problem as it is the interface.
Since GDL can be automatically created from models, it seems incredibly feasible to me to create a GUI that lets you model and assign parameters to elements, then let AC write the GDL code.
2011-05-08 03:30 PM
2011-05-08 03:38 PM
2011-05-08 03:41 PM
2011-05-08 04:28 PM
2011-05-08 05:35 PM
rwallis wrote:"ArchiCAD 15 offers automatic connections between building structures and elements where such connection helps the creation and maintenance of the BIM model while preserving the flexibility architects need." here:
what about instancing, relationships etc etc.
2011-05-08 11:23 PM
2011-05-09 07:48 AM
Bricklyne wrote:When it comes to the GS priorities for AC develpment, my guess has always been that they pay attention to the big companies that are using the product in bigger projects. Teamwork and new shell might be a hint of this (although until I get to play with shell, it looks like a "you wanted modeling freedom? there. let me work." statement).
The only thing that results from such a strategy in the long-term and from a PR and business-model perspective is that they lose more customers and users who stop using the software altogether (let alone just visiting this forum) as they justifiably believe that nobody who develops it cares what they think or to improve it to help make their work easier. And of course, that means less dineros for GS (money to spend on developers, R & D, PR and marketing (sorely needed here in North America), etc).
I mean, why spend my money on this software if I don't believe that it's not going to continue making my work easier and more efficient let alone pleasurable instead of banging my head against the wall to do the simplest task in the most rote complicated and repetitive method available?
Bricklyne wrote:And it is because of this that users are happy with what they get. Really happy. When there's something the product can't do, they get the answer directly from the source "we'll look into that, it is planned, it's not in our priorities, no it can't do that and it won't BUT you can do this or this until we solve it, etc".
In the Chaosgroup forum (the developers of Vray) you'll constantly find Vlado - the person who actually created the software - constantly answering users' questions and talking with them. Brad Peebler, the developer and creator of Modo does the same in the Luxology forums. Ditto Chema in the Fryrender/RandomControl software and forums. The developers of Maxwell and the creator also used to do the same until they had their little fiasco with their RC/Beta program, after which point they hired a full time PR person to deal with the PR direct engagement issues. But the developers still talk to the users.
rwallis wrote:This is what I meant when I said the software is being developed over the same old core, without looking to future needs.
Personally with every release I get more and more concerned about the future of ArchiCAD. As a relatively long term software (in the software world) it has not really seen the core upgrades required by 'future' demands with the speed and depth required to be competitive.
rwallis wrote:Exactly! It would actually seem like GS tried to create a side market for the basic needs. I'm OK with add-ons that make work easier, or extend functionality, but not with things that should be part of the core functionality. And some things might start as add-on extensions or improvement ideas, but when it comes a time when it must be part of the program, people just start to get angry as to why they need several purchases to complete a working package.
As long term users we've grown to accept ArchiCADs shortcomings, e.g. rendering (use Artlantis/ Maxwell etc - forget Lightworks), Stairbuilder (buy an add-on).
Unfortunately core level stuff is something we cannot cover with add-ons. And the more 'other' stuff we have to buy, the less viable ArchiCAD becomes.