Posts tagged Revit
“Hey, we decided we don’t need any revisions for the next issue.”
Sure no problem.
Except your project has 1,381 Revisions in it, across 140 sheets…
… and they’re all hidden…
… and as everyone knows, you can’t delete that last revision from Revit.
Hit run, bye bye revisions!
I’ve removed the link from the boolean to the python script and set it to False, just in case. This graph is, of course, nothing new. You can use it to delete every instance of any category in the project you wish so use responsibly.
Next challenge: Delete revisions from specified revision#/name/sequence#/etc!
Till next time!
Ever had one of those things that you always kinda knew, but didn’t REALLY know until you looked at it from outside your box (I thank Bruce Mason, my middle school Target teacher for the ability to do this)?
So today I was thinking about all the hate that Revit gets, even from me; especially from me. I was wondering, why is it that people hate revit? I realized the better question is “When is it that people hate Revit?” My personal answer is when I’m on deadline and Revit decides it is a pre-adolescent script that wants to say no to everything. Or in other words, when it doesn’t do what I want it to do. This is typically due to having to deal with the way architecture works with technology. Most instances of Revit failures with me have to do with the hardware hosting the program and not misuse of the software so where the industry meets the technology is where the typical battle line is drawn.
So how does this apply to how the typical Revit hater hates Revit? It seems to me that there is an inherent hate of technology in Architecture. Unbeknownst to a lot of people, Architecture is nothing more than critical application of common sense just like magic is nothing more than misdirection. The success of both is determinant in the flourish of the hand to produce the desired results. In Architecture the flourish is the Art side; drawing the lines, making them perty and impressive. A lot of Architects live and die by the line, how perfectly drawn it is, and the contractor’s ability to interpret it as a real object.
What I realized in this existential moment today is that a majority of the push back I receive from people on Revit is when I basically tell them that they can’t just draw a line, or just move a line. Usually it’s masked in the form of “I want to change this section, the wall needs to be 6″ stud instead of 8″ and the sheathing should only be 1/2″…” and typically they come from an environment where it’s just a matter of changing the lines to match. When my response is that they have to change wall types or floor assemblies or material properties to achieve this… that is the moment that Revit sucks to them.
I don’t think it’s the fact that they have to pay attention to how the building is actually going to be built and that they now need to be completely coordinated across all drawings in the model. It’s the fact that it’s not as simple as just manipulating the lines. They have to open a dialog box, sometimes 2, understand which layer it is they are looking at in an assembly, translate that to another section of the dialog box with dimensions in it and then hope that this changes the right line in that view. What if it was as simple as just manipulating a line? What if I could change a wall assembly by moving just the lines and that updated the entire assembly in the model? Would you still hate Revit that much? I really feel that the frustration comes from such high-order actions required to complete low-order tasks. Can we find a solution to make low-order tasks require low-order actions, not for the sake of making it easy for everyone but for the sake of making it intuitive to how we design and draw as an industry?
What have been your experiences with push back? Is it because of the complexity of the action required to complete the task? What have you found to be the case?
This is how you handle coordination in AutoCAD:
“I see structural members in our RCP where I’m trying to put lights…”
“OK, just delete those lines”
This is how you handle coordination in Revit:
“I see structural members in our RCP where I’m trying to put lights…”
“If you see it in RCP, then it’s below our ceilings and we need to coordinate it with structural.”
I wish people would realize that if you’re working on a revit project, if you do markups in DWF instead of PDF, you can ACTUALLY OVERLAY THEM IN REVIT!!!!
So the time has finally come! The NDA has been lifted and the features are flying… well at least from those of us who actually waited for the NDA to be lifted. Here today I’d like to “briefly” list some of the new features in Revit 2013 and then spend the next weeks days going over some of the more exciting ones!
- Push Revit.ini updates to multiple users
- DGN V8 export added
- DGN export dialog updated
- Levels, Lines, Line Weights, Patterns, Texts and Fonts now mappable in the DGN export
- DGN export configurations now save to the project file and are now transferable project standards
- Import DGN design models
- DWF now exports phasing info
- Manual naming of multiple views/sheets now available in DWF export
- Views and Sheets now displayed alphabetically in export dialogs
- Revit text elements now assigned to text style in DWG exports
- Unreferenced Error fixed for images exported from Revit to DWG
- Hatch pattern scale fixed for DWG exports
- Transparency in Revit now exported as Object Property in DWG exports
- Ability to hide Scope Boxes, Unreferenced Views and Reference Planes now an option in DWG exports
- DWG export of 3D solids now a Revit.ini switch
- “Correct Slightly Off Axis Lines” added to DWG import options
- “Center to Center” positioning now uses center to center of the view on the X-Y plane
- Shared Coordinates now kept when importing DWGs
- IFC… let’s just say they improved it quite a bit!
- UI & Rendering
- Ribbon and Command naming more consistent across all platforms
- Command name alignment more consistent
- Commands in different verticals have icons which better reflect that discipline’s use of the command
- Ghost Surfaces and Transparent Override replaced by Surface Transparency Sliders
- WARP replaces OpenGL to allow Hardware Acceleration on all computer builds!!!
- Anti-Aliasing available in ALL views now with improved results and performance
- RPCs now visible in Realistic Visual Style
- Sky, Image or Background options now available in Elevation, Section, Isometric and Perspective 3D views
- Artificial Lights now glow in Realistic Visual Style along with Photographic Exposure option
- Ray Trace Visual Style mode added to view styles
- Save and Load selections available in all platforms
- More filter control in the Visibility Graphics dialog categories lists
- Project Template library support added in File Locations
- View Templates now lockable to views as well as automatic updating of a view once a view template is assigned to a view
- View Template parameter now schedulable
- View Types are now manageable for nearly all types of views via type duplication and view lists
- Plumbing is now an option in the Discipline parameter for views
- Set default view discipline on creation of new views
- RCP underlay orientation now defaults to “Reflect Ceiling Plan” instead of “Plan”
- Color Schemes now configurable in view templates
- “Workset Global Visibility Settings” is now a Project Standards workset that is editable and able to be checked-out
- Site tools added
- Revit (One Box)
- Access to tools and functionality of all Revit verticals
- Setting discipline during install will customize UI for that discipline
- Construction Modeling
- Merge parts into a single part
- Exclude parts to prevent scheduling and from showing up in views
- Restore parts brings excluded parts back into a part
- All faces of parts are now available for shape editing. Resettable
- Divide parts with parametric gaps
- Divide parts with custom profiles. New Category “Division Profiles”
- Parts inherit parameter values from their parent source
- Parts now Import/Export from/to IFC
- Assembly view creation has expanded dialog options
- Assembly view creation dialog remembers last settings per project and per user
- Assembly views can now be placed on normal sheets. Normal views can now be placed on Assembly sheets
- Assembly views allow rotation on sheet
- Assembly Views transferable to other Assemblies
- Assemblies now have Assembly Origins
- Assembly types
- Assembly export to IFC
- Entire materials system concept reworked
- New materials interface.. completely new, not even remotely related to old interface
- New Structural data for materials
- New Thermal data for materials
- Savable Material Libraries
So here’s the next installment in the Family Creation series. This is the continuation of our talk about planning out the families and getting everything ready before you go into the family editor. I talk about a strategy that I’m developing which I feel works pretty well, and involves separating out the Content, Structure and Style of the family and finding a way to make each independent of the other. Hope you enjoy, and I’ll see you around for the next installment in a couple of weeks!
Recorded Session: http://www.anymeeting.com/rfowebinar/EA54D781824C
Yes! I’m really going to start this back up. A post here, A post there. Maybe one in between. Either way, I’ll be trudging through this series as well as posting the occasional impromptu tutorial post. In the meantime, I’m going to just leave the text that I wrote over 9 months ago and just let it go from there. It’s actually quite short and is just another large step on the way to understanding families. Enjoy, comment and see you for the next one.
Well, I thought all this preliminary explanation that is leading up to family creation would bore everyone, but I’ve never had so many hits on my site! This is awesome! I thought I was going to make the next one a preemptive strike on modeling and get down and dirty with some geometry creation but seeing these stats kinda makes me think I should just chug along; those who are looking for geometry creation will be back in good time.
If you don’t know by now, I’m a KS junky… that’s Keyboard Shortcut for you mouse clickers (try it, try typing KS in Revit to see what happens!). So it occurred to me that I should share another quick KS that I use quite a bit.
A personal preference of mine is to halftone objects that are being called out in an enlarged plan. This makes any dimensions or tags that are in that area pop out and become more readable against those objects. So as you can imagine I do a lot of half toning of individual objects. To prevent pulling my hair out in trying to get certain categories grouped or any fancy trick like that I usually simply halftone the individual objects using element overrides.
Believe it or not, there is actually a KS for this already provided in Revit: “EOH” If it’s not already in yours, maybe it should be. Simple to add. Search for halftone in your KS dialog and look for the highlighted command below.
That’s it for today. Thanks for stopping by and I look forward to seeing for the next BIMTotD
Someone recently told me I need to find the balance between modeling and drafting. I asked them why and their response was “I’M AN AUTOCAD USER DON’T QUESTION ME!”.. no seriously, I have no clue what their response was because I stopped listening once I realized that the reason they didn’t want to model things was because they didn’t know how. So in response to those people who think that modeling is a waste of time, but can’t justify it other than “It takes too much time” (so does a good scotch, but you wouldn’t really want to skimp on that would you?) I have created the following…
Image source Hyperbole-and-a-half