Steve’s post recently reminded me of something I have done in the past – using multiple pseudo usernames to access the same Central File in different instances of Revit.
Let’s say that you wanted to render a certain scene in Revit, and then save the resultant image to the Project (a Central File). As this render could take 10 minutes, you want to keep working on something useful in the same Central File. What to do?
You just need to open a new instance of Revit and change the Username, then open a Local Copy of the Central as per usual. You now have 2 instances of the same Central model open, and you can work in and Synchronize from both of them … obviously you are going to need some decent hardware if you are working on a large central file with links. Set the first instance to render, and work in the second instance while that is happening (keep in mind that local renders in Revit can use multiple cores, so you may want to think about manually adjusting core affinity).
The username can be changed in the Revit Options dialog:
From Steve’s post: You can however change your username anytime you want when you work in a central file. It isn’t a great idea to actually work this way, switching usernames as you go. It is however a way to clear out users that have not relinquished worksets properly though. When nobody else is working on the project you can open a central file and pretend to be the ill mannered users that haven’t relinquished elements properly. It’s another reason you might consider working in a central file, even though it is generally frowned upon.
Here are a couple of system utilities that may help you to squeeze maximum performance out of your hardware (to speed up Revit, of course). Actually, my FX580 was struggling a bit with Showcase, so I wanted to overclock it a bit to make the augmented reality plugin work a bit more smoothly…
GPU-Z is a handy information tool for your video card. If you are overclocking, it will tell you the current clock speed, as well as the default. It will also tell you the driver and Forceware version that you are running, as well as additional advanced performance information.
Standard Casework families can not join geometry in the project environment, but Generic Models can. There are various opinions on how to handle this. From RFO:
Aaron Maller (using Generic Model, non adaptive): Ours are generic models, non-line based, and we join geometry. It reports quantities correctly but conservatively, since a mitered corner reports both full lengths. But i prefer it that way. AC’s are nice, but since they havent made one that is multiple point with point number dictated on the fly, im not making 7 different families so i can have a 2, 3, 4, 5 and so on.
Alex Page (Generic Model, but using subcategory): Ours are Generic models (on a subcategory called Casework) so we can successfully use the join tool, and line based for ease of use…
Steve Stafford (Casework, adaptive): ah youze guys are chickens I made this one in less than five minutes from scratch. Not much more work than the old in-place deal. Make a few versions and you’re “done”.
Old 2006 post on AUGI, listing the then ‘joinable’ categories: It seems to be that only elements of some categories can be joined. Using the default Revit Building template, these are the categories that can be joined: Ceilings Columns Floors Generic Models Mass Roofs Structural Columns Structural Foundations Structural Framing Walls
If you want to use SharpDevelop: “yourdrive:Program FilesAutodeskRevit 2013ProgramSDAbinSharpDevelop.exe”
Just drag and drop the solution file into the SharpDevelop window.
Running the command, I get a couple of different errors. One is: Revit encountered a Autodesk.Revit.Exceptions.ArgumentException: Box is empty Parameter name: box at Autodesk. Revit.DB.View3D.set_SectionBox(BoundingBoxXYZ section Box) at SetSectionBox.Command.Execute(ExternaiCommandData commandData, String& message, ElementSet elements) at apiManagedExecuteCommand(AString* assemblyName, AString* className, AString* vendorDescription, MFCApp* pMFCApp, DBView* pDBView, AString* message, Set< Elementldstd::less tnallc< Elementld> > • ids, Map tnallc > * data, AString* exceptionName, AString* exceptionMessage)
Nice tip from Revit Rants on how to round values within a family – and it allows much greater flexibility as to the rounding increment. In the example below, Chris uses ROUNDUP to round to a 5mm degree of precision. You could combine his method with Shared Parameters to ensure that the resulting value is schedulable (make Param2 a shared parameter in the example given below):
Quote: I have a parameter called “Param1” that I want to drive “Param2” from.