OTOY Forums

Greeting Paul and Revit Octane Users,
Octane is a beautiful engine BUT
Could you please tell me why Octane material does not work "out of the box" ?

I have this Revit 2019 project for everyone to play with - the material has been set up using Revit's material editor.
It is a requirement that all materials have to start by setting up through Revit's material editor, because we can then output textured elevations drawing, hatch etc.
You can download it here: https://drive.google.com/drive/folders/ ... sp=sharing When you first open the file you will end up with missing textures everywhere. You do not need to re-path the textures manually, all you need to do is tell Revit where those textures are located, by going to Options --> Rendering --> Add links. I have included all textures for you to test as well. The catch is Revit cannot read Sub-folders so all textures have to be sitting inside 1 folder. Once you have added the path all materials in the folder will be re-pathed automatically. Now, since I also use Enscape. All I need to do is go to a 3D view (3D Ortho view is also okay!) and press "Start Enscape" - that's what we will see out of the box with no settings required: As for Octane - I have to start from 3D Perspective view...that's okay.
I then tried to Re-convert all materials to Octane material. Finally I hit Open Viewport, and that's what I get: Then the viewport opened, and I get 1 more error: and that's what I see: Could you please tell me what has gone wrong?
Paul, could you also make the plugin work using Revit's material editor similar to Enscape's 1 click solution???

Thanks.

Paul I would appreciate if there are some temporary workaround.
Looking from the error message it seems like a absolute/relative texture path issue.
But surely I dont want to go into the material editor to manually re-link the trxture

Hi

When you add the textures path to the Options/Rendering/Additional paths, Revit is still reporting that the texture map is missing in it's own Materials window, so this function appears to be bugged. Inside the SDK, you can see if you add your path to the Options/Rendering/Additional paths, it only provides the relative filename, not the full path: Whereas if you manually fix the broken link, the SDK provides the full path name: So this looks like a Revit SDK problem to me. I have requested from Autodesk how to retrieve the list of paths added to the Options/Rendering/Additional paths window, which might provide a way for the plugin to get the full path name. However at the moment, you would need to manually relink all the textures in the Revit Materials window.

Paul

The answer is to look in the "additional appearance render paths" and see if the material image is there. I don't see what the problem is since you have access to both pieces of information and you can put them together.