Readme:
http://download.autodesk.com/SWDLDDLM/Updates/ReCap/Autodesk_ReCap_2015_Hotfix1.html

1.    This hotfix addresses Heartbleed vulnerability – a security bug in the open-source OpenSSL cryptography library. Heartbleed is registered in the Common Vulnerabilities and Exposures system as CVE-2014-0160. For more information, please visit the CVE dictionary at http://cve.mitre.org.
2.    This hotfix fixes the bug in ReCap that project file might be corrupted or deleted when computer went to sleep or shut down during scan importing.
3.    This hotfix fixes the bug in ReCap that PTG with only intensity are imported as all-black.
4.    This hotfix adds the support for US Survey unit in ReCap.
5.    This hotfix fixes the bug in ReCap that project cannot load on A360 if map images do not exist in Temporary Cache when publishing.
6.    This hotfix fixes the memory allocation error in ReCap during registration.
7.    This hotfix fixes the bug in ReCap that export might fail under certain conditions.
8.    This hotfix fixes the bug in ReCap that region is not displayed properly when reopened after deletion of points.
9.    This hotfix fixes the bug in ReCap that project save as function is not copying all support files to destination folder when merging several projects.

I recommend trying the Explode button:

Press the structure button Structure button to browse down through the model’s assembly structure or component hierarchy. You can use this to isolate specific components in your model, hiding everything else.
After hitting reset Reset button, now try the explode button Explode button and then manipulate the slider that appears at the top of the window to move the various model components outwards from the centre to form an exploded view.
Aside from the need to support a huge array of formats, the viewer is really good at streaming large models – displaying them at appropriate levels of detail – and allowing you to get in and work with the structure of these models.

via full post:
A sneak peek at the new Autodesk 360 viewer – Through the Interface

As one of the reviews states, this is a “very fast” way to open and view FBX files.

New in FBX Review v1.2

  • Added support for geometry and textures contained in a zip file.
  • Added support for geometry caching: Maya cache, 3ds Max cache, and alembic format.
  • Added Camera refocusing based on user-targeted area.
  • Added support for iOS and Mac OS X operating systems. 

Download at:
Autodesk FBX Review – Windows 64 Bit – Autodesk Exchange Apps

Or for iOS, Mac OS, Win 8 see below:

iOS 7.0

Visit iTunes online or browse in the App Store directly to download for iPhone or iPad.

Mac OS X

Visit the Mac App Store to download for OS X.

Windows 8

Visit the Microsoft Windows Store directly from your Windows 8 device.

Windows 7

Visit the Autodesk Exchange Store to download for Windows 7.

Part of working in a BIM environment is putting together all of the little pieces that you know and turning it into a useful workflow. Do you have a 3D file, such as an FBX, that has some camera views saved in it, and you would like to convert these to BCF, perhaps for eventual import to Revit or some other application?

Navisworks can help here. It is pretty smart when it comes to most 3D formats. Importing an FBX will bring in camera views as Saved Viewpoints. If you have an FBX file from 123D Catch, it will contain Camera views that match the actual camera locations. Here’s what to do:

  1. Append the FBX to Navisworks 2014
  2. Use the addin and method here to export from Navisworks viewpoints to BCF issues
  3. Import to Revit or your software of choice using the relevant BCF importer

Quotes:  
Throughout the design and construction process, the project team used Building Information Modeling (BIM) solutions from Autodesk, including Autodesk Revit Architecture for 3D architectural design and project visualization, Autodesk Navisworks Manage for whole project visualization and coordination, AutoCAD for project documentation, and Autodesk 3ds Max Design for advanced 3D rendering and animation. 
 
The team also used Navisworks Manage to perform formal clash detection. “For a building with such complex functions as this hospital, there is normally a great deal of rework that needs to be done during construction,” says Fujiki. “But on this project, Autodesk BIM software helped us identify and solve coordination issues during the design process. This helped reduce the amount of expensive rework during construction-improving construction efficiency and quality, which ultimately benefits our client.” 
 
The project team also used Navisworks to evaluate construction logistics. For example, models of several large construction cranes were added to the Navisworks model to study crane placement. The crane arm was rotated to check the range of the crane and identify placements that involve the least amount of rotation. “The value of the Revit and Navisworks models increased as construction complexity increased,” reflects Hosoda. “Autodesk BIM solutions provided a more thorough grasp of the whole building and had a major impact on the understanding of the workers at the site.”
 

Read the whole article:
78717-First Experience with BIM Proves Highly Successful for Japanese Designers Collaborating on Complex and Advanced Hospital Design

When exporting to IFC, you may find that Revit feeds the Survey Coordinates (or shared coordinates) to the resulting IFC file, when in fact you want it to be based on Project Coordinates.

If your project team is using origin-to-origin linking, it will be almost vital that you neutralize the Revit survey coordinates immediately prior to exporting to IFC.

This is quite easy:

  1. Make a new file based on a blank template
  2. Insert a origin locator dwg and draw a couple of model lines over the top (this is purely to give you something to “pick”)
  3. Save and close this blank RVT file (and keep it for future use)
  4. Link it into your live Revit project
  5. Use Acquire Coordinates and select the new, fresh, blank RVT file
  6. Save As this temporary RVT with neutralized survey coordinates to somewhere
  7. Now Export your IFC

Your resulting IFC file won’t be confused about which coordinate system to use – it should now Append to Navisworks and other software using the same origin-to-origin coordinate system as that in the originating Revit project.

Konrad Sobon has put together a Dynamo definition that parses a Warning HTML from Revit, picks out those associated with a particular warning type, and then lists the associate element IDs so they can be isolated in a view. What Revit Wants is this kind of cool.

Original post:
http://archi-lab.net/?p=94

Video demo:

Check out his channel for more Dynamo things:
https://www.youtube.com/channel/UCr_CFVPDPN53DxFjPRs7wZQ

You can also:
Download Dynamo here