@MKFreiert wrote:
mastjaso
it seems that there are some things you don't understand about revit, and that's fine, it's what this forum is here for. to learn about your tools and how they work. we all learn from each other.
being willing to understand how the tools behave is critical to working with them, rather than blaming the tool. if some of these "impossible" things were easy to implement they would be built in. i've *repeatedly* explained why this particular item is NOT simple (or necessary), and i'm not even a programmer or data base admin, but i've learned enough about how revit works to understand why some stuff isn't feasible, easy, or in this case actually very desirable.
that understanding also helps troubleshoot problems my users have, and helps me to understand unexpected behavior within projects. it's kinda like knowing how your opponent usually plays in a game of chess.
You're right, I don't understand everything about Revit, but I've used it enough, and used the API enough that I have a pretty good understanding of what works, what's possible and what is completely technically infeasible. And this room issue, is by no means technically infeasible.
But first of all, unlike you keep trying to insist, Revit is a tool to create construction drawings (a drafting tool as you keep calling it). Can it do a bunch of cool stuff with it's calculations and it's database? Yes. But until the day that contractors start regularly getting models as the deliverables, those cool things are just to make drafting construction drawings easier. The millions of licenses that Autodesk has sold to AEC firms, haven't been sold as a tool for making a cool virtual model of a building, they've been sold as a tool for producing better construction drawings. Any regard that it fails at that it fails as a tool. There are better and worse ways to use it, but also a lot of ways in which it really really sucks as it's purpose, or does things super inefficiently.
But back to the topic at hand, a room in Revit is fundamentally just a point. That's where the X's cross, and that point looks out from it's location to find bounding elements and create the room volume. There's no reason that volumes couldn't change with phase, except that that is how Autodesk has chosen to implement it. There is no huge show stopping technical reason they couldn't change it's behaviour beyond the fact that it would take a bunch of work and Autodesk has no competition to actually put a lot of work into improving Revit.
@MKFreiert wrote:
autodesk and revit are NOT perfect, but they do keep improving. maybe not in the ways that you or i want, but generally in useful ways. (but not the ribbon, don't get me started on that debacle of a UIX mistake)
all that said, i'll digress and fix one of your complaints (they all have solutions):
include a symbol within the family and set your model object visibility off in plans and rcp within the family.
we're now way off topic.
None of the things I've complained about have solutions without diving into the API, it's pretty ludicrous that you've even claimed you can "fix" the text editing issue, or the title block issuance issue.
Regarding the light fixture, no, that is not a solution to the problem. Light fixtures need to be face based, if they're face based and hosted on a vertical face then the annotation symbol displays parallel to the Plan / RCP so it's not visible. In the "Lighting Device" category (or "Electrical fixture", "Security Device", "Nurse Call Device" etc.) there's an option for "Maintain Annotation Orientation", but for some reason this does not exist for the "Lighting Fixture" category. Take a light switch family and change it to lighting fixture and it's symbol disappears.
it seems that there are some things you don't understand about revit, and that's fine, it's what this forum is here for. But don't just blindly defend Autodesk and say that things are technically impossible if you don't understand how the underlying database works. Most of these things are possible, and some may be difficult, but having a software engineer spend 1 month on a problem that would save every AEC firm hours of time on every single project is more than worth it, it just doesn't happen because AEC software is not an economically competitive industry.