RTV Xporter Pro is one of those addins that I can safely recommend to every Revit user. If you ever need to print more than one sheet, or export a model multiple times, or to multiple formats, this tool is going to save you time. In fact, I think a large percentage of Revit users probably already have it! So, what’s the latest?

As you probably realise, Collaboration for Revit (C4R), Autodesk’s ‘Revit Server in the Cloud’ solution, is gaining popularity globally. It is genuinely a good way to get a team of people in different places to work together in real-time on a Revit project… provided you have good internet that is! So, it is great to see that RTV have now supported batch exporting from C4R projects using the local desktop application. Nice work!

Another interesting feature is that you can now reference additional Revit projects to the current Document Issue / Transmittal record, which is pretty cool.

The latest build for Revit 2017 is 1.0.740.

Oh, and one final thought… if you haven’t tried RTV Xporter in a while (perhaps you recall the days of working with SQL Server and so on), I recommend you give the latest version a try. On almost every project I do, we do not need to use a SQL server because the addin just integrates so well with the information you already have in you Revit model.

How to Batch Upgrade Any Revit File Type
A while back, I posted about an admittedly circuitous method to upgrade Revit files for free using eTransmit.

However, this is a much quicker and easier way, and its pretty affordable too… using RTV Xporter Pro. It supports batch upgrading of every Revit file type: rvt, rte, rfa, rft

To use it, just click the File Upgrader button and fill out the dialog. Easy!


Other related post:
What Revit Wants: Various methods to upgrade your office RFT files to 2013

RevitworX: Upgrading Files to 2016

Here is the full list of the latest updates, from the newsletter:

We have been busy working hard to integrate Collaborate for Revit (C4R) with our RTV Xporter PRO App for Revit. It is our pleasure that we are now able to provide C4R access via the desktop application (only). At this time our Remote Processing (Server) doesn’t support C4R but we are working hard to get this functionality added as soon as possible.

The updates are now available for download from our website and can be found here:
RTV Xporter Pro 2016 (Build 709)
http://www.rtvtools.com/downloads/2016_RTVXporterPro_64B.zip ;and
RTV Xporter Pro 2017 (Build 740)

The following is a list of new features, updates and fixes included in the above software updates.


1. Scanning for PDF printers will only be performed on Export start up, if no registry printer or xml printer list is empty;
2. Multi-line parameter used for the export filename, New Line replaced with a Space;
3. Separate group for Title block Revision schedules in Views list;

1. Fixed DWG layer mapping file selection dialog displaying twice and multiple mapping files added to drop-down list;
2. Fixed Remote GUI when the root shared folder is defined as the watch folder;

New Features:

1. Checkbox option to Reset Adobe PDF print queue prior to export;
2. Delete button added to Export Folder and Export Filename template drop-down lists;

3. Issue, Reference Projects option now added. Users now have the option to reference additional Revit projects to the current Document Issue/Transmittal record. User can browse to select the project or used an existing (loaded) linked Revit project;

Note: Issue Reference Projects support linked models including C4R and Revit Server.


Web Update
4. New registry key added to disable check for updates by the users (restricted to system administrators);

5. C4R Support added – limited to current model, not available with the Remote (Server) function;

The fact that I’m posting about it means that it probably isn’t really that easy, right? There are a few challenging pieces of the puzzle that all need to come together to get C4R or Collaboration for Revit working on a real project. I just went through this process with a mechanical firm so it is all pretty fresh in my mind.

Firstly, note that A360 Team has been rebranded as BIM 360 Team and will be migrated, more details at this post.

Secondly, Autodesk really wants your whole team (like everyone, every consultant, every Revit link) on Collaboration for Revit. However, out in the real world it is just happening bit-by-bit, and in the meantime some hacks and workarounds can make the process a little bit easier.

A Quick Overview
Ok, so Collaboration for Revit runs on top of BIM 360 Team. What this means is that you need to have an active BIM 360 Team license if you wish to run projects. Then, you need a Collaboration for Revit license for each Revit user who will be connecting to that BIM 360 Team site. You still with me? This also means that persons outside of your firm may connect to your projects, provided they have their own Collaboration for Revit entitlement applied to their Autodesk account.

Once you have the BIM 360 Team license, and the Collaboration for Revit licenses, you then need to “Assign” the Collaboration for Revit licenses out to the users (using their Autodesk login details).

Finally, you need to actually do some stuff, like:

  • make a BIM 360 Team project,
  • invite the users,
  • initiate Revit models, and
  • get the links working.

Its a lot to take in, so you can see that the blog title is actually a half-joke 🙂 However, we were able to get all this up and running in about 4 hours for one firm, so you can too. Hopefully.

Something that will help
Given that there are a lot of moving pieces, I turned to my favourite research and documentation tool, OneNote. I have created a public notebook that you can view at this link:
Revit Collaboration Public Help


Basically all of the steps involved in getting the licensing setup, inviting users, installing the addin, and initiating models onto Collaboration for Revit are in the notebook linked above. I will continue to update and add to this over time.

Any Questions?
Just comment to this post and I will endeavour to answer your question in the notebook, or point you toward the answer.

Now, here are a few other bits and pieces that may be useful, if the notebook doesn’t answer your questions…

new help documentation:

moving models to folders:

You can move projects from A360 Free to a paid BIM360 Team hub by using the Transfer function:


Taking models offline and replacing later:

using local linked files

Download links:
Collaboration for Revit 2017
Collaboration for Revit 2016

Collaboration for Revit 2015

Recent chat with Autodesk

I have posted many times over the past few years about Project Skyscraper, which then became Collaboration for Revit (C4R). Having used the cloud service in beta, I was keen to get it going on some live projects. Unfortunately, Collaboration for Revit was only available in the USA…

Until now, that is! Check out this press release for details on the global launch. Quote:
Released and available in North America only since December 7, 2014, Collaboration for Revit will be available for commercial global use as of January 7, 2016.  




Autodesk A360 Collaboration for Revit is a service that works with Revit software to connect project teams with centralized access to BIM project data in the cloud.  Image courtesy of Autodesk

I, for one, am very excited about this. I have been involved in at least one geographically distributed vanilla Revit Server setup, and I think that the necessity to have ‘my IT people talk to your IT people to set up a DMZ between our VPNs’ is a bit counter-productive. In these situations, the global availability of C4R will really shine. Now, firms will be able to spin up a C4R instance very quickly and get working together, on real projects and in real-time.

You can hear Ralph Bond interviewing Sylvia Knauer on the Autodesk AEC Channel Podcast here in this mp3.

Between this global launch of Collaboration for Revit, and the improvements in the Glue – Navisworks connection in 2016 products, my Federated Model Streamer concept is one step closer to reality 🙂

This fixes the relatively nasty addin incompatibility issue that was floating around…

Direct link for Revit 2015:

Direct link for Revit 2016:

Known issues and Fixes:

I reported this issue on github a while back, but it turns out it is a reasonably serious DLL conflict. More details here:
Collaboration for Revit: 2015.6/2016.1 breaks other add-ins | Revit Products | Autodesk Knowledge Network

Users reported that installing the Collaboration for Revit® 2015.6 or 2016.1 add-in is causing other add-ins to stop working.
There seems to be a DLL conflict with the latest Collaboration for Revit add-in.
Status: This incident is currently being investigated for a possible cause and resolution
Incident ID: 72448
Workaround: Continue using the 2015.5 or 2016.0 version of the Collaboration for Revit Add-in.
Note: If you need to remove the newer add-in (Autodesk A360 Collaboration for Revit…), you will also want to remove the new version of the “Personal Accelerator for Revit” and “Dynamo 0.8.1”

This coincides with UR8, and interestingly includes an update to Dynamo 0.8.0. I would recommend using Autodesk Application Manager to obtain this entire package.

Collaboration for Revit v5 download:

Personal Accelerator:

This is the packaged Dynamo installer:

From microsolresources:
Select your project, and you will get a list of cloud-enabled models. Please note you will not see other data, such as Word documents or non-cloud enabled models.

When you click on the icon that resembles a floppy drive, you will have an option to View Versions.

Each of these Versions refers to an instance of Sync to Central.

On the far right column, we see Actions. If you click on the clock icon, you can roll back to a previous STC. You should exercise caution whenever rolling back to an earlier version. ALL NEWER VERSIONS WILL BE DELETED WHEN YOU ROLL BACK. In addition, anyone currently working on that model will lose their work, and any changes will be orphaned.

Read the whole post at:
Backing Up A360 Collaboration for Revit Models | microsolresources

This is ‘on purpose’, and it represents a new workflow. See below from Autodesk:
 … the new intended workflow: For file-based collaboration, as well as for Revit Server based collaboration, you would click the Collaborate button and select the LAN/WAN option.  This will create the default worksets and enable worksharing, after which you would save the model as a new central to the location of your choice (typically a local file share or a Revit Server host.)

So, the correct way to enable worksharing on non-workshared models is to click the Collaborate button, then to choose “Collaborate within your network”, as per the image below. Then Save the Central as previously. Finally, in a usual work environment you would immediately close the Central, and create a new Local before starting production work.

Also known as Autodesk Revit Collaboration Add-On 2015 English-US Locked 64-Bit Service Pack 4. This goes hand-in-hand with Revit 2015 Update 7.

Direct link:

Known issues:

Installation and Known issues text copied here:
Autodesk A360 Collaboration for Revit version 2015.4 can be applied to Autodesk Revit 2015 as a new installation, or as an update to Autodesk A360 Collaboration for Revit versions 2015.1, 2015.1.1, 2015.2, or 2015.3.

Note that this is a mandatory update; previous versions may cease to function at a future date.

Before installing Autodesk A360 Collaboration for Revit you will need to update Autodesk Revit with Update Release 7. Note that the installer for UR7 is specific to the variant of Autodesk Revit 2015 that you have, for example, Autodesk Revit 2015 vs. Autodesk Revit 2015 R2 (available only to subscription customers) or Autodesk Revit Architecture vs. Autodesk Revit MEP.  Please be sure to install the correct update for your installed version of Autodesk Revit.  Once you have installed Update Release 7 you are ready to install Autodesk 360 Collaboration for Revit.

New Installation
1.    Close all instances of Autodesk Revit 2015.
2.    Launch the installer, select the option to Install, accept the License and Services Agreement, and click the Install button.  This will complete the installation.
3.    At this point, your Autodesk Revit has been updated and is ready for use. You will need the appropriate entitlements to access the new functionality. (Please refer to the About A360 Entitlements section of the Autodesk Revit 2015 help for more information, link.)

Updating Existing Installation
1.    Close all instances of Autodesk Revit 2015.
2.    Launch the installer, select the option to Install, accept the License and Services Agreement, and click the Install button.  You will be informed that there is a previous version of Collaboration installed; be sure to confirm and allow the installer to remove the old version.  This will complete the installation.

 What’s new in this release?
1.    Performance improvements when Revit is downloading data from the Collaboration service.2.    Users now have the ability to control the model views that are published to the A360 project. The default behavior, to publish the default 3D view and all sheets, remains unchanged.To change which views are published, click the Views for A360 button in the Manage Models panel of the Collaborate tab. Make the appropriate selections in the resulting dialog and then Sync with Central.
Subsequent publishing operations will make these views available to A360. For more information, refer to the “Select Views to Publish on A360” topic in the Revit 2015 help.

3.    The A360 project page can now distinguish between models that have been published via the Collaboration service and RVT files that have been directly uploaded via the web page. Models that have been published have been changed as follows:o    Special icon badging
o    Dedicated file type identification (“Cloud Revit…,” rather than “Revit Files”)
o    File actions that should not have been possible have been removed from the user interfaceNote that these changes will only manifest for models that have been published using Collaboration 2015.4; those published with previous versions of Collaboration will continue to be indistinguishable from RVT files that were directly uploaded via the project web page.

Known Issues
Issues related to install

1.    Collaboration users who have updated Revit with UR7 but have failed to install the 2015.4 Collaboration update will experience an error on startup, stating Revit “Could not load file or assembly ‘Autodesk.RevitServer.Versioning.Client, Version=…”  To resolve this, be sure to install the Collaboration update after installing the Revit update.
2.    If the Modified date for the revit.exe.config file (located in the Revit program folder, e.g., c:Program FilesAutodeskRevit 2015) is newer than the Created date, the patch installer will fail to update it and Revit may not launch correctly.  It is extremely unlikely that this will occur as the file is not intended to be edited, but if it does please contact Autodesk for guidance on how to repair and properly update the installation.
3.    The A360 icon may appear in the wrong position of the file navigation when Revit and the Collaboration Add On are first installed.  This condition will self-heal.
4.    In rare cases, the ribbon will fail to update after all components are installed. If buttons or groups of buttons seem to be missing and do not match what is expected according to Revit’s help documentation, please reset the ribbon state by deleting %roamingappdata%AutodeskRevit[flavor of Revit 2015]UIState.dat. This is a one-time correction and will not be required thereafter.

Issues related to A360 projects and the A360 web interface
1.    When a project is renamed, it may be necessary to perform a SWC (and, for links, a Reload… from the Manage Links dialog) in order for paths to update and resolve correctly.  Refer to the help documentation for more information.
2.    Project names should NOT include slashes or backslashes, or Revit may behave erratically.
3.    Projects that have been deactivated in A360 may still be visible from certain parts of Revit.
4.    A360’s filter by ‘Me’ function may display items from other users.
5.    Preview images for models that have been published to A360 may fail to update automatically, requiring a manual refresh.
6.    The A360 model viewer may incorrectly report that there are no views found, if only a single view is published.
7.    Notifications of newly published versions of a model may not be displayed in the Activity Stream.
8.    The commenting feature in the A360 model viewer is not supported for 2D sheet views.

Issues related to model or project access
1.    During a network outage it may not be possible to work in a model, even if worksharing operations are avoided. For best results, save the model locally and wait until connectivity is restored.  Note that the save process may take more time than usual, but it will complete successfully.
2.    If a user is added to a project as a contributor, they must click the project link in their invitation email before the project can be accessed through Revit.
3.    If a user is added to a closed project as a member, a project moderator will still need to approve their membership even though they have been explicitly invited to join the project.Issues related to initiating collaboration (saving a model to A360)1.    Initiate collaboration may fail and cause Revit to hang if the model’s current view is a 3D perspective view.  To avoid this condition, be sure to switch to another view before initiating collaboration.
2.    If a user does not have a valid Collaboration entitlement and they attempt to initiate collaboration, Revit will report “You cannot use the option “Collaborate Using A360″ because you do not have access to any A360 projects.”  This is potentially confusing because the message does not indicate the true root cause of the failure (i.e., the lack of an appropriate entitlement.)
3.    If initiate collaboration fails, entries may be created in Revit’s Most Recently Used file list and the zero document screen, even though the model was not actually saved to A360.

Issues related to the Communicator panel
1.    The Communicator panel will lose the context of the current project if the user attempts to save a loaded family to the local disk.  The context will be reacquired when the user switches views or closes and reopens the model.  Similarly, editing a family may cause the panel to falsely claim that the user have been removed from the active project. When the family editor session ends, the status will be refreshed and updated to the correct state.
2.    The Communicator button will still be active even when the panel is open, but it won’t actually do anything.
3.    User profile updates on A360 may fail to reflect in the Communicator panel.
4.    The Communicate panel may fail to sign in if the user signs out from Revit, closes the Communicate panel, and then signs back again.
5.    Sending image content in a chat session may fail, requiring a retry.

Issues related to publishing models or selecting views to be published to A360
1.    Publishing a model that has been renamed will generate a new RVT by that name in A360. When this occurs, the user will see published RVTs with the old name as well as the new name.
2.    Publishing a model to A360 may fail for large RVT files.
3.    Column sort by name does not function correctly in the Views for A360 dialog.
4.    The initial state of the Views for A360 dialog shows no views selected to be published, however, the default behavior (to publish the default 3D view and all sheets) still remains.
5.    Using the Views for A360 dialog may cause an update and redraw of current active view in Revit.
6.    Section views may not be published to A360 unless at least one 3D view is published too.

Issues related to models that have been rolled back or deleted
1.    Revit may incorrectly claim that a user is not a member of a project if they attempt to open a model that was previously deleted.
2.    The vertical scrollbars in the Manage A360 Models dialog may deactivate after a model has been deleted.  To restore them, close the dialog and reopen it.

Also helpful:
How to Get Started with Your A360 Collaboration for Revit Subscription | Revit Products | Autodesk Knowledge Network

Some details on the different project types:
Project types
If you are using the free version of A360, your project is Secret by default, requiring you to invite people by email addresses; the project type cannot be changed. If you are using the paid version, A360 Team, you can choose between three project types, Open, Closed, or Secret; the project type can be changed. You can see the project type on both the project card and on the project Profile page.

Open : A360 Team only. Use for projects where the intent is to share information broadly to everyone. All Open project information is searchable and accessible to all members of the organization. Anyone in the organization can join and leave an Open project at any time. People outside the organization are not allowed to be invited to Open projects.

Closed : A360 Team only. Use for projects that require some privacy. Anyone in the organization can see the Closed project name in search results, as well as the Closed project Profile and People pages. All items in the Closed project shared with the entire hub (Hub All) are also visible. Only members of the Closed project can search for and access the project page, activities, and content. The Closed project’s moderator must approve membership requests. An organization’s hub settings determine if people outside the organization can be invited to join Closed projects.

Secret : Use for personal projects or projects that require extra privacy. Secret projects are hidden from people who weren’t invited to the project. Only existing project members of a Secret project can search for and access the project page, activities, and content. Team Administrators can’t view content inside Secret projects. Membership to a Secret project is by invitation only. If you are using the paid version, A360 Team, the hub settings determine if people outside the organization can be invited to join Secret projects.

From http://help.autodesk.com/view/ADSK360/ENU/?guid=GUID-C6DC09BF-1680-4EE6-853A-563AC4B5E953