face_off wrote:this is a huge con (the API issue) everyone must consider when using Octane with Revit 2013.
Autodesk thankfully resolved this issue 2 releases ago - so it is up to users to upgrade to a current release of Revit if they need this resolved.
Paul
The Firm I work with just made the transition to 2015 BDSU (30+ seats) - a significant investment - but so many workflow advantages for us:
-Faster viewport performance
-Pictures within schedules (previously we exported smart data to a dumb spreadsheet to combine with other product info which we couldn't integrate with Revit as easily)
-Reveal constraints and more 'safeguarding' options (some from 2014)
-Better IFC import for our VisualARQ based designers.
-Site Designer (anyone who used split regions to model acceptable 3D sites in Revit will understand the need for this)
-Finally some editing in 3D perspective
-Sketchy line (clients love it, and the alternatively workflows were not accessible to all technical staff)
-Material manager improvements (mainly from 2014)
Not to mention the API improvements, which prompted this discussion.
None of the above was worth upgrading for on its own, but combined, along with some of our main consultants upgrading to 2014/2015 it became the less of two evils to upgrade.