OTOY Forums

There is a problem with the 2.6.0.10 installers, so I have rolled back to the previous version in the links at the top of this thread. There should be new test release available in the next week which includes all the changes from 2.6.0.10, but in the meantime use the versions at the top of this thread.

Thanks

Paul

I have posted a build of the plugin for Octane 2.10 at http://render.otoy.com/forum/viewtopic.php?f=61&t=42589.

Paul

Hi Paul,

The 3D imported objects (DWG, etc) cannot get any material assignments. Is there any workaround for this, other than use proxies?
The families render correctly inside Revit, and the respective materials are into the Octane mat list.


Thank you.

The 3D imported objects (DWG, etc) cannot get any material assignments. Is there any workaround for this, other than use proxies?
The families render correctly inside Revit, and the respective materials are into the Octane mat list.

Are you able to send me a DWG where this occurs pls? Then I will take closer look.

Paul

The 3D imported objects (DWG, etc) cannot get any material assignments. Is there any workaround for this, other than use proxies?
The families render correctly inside Revit, and the respective materials are into the Octane mat list.

Thanks for emailing me the additional info. The immediate workaround is to select the materials from the Scene Materials combo box (rather than Selection Materials). Also, you can open the Viewport and material pick the materials. I am also working on a fix which should see the materials added to the Selection Materials combo box, which will hopefully be in the next release.

Paul

Hello Paul,

As I said before, the materials are there, on the plugin materials list, but the objects are rendered all black or even disappear at all, no matter what is on the material profile. Could the Revit 2013 version be the culprit?

As I said before, the materials are there, on the plugin materials list, but the objects are rendered all black or even disappear at all, no matter what is on the material profile. Could the Revit 2013 version be the culprit?

Ah - yes - they will potentially not be picked up in Revit 2013. From Revit 2014 there is a new geometry loader in the Revit API which provides access to these materials. I doubt there is a solution for Revit 2013 - sorry.

Paul

Inside Revit, using both MR or RT, the textures render okay - this is a huge con (the API issue) everyone must consider when using Octane with Revit 2013.

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

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.