Autodesk® A360 Collaboration v6 for Revit®  2015

Autodesk® A360 Collaboration v1 for Revit®  2016

 

 

Install and Known Issues

 

The capabilities and behavior of Autodesk A360 Collaboration v6 for Revit 2015 and v1 for 2016 are identical; they only differ in the versions of Revit that they target.  They share the same readme documentation.

 

 

Introduction: Autodesk A360 Collaboration v6 for Revit 2015

 

Autodesk A360 Collaboration v6 for Revit 2015 can be applied to Autodesk Revit 2015 as a new installation, or as an update to Autodesk A360 Collaboration for Revit 2015 v1, v2, v3, v4 and v5.

Before installing Collaboration v6 for Revit 2015 you will need to update Autodesk Revit 2015 with Update Release 9.  This release of Collaboration features an enhanced installer that can automatically download and apply UR9 for you.  If the installer has enabled the option to apply UR9 please do not disable it.

As a reminder, updates are specific to the variant of Revit that you have installed, 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 download the update that is appropriate for your installed version of Autodesk Revit. 

 

Introduction: Autodesk A360 Collaboration v1 for Revit 2016

 

Autodesk A360 Collaboration v1 for Revit 2016 can be applied to Autodesk Revit 2016 as a new installation, or as an update to Autodesk A360 Collaboration for Revit 2016.

Before installing Collaboration v1 for Revit 2016 you will need to update Autodesk Revit 2016 with Service Pack 2.  The Collaboration installer will attempt to download and install SP2 if it is not already present, unless the option to do so is explicitly disabled.  Please do not explicitly disable the option to install SP2.

 

What’s new in this release?

1.      Parallelized uploads to substantially improve performance for SWC.

2.      Improvements in the reliability of publishing operations.

3.      Enhancements to the Communicator panel that will allow it to remain functional and usable even when Revit is busy (e.g., when a SWC is in-flight.)

4.      It is now possible to delete a “Cloud Revit” RVT file from the A360 project web page.

5.      The installer has been enhanced to improve the reliability and integrity of component downloads.

6.      Assorted defect fixes have been made.

 

 

 

 

Installation Guidelines

 

Important!

Users who attempt to use Collaboration v6 for Revit 2015 without applying Revit 2015 UR9 may receive an error when starting Revit and may find that Collaboration does not function correctly.  Do not attempt to install Collaboration v6 for Revit 2015 without also installing Revit 2015 UR9.

Users who attempt to use Collaboration v1 for Revit 2016 without applying Revit 2016 SP2 may receive an error when starting Revit and may find that Collaboration does not function correctly.  Do not attempt to install Collaboration v1 for Revit 2016 without also installing Revit 2016 SP2.

1.      Close all instances of Autodesk Revit 2015 and 2016.

 

 

2.      Launch the installer. 

 

 

3.      Please wait approximately 30 seconds while the installer analyzes your system to determine which Revit installations are present and what updates need to be applied.

 

For Collaboration v6 for 2015: you must have Revit 2015 UR9 installed.  If UR9 is not already present, the installer will calculate which updates need to be applied in order to successfully upgrade your Revit installation to UR9.  If the installer displays the option to install UR9 after analyzing your system, do NOT disable it. 

 

For Collaboration v1 for 2016: you must have Revit 2016 SP2 installed.  If SP2 is not already present, the installer will calculate which updates need to be applied in order to successfully upgrade your Revit installation to SP2.  If the installer displays the option to install SP2 after analyzing your system, do NOT disable it. 

 

4.      Confirm that the checkbox for Collaboration is enabled.  Enable or disable the option to install Dynamo for Autodesk Revit, based on your preference.  Click the Install button and allow the installation to complete.  You may see several pop-up windows as various components are downloaded and installed.  (Note that if you have elected to install Dynamo, an install wizard for IronPython will appear.  This is expected and as designed) 

 

5.      When the installer completes, you will see a splash screen confirming that Autodesk A360 Collaboration for Revit and Autodesk Personal Accelerator for Revit have been successfully installed.  Click the exit button to dismiss the installer. 

 

6.      At this point, your Autodesk Revit has been updated and is ready for use. 

 

Note that you will need the appropriate entitlements to access the new functionality.  (Please refer to the About A360 Entitlements section of the Autodesk Revit 2015 or Autodesk Revit 2016 help for more information.)

 


 

Known Issues

 

Issues related to install

 

1.      If the Modified date for the revit.exe.config file 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.

2.      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. 

3.      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%\Autodesk\Revit\[flavor of Revit 2015 or 2016]\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.

9.      Extremely large 3D views may fail to display correctly in the A360 model viewer.

10.    A future update of A360 will introduce the ability to move a project from one Team hub to another, however this capability will not be supported for Team hubs that are used with Collaboration.  As such, if a project is moved to a Team hub used with Collaboration, it must stay there and it will not be possible to move the project to yet another hub.

 

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.      The A360 projects page does not block a user from moving a Cloud Revit model from one project to another.  At this time Revit's behavior is undefined when this occurs.  For best results, only move a model between folders in its original host project.

 

 

 

Issues related to initiating collaboration (saving a model to A360)

 

1.      For Revit 2016, initiate collaboration may appear to hang at the first stage (where worksets are created) if the model is in a 3D perspective view.  If this occurs, use Control-F4 to escape out of the progress dialog, switch to a 2D view, and try again.

2.      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.      User profile updates on A360 may fail to reflect in the Communicator panel.

3.      User profile updates on A360 may fail to update in the Communicate panel.

4.      If network connectivity is interrupted while a file is being downloaded from a chat session, the download will fail and subsequent retried attempts may also not succeed. 

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 or complex 3D views.

3.      Using the Views for A360 dialog may cause an update and redraw of current active view in Revit.

4.      If you attempt to move a model published prior to the launch of Collaboration v6 for Revit 2015 and Collaboration v1 for Revit 2016, the next publish operation will create a new copy of the Cloud Revit model in the root folder of the A360 project page.  For best results, do not attempt to move the model until you have first published a new version; subsequent publish operations will then successfully track and update the model in its new location.

5.      Publishing may fail if there are multiple copies of the Cloud Revit model on the A360 projects page.  (Typically, this condition arises when a Cloud Revit model has been moved from the root folder into a subfolder on the projects page; in previous versions of Collaboration, subsequent publish operations would result in the creation of another copy of the Cloud Revit model beneath the root folder.)  To resolve this condition, delete every copy except the one in the root folder and then attempt to publish from Revit.  After the publishing operation completes, you may then move the Cloud Revit file to a subfolder and subsequent publish operations will update it in its new location.

6.      For certain printer driver configurations, invoking the Manage A360 Views dialog may result in a warning message about current print settings.  Please dismiss and ignore this dialog; the Manage A360 Views functionality will be unaffected. 

 

Issues related to models that have been rolled back or deleted

 

1.      If a model is renamed and then subsequently restored, the user must open the model by browsing A360 through Revit's file open dialog.

 

Autodesk and Revit are registered trademarks or trademarks of Autodesk, Inc., and/or its

subsidiaries and/or affiliates,, in the USA and/or other countries. All other brand names,

product names, or trademarks belong to their respective holders. Autodesk reserves the

right to alter product offerings and specifications at any time without notice, and is

not responsible for typographical or graphical errors that may appear in this document.

Occasionally, Autodesk makes statements regarding planned or future development efforts for

our existing or new products and services. These statements are not intended to be a promise

or guarantee of future delivery of products, services, or features but merely reflect our current

plans, which may change. The Company assumes no obligation to update these forward looking

statements to reflect any change in circumstances, after the statements are made.

© 2015 Autodesk, Inc. All rights reserved.