Collaborating in the Autodesk Cloud with Plant 3D and Revit

[@Hagerman_brettbarkman]

UPDATE: After sharing a project from Plant 3D, it is possible to move the top-level folder in Docs. For example, if you want a discipline folder like the one for your Revit models, you can create it (e.g. 'Plant'), then move the main folder for the Plant 3D project into it. Next time you open that project in Plant 3D, it will load as expected. This will help with overall folder organization in Docs.

[@lukecoxon4570]

It's 2022 and Autodesk still can't work out syncing between disciplines of their own software. We still need to export a 3d solids "dumb" copy, which is stripped of its data, for every Plant 3d file. Likewise from Revit to Plant 3d. If a team is updating models several times a day and need to collaborate the deigns in real time, this workaround of dumb exports is extremely counter productive. At the very least Autodesk should include some automation capability so that the "dumb" P3D & Revit exports are automatically generated upon Check in and synced to a shared folder that Revit & P3D users are already mapping to in their software. Note that this additional folder would be yet another copy on top of the "Shared" or "Collaboration" copies. That's 3+ sets of the same files with each copy needing resubmission to the correct location. Should be one set. Two sets is annoying but manageable. 3+ sets only leads to wasted time & collaboration errors. Also, what do we do for required changes that are not clashes now that ACC has removed the ability to do markups in the 3d model interface? We still can't create an issue with a simple sketch markup in it to provide a visual of the required change. It's clear that these processes are not considering actual designers and their workflows. Rather ironic for a design software company that sells construction design software solutions.