I'm not an MEP user, therefore technically don't really have a bone in this fight or a stake in all this (....not really true.....but I'll circle back to that later).
So I hope my ignorance on any part will be excused, but as I was passing by, I just can't believe some of the things I'm reading on here.
We (the non-MEP/Structural/DDSCAD Archicad users) are under the general impression that a large part of the reason we've hardly been getting any (substantive) improvement to the ARCHITECTURE and design tools in ARCHIcad over the last several versions has been because Graphisoft has been dedicating a large amount of resources in this drive to make it the Swiss-army knife of AEC BIM tools with the inclusion and improvements to those tools related to Structural, MEP and DDSCAD taking primary focus.
So imagine my shock in learning that poor MEP tool users such as yourself aren't even getting the basic satisfaction of a working tool out-of-the-box sans a couple (or several.....who know) hotfixes or updates.
So what the hell are they actually spending the development resources on over there at GS HQ, if they can't even get basic quality assurance (Q/A) on new tools and solid beta-testing and fixes done to esnure tools are production ready?
And why even release a half-baked, and not ready-at-all-for primetime tool as key feature release when you know it's not ready?
I realize that this is just a Graphisoft deal to do this sort of thing going all the way back to Complex Profile Manager in ArchiCAD 10 that couldn't do curved paths until ArchiCAD 11,...but seriously though,.....why?
And then to make things even more mind-boggling, apparently the solution is to go back down one version to continue using the older version of the MEP tool - WHICH, by the way, is essentially, or is supposed to be obsolete since MEP objects created in it will technically not function as such (...as MEP objects) with the new version.
What the he**????!?!?!
Surely, how can the solution be, "Go back and use the tool (or the version of it), that is technically incompatible with the current one (that's supposed to work, but isn't) and that we will no longer be supporting in the future".
That's not a solution.
That's not even a workaround.
That almost feels like a joke on some level.
Listen, I applaud and fully appreciate Balint for having the decency (...and heck, even the courage) to come here and address the concern directly, but you can see and understand why we, the users tend to get super-frustrated with what's happening over there (or not), when we end up with situations like this, no?
I don't even use this tool but I totally understand the frustration of those who do, and commiserate with their anger.
And in terms of it not affecting me (because I don't use the tool), that's not even true.
It does affect everyone else, because if we're correct in our understanding that this is where all our subscription fee and license fee-funded development resources are being dedicated to, how does it bode for the tools we actually want improved, when even more of those resources will apparently now have to be spent to fix the broken "other" tools we're supposed to be patient in waiting for Graphisoft to implement, before they finally decide to remember that Architecture users also exist, 3 or 4 versions down the road and might want some of their tools improved and fixed as well then?
This is all very painful.
I'm hoping for all your sakes they do fix the MEP tool and have a (fully and properly) working version by the next couple of updates, because if not,.....then God help us all.
Still looking?
