OTOY Forums

Still about the second example of the previous post, I found this:
This is how an elevated (above ground by offset) building pad looks like in Revit
and this is how the same scene looks rendered. The way this algorithm works could be related to the issue with the displacement rendering.

The only subdivision config I found (v2.06) is under the "preferences > geometry import"

You need to use 2.16 - since there have been displacement mapping fixes applied after 2.06.

Paul

face_off wrote:

The only subdivision config I found (v2.06) is under the "preferences > geometry import"

You need to use 2.16 - since there have been displacement mapping fixes applied after 2.06.

Paul

Thank you Paul,

Now that's beautiful - I got perfect results with 2.16 on my specific scene (another one) with 0.02 height of the grass. Just waiting for this to happen inside the Revit plugin.

Merry Christmas to you and all the team.
Regards.

I have updated the STABLE version links at the top of this thread to the latest TEST version (2.16.0.23).

Paul

Hi Paul,
Have been testing out the save to defaults orbx feature quite a lot and it seems to be working great. The only bug I have found so far is when making a change to an already saved to default orbx material, and re-saving to default. A error occurs and the original orbx file seems to loose its embedded textures, as the file size reduces to about 15KB.
Other than that so far it is working great

Many Thanks.

Have been testing out the save to defaults orbx feature quite a lot and it seems to be working great. The only bug I have found so far is when making a change to an already saved to default orbx material, and re-saving to default. A error occurs and the original orbx file seems to loose its embedded textures, as the file size reduces to about 15KB.
Other than that so far it is working great

I can reproduce this issue - so will try to find a solution. The workaround for the moment is to "Save as Default" with the Viewport CLOSED.

EDIT: Closing the Viewport still does not result in the ORBX being updated. At this stage you cannot update the default if there is already a default. I will need to investigate this in more detail....

Paul

Have been testing out the save to defaults orbx feature quite a lot and it seems to be working great. The only bug I have found so far is when making a change to an already saved to default orbx material, and re-saving to default. A error occurs and the original orbx file seems to loose its embedded textures, as the file size reduces to about 15KB.
Other than that so far it is working great

I have been talking to Otoy about using the ORBX format for storing "Default" materials - and there are some complexities with this strategy which are of concern. For example, if you have a default ORBX material containing a texturemap, if you copy the rvt file to another PC - you will need to also copy the default ORBX files (since the texturemaps used in the .rvt reference texturemaps inside the ORBX files). I think this is going to be confusing to users - particularly where you have saved a "Default" which contains a texturemap from the Revit materials library - which would exist on other PC's with Revit installed. Plus, once you have saved a default for a material, there is no way to edit and resave that ORBX (for technical reasons that I won't bore you with). The above issues exist with the LocalDb too on Octane Standalone (ie. once you have saved a material to the LocalDb, you cannot update it and re-save to the same LocalDb name).

So I think the best solution is to change the "default" material save format from ORBX to OCS. With OCS files the texturemaps are on your filesystem, so you can manage where they are stored and ensure they are copied onto other PC's when the .rvt is copied. Plus the OCS format is "future-proof" for any changes make to the Octane node structure and when loaded Octane will automatically convert the nodes form the Octane version they were saved in to the current Octane version of the plugin.

Happy to explain/discuss if people have questions...

Paul

face_off wrote:So I think the best solution is to change the "default" material save format from ORBX to OCS. With OCS files the texturemaps are on your filesystem, so you can manage where they are stored and ensure they are copied onto other PC's when the .rvt is copied. Plus the OCS format is "future-proof" for any changes make to the Octane node structure and when loaded Octane will automatically convert the nodes form the Octane version they were saved in to the current Octane version of the plugin.

Happy to explain/discuss if people have questions...

So once everyone has a chance to review & comment (presuming it doesn't present any unseen issues) the default system in the Stable & Test version will be switched to OCS?

So once everyone has a chance to review & comment (presuming it doesn't present any unseen issues) the default system in the Stable & Test version will be switched to OCS?

Yes - I will release a new TEST version today, and if no issues are found in a weeks or so, STABLE will be updated too. Then I'll release a 2.20 build into the TEST thread.

Paul

Hello Paul,

I'm getting some artifacts from Revit, take a look at these rendered extrusions:
They are just ellipses or circle based extrusions, either Revit components or masses. When I render using raytrace view mode or using the Mental Ray, those faceted extrusions become perfectly smooth. Is this an error from Revit or the API, or something else with the plugin?

Thank you.