“… different parts of a model can be viewed at a time by splitting the Scene View vertically and horizontally. The options can be accessed from the View > Scene View > Split View drop-down. …”
from Sham Tickoo at:
Conquer Navisworks
We have come across a slightly annoying issue: someone modifies a Linked DWG file in AutoCAD, and upon reloading in Revit, the Import Scale will have been somehow automatically and incorrectly set to some Imperial conversion factor.
The fix is relatively simple – just reset the Import Units and Scale Factor to correct settings:
The cause of this particular seems to be that some users are modifying DWGs in versions of AutoCAD and saving them in newer formats than Revit can understand. In this case, Revit 2012 was not impressed with 2013 DWG files from AutoCAD 2014… If the AutoCAD Options Dialog, Open and Save was set to save as an older DWG version (like 2004), there was no problem. However, if the file was saved to 2013 version, this would trigger various errors from Revit 2012 when trying to reload it.
In the course of this change (including messages about “Do you want to import from Paper Space” etc), Revit 2012 basically modified the Scale of the DWG. The trigger point for this could actually be when you try re-linking the DWG, because it seems to have “disappeared” after the version problem. When finally resaving the dwg to an older version and reloading to fix the scaling problem (often associated with a fatal error / crash), the Scale would probably have to be reset as detailed above.
This PDF may be useful:
http://communities.autodesk.com/india/sites/default/files/india/resources/Acad-imports-issues.pdf
Read about it on the Help page:
http://help.autodesk.com/view/ADSKFD/ENU/?guid=GUID-C5218E9E-5122-4720-B62D-A968F96A7D02
From Labs blog:
“updated version of Falcon with an improved user interface for the stand-alone version (PC and Mac) and some upgrades inside Inventor and Revit.
…
Here are the features honed by the Autodesk Labs community:
- 64-bit solver process with greater access to memory
- Expanded graphics card and driver support
- Voxel size and overall tunnel size information
- Solution status indicator
- Ability to key-in specific values for velocity, resolution, orientation, etc.
- Expanded CAD imports (ipt, iam, sldprt, prt, x_t, STEP, etc.)
- Ribbon-style controls, standard menus, and model navigation cube
- Color banding and contour display options
- Revised tunnel and flow line seed box size controls
- Improved video recording controls and feedback
- Simplified iso-surface controls
- Saved run configurations for fast recall of past runs
- Multi-axis wind tunnel orientation control inside Inventor
- Pressure shading on building surfaces inside Revit
- Wind velocity profile option inside Revit”
PDF download:
http://labs-download.autodesk.com/us/labs/trials/worldwide/AutodeskFlowDesignInformationBrief01132014-2.pdf
Read more:
Project Falcon graduates from Autodesk Labs to Autodesk Flow Design – It is Alive in the Lab
I don’t think the API programmers should get scared just yet, but is there a day coming when visual programming will completely replace custom code? Julien seems to think so:
“I firmly believe Dynamo could be used for many many purposes, and addin-like behavior is one…
Definitions are easy to share and update. Users can tune them with only some basic Dynamo skill. It is not the same with addins. It is a lot of work to manage and deploy. And users will not be able to tune things. Same thing for macros.”
Read more:
API or not API: addins vs Dynamo in Revit | AEC, you and me.
Heads-up: https://twitter.com/Jbenoit44/status/414322858823659520
Tim over at the RevitCat has put together a nice writeup on component stairs, and specifically, landings. Some of you may have struggled to place a landing at the top of a stair flight – particularly when dealing with multistorey stairs. Along with other tips, Tim shows you how…
Here is the key to the workaround:
Place an extra run at the top so that Revit creates an automatic landing; then delete that run – the landing will remain, but will be converted to a sketch based component
Read the whole post:
http://revitcat.blogspot.com/2014/01/revit-stair-landings-part-1-creation.html
I recently posted about converting Topography to massing forms using a somewhat “manual”, yet lofted and smooth, method:
Convert Revit Topography into Massing Forms
Harry provides some code to do a similar thing with triangulated flat faces over here:
Read the whole post with macro code
Heads-up via:
Creating a Revit mass from Toposurface geometry https://t.co/pzaunaJlQU via @BoostYourBIM
— Ben Malone (@BenPMalone) January 13, 2014
Its already across the Twitterverse, but in case you missed it:
2013:
IFC Exporter for Revit 2013 (v2.16):
IFC Export Alternate UI for Revit 2013 (v1.16):
2014:
IFC Exporter for Revit 2014 (v3.8):
IFC Export Alternate UI for Revit 2014 (v2.8):
This topic is somewhat of a work in progress (I know Julien and a few others have been chasing how to make this happen nicely). Lev Lipkin made a comment on the thread, which reads a bit like a how-to, but to my knowledge it is probably more of a wishlist at this stage.
First, a few basics for setup:
- Install Vasari Beta 3
- Open / activate Vasari
- Install Dynamo (experimental builds here). If you want to try DynamoDS, here is the current download. (Remember all that talk about Dynamo and DesignScript merging? DynamoDS seems to be where its happening…)
- Packages – Search for a Package
- Install relevant packages / nodes and…
Then, have a read of this:
Comment here
Quoted below:
Permalink Reply by Lev Lipkin
Dynamo when working on Vasari beta 3 has node “Face From Points” (which needs n x m grid of points) and “Replace Solid Faces” (which would keep adjacent faces as bounds of the resulting Solid). Resulting solid could be put into Form using “Bake Solid as Revit Element” node. Hope this might help.
While you can use Highlight in Model from a Schedule, there is no similar command relating to a ‘current selection’. If you have somehow selected an object and want to “find” it so you can actually see it, what can you do?
This:
- Select the object
- Manage – IDs of Selection
- Ctrl+C (copies the ID)
- Manage – Select by ID
- Ctrl+V (pastes the ID)
- Don’t press OK, instead
- Click Show. You can cycle through various views by pressing Show multiple times.
To speed this process up, map some keyboard shortcuts to IDs of Selection and Select by ID.
I have posted about Profiles and Adaptive components before, but more recently Tim Waldock put together a nice, detailed post on the subject over at this link.
In the post, he states:
You can host it on a divided path node; but don’t bother to convert it to a repeater because it cannot then be used to create a solid form.
Technically, this is true. If the element is not a Repeater – just a set of Profiles in an Adaptive, you can then Tab-select until you get the “closed” loop of lines, and use these to generate forms. In other words, you aren’t selecting the Component – just the lines inside the component. It can be a little fiddly, but it does work. This is only really necessary if the normal workflow of selecting the Components and using Create Form does not work or is not available.
However, when it comes to Repeaters, even the above idea does not work.
Neither does “doubly nesting” another shared Component inside the Repeated Component.
One of the few things you can do is to select a Line in the Repeated Component and use the Divide tool.
You are then left with using the Repeater to set up a “rig” to place multi-point line families on or between, and using this skeleton to generate forms. In some ways, it depends how parametric and adjustable you need the resulting form to be…
