OctaneRender for Rhino 1.32 [OBSOLETE] (RhinoSR7 31213)

[justix]

Paul, is the Export to OCS actually work as it should? I mean, I did try to export it to OCS but this is as far as I go, other exporter does open the scene by itself while on this installer it does not, BUT is not the issue, more like that It does not seems to render the scene at all, only materials and nodes seems disconnected? clicking on the render target does nothing...

edit: upgrade to Octane 1.27 works BUT camera coords seems lost AND navigating to recover camera position make octane hang...

Until things settle down with Octane Standalone - I think you will need to open the exported OCS file in the same version of Octane Standalone as the Rhino plugin. So export from the 1.25 version of the Rhino plugin and import into Octane Standalone 1.25. This /should/ work. If it does not, pls let me know the details.

Paul

Thanks Paul. sadly it does not work, installed 1.25.05 plugin and Stand Alone 1.25 but is a no joy ride. I will wait for a new version.

Thank You

[face_off]

Thanks Paul. sadly it does not work, installed 1.25.05 plugin and Stand Alone 1.25 but is a no joy ride. I will wait for a new version.

You need to have the Viewport open when you export in Rhino. The export menu command should not be available unless you have the Viewport open - but this is not working right - and I will rectify this in the next version.

Paul

[face_off]

I have refreshed the installer at the top of this thread with:

1.25.0.6
- Disabled exporting of the scene to OCS if the Viewport is not open
- Fixed issue where nodes could not be disconnected. You can now disconnect some nodes, including "bump", "normal", "filmwidth", "filmindex", and "medium" pins
- Focus and Material pick now works correctly when the Viewport has been zoomed

Paul

[v-cube]

Hello Paul,

thank you very much for the new build!

While testing I found a few issues of varying importance:

1. Sun orientation
I find the current way to orient the sun position not very user friendly, I would prefer to have only two variables to manualy position the sun: a) vertikal angle between 90 deg (zenital) and 0 deg (dawn) b) horizontal position between 0 deg (north) and 359 deg. Northofset should also be a number between 0 and 359, representing the offset angle from 0 deg (north)
Another thing... am I wrong or do I remember a nice daylight editor with the possibility to enter location, date and time to alter the sun position accordingly, which was already implemented in one of the former versions?


2. Material conversion from vray materials
I still experience some oddities e.g. a former vray glass material gets converted to a specular material with a color value of 0/0/255 in the reflection slot...
materials with glossy layers are initialy converted th octane glossy materials with a specular value of 1, independent of the former intensity
Another thing which is especially time consuming to correct is that I sometimes end up with 2 or 3 duplicate (same named) materials.. could this maybe be connected to materials which are in some cases applied on an object level, in other on a layer level or in blocks? Could there maybe be an option to remove orphanage materials and/or duplicate materials?

3. HDRI orientation
yesterday I tried to light a scene with an HDR image which was casting clearly visible shadows in its initial position. However when trying to rotate the image by changing projection from the default UV to spherical, then opening the 3d transformations of the spherical projection and modify the y value, the background in the octane viewport is indeed changing but the light is altered in a strange way... I tried to illustrate the phenomenon with the help of the tree attached pictures:

the first picture shows the situation with the original orientation of the hdri file with high contrast shodows

the second and third show the same scene with only the y value of the hdri rotation altered by 90 / 180 degrees. While one can see the orientation of the main light source is rotating, the light balance is completely different, darker and much more diffuse. I would expect that the initial sharp shadow just travels around the sphere...

4.crashes

in the last days I had 3 blue screens while using octane4rhino... Since I cannot remember this happening before I guess it might be related to one of the new builds...
please see attached picture:

any feedback is really appreciated

thank you for your effort!

Andreas

[Tipperz]

We also suffered blue screen crash situations on 2 separate systems with a file that appears to have some error saved in it. To solve this issue we copied the needed geometry to a clean instance of Rhino and this solved the problem. I can't tell you why but maybe this helps?

[face_off]

Thanks for the feedback.

1. Sun orientation
I find the current way to orient the sun position not very user friendly, I would prefer to have only two variables to manualy position the sun: a) vertikal angle between 90 deg (zenital) and 0 deg (dawn) b) horizontal position between 0 deg (north) and 359 deg. Northofset should also be a number between 0 and 359, representing the offset angle from 0 deg (north)
Another thing... am I wrong or do I remember a nice daylight editor with the possibility to enter location, date and time to alter the sun position accordingly, which was already implemented in one of the former versions?

Turn the Rhino sun ON, then the Octane will pickup the sun direction from there.

2. Material conversion from vray materials
I still experience some oddities e.g. a former vray glass material gets converted to a specular material with a color value of 0/0/255 in the reflection slot...
materials with glossy layers are initialy converted th octane glossy materials with a specular value of 1, independent of the former intensity
Another thing which is especially time consuming to correct is that I sometimes end up with 2 or 3 duplicate (same named) materials.. could this maybe be connected to materials which are in some cases applied on an object level, in other on a layer level or in blocks? Could there maybe be an option to remove orphanage materials and/or duplicate materials?

Vray materials get first converted to a Rhino "Basic" material, then from there to an Octane material. It may be the Vray to Rhino step at fault, or the Rhino to Octane step. Would it be possible to send me a RMTL file from a Vray material which is causing these issues pls, and I will investigate.

Regarding the duplicate materials - I thought I had resolved this previously, however it looks like there are some creeping in. If you can identify exactly where the duplicates are coming from, I'll fix. Are these duplicates a result of using the "Convert all materials to Octane materials"?

3. HDRI orientation
yesterday I tried to light a scene with an HDR image which was casting clearly visible shadows in its initial position. However when trying to rotate the image by changing projection from the default UV to spherical, then opening the 3d transformations of the spherical projection and modify the y value, the background in the octane viewport is indeed changing but the light is altered in a strange way... I tried to illustrate the phenomenon with the help of the tree attached pictures:

Can you try exporting the unrotated scene to Octane Standalone 1.25, then add the spherical projection and try rotating. Is it happening there? Also, try unclicking then clicking the Importance Sampling checkbox. A few people have reporting HDRI issue with 1.25, so the next release may fix this.

4.crashes

in the last days I had 3 blue screens while using octane4rhino... Since I cannot remember this happening before I guess it might be related to one of the new builds...
please see attached picture:

There is something in the scene which is tripping up Octane when the plugin sets the rendertarget. I've had a handful of cases with the other plugins with this - and the latest Octane API potentially fixes this. If you have a simple scene which causes a blue screen, pls send it to me so I can confirm this.

We also suffered blue screen crash situations on 2 separate systems with a file that appears to have some error saved in it. To solve this issue we copied the needed geometry to a clean instance of Rhino and this solved the problem. I can't tell you why but maybe this helps?

Good fix. Again, if it is possible to send me one of the scenes which crashes Rhino, that would help immensely.

Paul

[Tipperz]

Hi Paul,

what email do I send a Box link to? It's a big file!

[face_off]

what email do I send a Box link to? It's a big file!

paul at physicalc-software dot com.

Thanks

Paul

[v-cube]

Hello Paul,

thanks for the hint concerning the rhino sunlight system, this work like a charm...

I took another look at the duplicate material issue and it seems that during the automatic, right click triggered material conversion process, octane creates a separate material for each layer, regardless that these share just one single material ( please see attached pics...)
This behaviour is the same for both vray or native rhino materials.

best

Andreas

[v-cube]

Hello Paul,

I took another look at the glas Problem,
like you suspected both the rhino material and the vray material are showing the same effect... the rhino material was a basic material with 88% reflectivity and 92% transparency....

best

Andreas