andrewharle8552 wrote:
ToanDN,
You are missing the point. When the program does not behave in accordance with its underlying logic, you have to troubleshoot to find out why, particularly where you can't use the project browser to select the element in question.
@andrewharle8552
Revit is only a tool (it is not 100% perfect; no Software or platform I have used so far is); however, how it is used is up to the user. For that reason some of us employ strict Guidelines and Best Practices on what a user MAY and SHALL not do. When a user goes rouge and does whatever, one can't blame the Software that it is not behaving with its underlying logic! At least...not on this one
andrewharle8552 wrote:
None of us knew that there was a shaft in a future phase. It should not have been there, as the stair shaft it was meant to be forming was in the current phase, and other staff had drawn floors with the boundary creating the stair shaft. I myself was unaware there was a future phase in the model.
We can learn from the experience and ensure it doesn't happen again (saving 20 minutes x 3 people), but because we did not know it was a phasing issue even a search on the internet did to come up with the solution, because we didn't put 'phase' as one of the search terms.
How would you know!!!
Any other user might or can also place elements here and there mix up worksets, Phase to his liking, bloat your central with exploded CADs and the list is infinite when it come to how to mess up a model User vs Software. Who is to be blamed for that? Not the Software for sure. I would blame that on bad practice and unqualified Team members (if not Team leaders)
Troubleshooting is inevitable (applies to all Software) If it is done regularly and periodically one can avoid 90% of the mess. Revit gives and error (minor or major – regardless) and the users ignore. When that happens (for instance) one shouldn’t whine and complain after 6 months into the program that Revit is not behaving as one would want it to..
- Who maintains your Project's and who/how do you ensure that your Team is abiding to the set Guidelines and Best Practices? or does the process run itself and you guys just hope that all goes well in the end?
- When you get a new team member onboard what does he receive as induction?
andrewharle8552 wrote:
The frustration is that some things in the program don't fully work, are known not to fully work by Autodesk, and don't seem to get resolved. Their limitations are not spelt out in the online help - in this case that shafts cut slabs of all phases regardless of which phase they are in, which means it is unhelpful to have them allocated to a phase in the first place.
Revit, like many other leading BIM platforms provide tools with which one may do one things in a multitude of ways… they didn’t stop there; they even gave us access to Revit’s API and provided powerful tools such as Dynamo as well as interoperability with a multitude of software. It is the user who frustrates himself by limiting his options as well as his knowledge. Frankly speaking, the options provided by Autodesk Revit are close to limitless and when one tool doesn’t work the way one wants or expects it to doesn’t mean that such tools do not fully function the way they should… Many tools are also not meant to be used the way the user wants them to.
Back to the case of the shafts phasing…When one wants to phase horiyontally, one should not place or span vertical element unless those elements are phased separately...example a towers Core has it’s own phasing independent from the floors...it is a strategy which should be set before the Project Begins - how to split and how to Phase (One also can't blame an ex employee who did something to his own logic due to the lack of clear guidelines)…Therefore, when one wants to phase shaft openings by floor/slab then he uses/place X shafts (by tool) instead of one which spans from bottom to top…Personally I would still use a Void Family (for a dozen of other resons) … Same applies to almost every element one wants/plans to Phase
Unsubscribing to post ... apologies for not being able to entertain future replies to this thread but comments to PM inbox are always welcomed
