OTOY Forums

Hello Paul,

I just discovered a very nasty material bug... do the following:

1. in a fresh rhino session create any object, copy it 3 times
2. select all 4 objects, assign a material by object, create a simple green rhino material
3. open the material editor - you see the material you just created...
4. open the octane render settings dialogue, right click - convert the materials to octane materials.
5. look at the material editor again. Although there should be only one material there are now 4 identical materials (one for each copy...)

switched back to 2.10.0.16 -> bug still there
switched back to 2.6.0.15 -> bug is gone...

So for now I have to switch back to the official version since it is crucial for me to be able to convert materials which are object based.

I will try to find an older copy of 2.10.0.15 to see if the bug is also there... Is there any place to download the old wip versions?

best regards

Andreas

Hi Andreas and Paul,

I can confirm the above is happening, followed Andreas's steps and got 4 identical materials after converting to Octane materials.

Ryan

5. look at the material editor again. Although there should be only one material there are now 4 identical materials (one for each copy...)

Fixed in the next release.

Paul

It seems that curves might be filling up GPU ram even when curve piping is not enabled - ie. I am currently rendering a scene on my 1GB cards, and with no curves the total is ~200mb, but with 4000 curves visible (with no piping) it tops out the card and won't render.

Hi Cam - Are you able to send me a sample scene demonstrating this?

And also a reminder to send me that Bongo scene which was not rendering.

Paul

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

2.11.1.18
- Compiled against Octane 2.11.1
- Added Highlight Compression to the Imager settings (see Standalone release notes for details)
- Changes to render passes as per Octane Standalone
- Added additional Color Correction node pins (see Standalone release notes for details)
- Added new Noise texture node (see Standalone release notes for details)
- Added additional kernel pin Static Noise (see Standalone release notes for details)
- Stopped the "Texture" node being transferred when changing the Environment node from Texture Environment to Daylight (and vise-versa)
- Rendering of Rhino Parallel Projection camera is now scales correctly for all Rhino scene units
- Added "Import Material from Local Db" button on the Octane material panel which is the same is importing an ORBX, however the Load File dialog is shortcut to the Octane Local Db folder
- Add "Export" button on the Octane material panel to export the current material to the Octane Local Db

Paul

Paul, you are the best!

thanks

Andreas

face_off wrote:

when switching from the material editor panel to the octane panel I often have a freeze of octane /rhino which forces me to brute force end the program...

Andreas - is it possible Rhino/Octane is generating the preview when you change tabs, resulting in the freeze?

Hello Paul, I just got another "freeze" and I think you are right, it seems it has happened while I changed the tabs while the preview was still working...

however I did not get a crash report, I am not sure 100%, but I think this is due to the fact that it freezes and does not crash...

edit:
I was just able to repeat it, I will try to do a small scene for testing

edit2:
I can provoke freezing on a fresh scene:

1. create any object
2. apply a glossy material to the object
3. open material editor (I have the octane render settings and the material editor as tabs side by side)
4. increase the roughness multiplier to a value of 1 and while the preview is still working tab on the octane render settings panel. -> Freeze!

here is the "detail" (in german i´m afraid...)section of the dialogue box "Rhin0 5.0 is not responding" , i don't know if this is of any help :

Aufgrund eines Problems kann dieses Programm nicht mehr mit Windows kommunizieren.

Problemsignatur:
Problemereignisname: AppHangB1
Anwendungsname: Rhino.exe
Anwendungsversion: 5.10.41015.17045
Anwendungszeitstempel: 543f162d
Absturzsignatur: 9e25
Absturztyp: 524288
Betriebsystemversion: 6.1.7601.2.1.0.256.48
Gebietsschema-ID: 1031
Zusätzliche Absturzsignatur 1: 9e258df21fcc0c08cfea2105e6951ff9
Zusätzliche Absturzsignatur 2: 3f1f
Zusätzliche Absturzsignatur 3: 3f1f21e54d739595db157695f49e9993
Zusätzliche Absturzsignatur 4: 9e25
Zusätzliche Absturzsignatur 5: 9e258df21fcc0c08cfea2105e6951ff9
Zusätzliche Absturzsignatur 6: 3f1f
Zusätzliche Absturzsignatur 7: 3f1f21e54d739595db157695f49e9993



best

Andreas

I can provoke freezing on a fresh scene:

Andreas - can you do this with ProcDump running as per my PM to you a week or two ago?

Thanks

Paul

done...

face_off wrote:

I can provoke freezing on a fresh scene:

Andreas - can you do this with ProcDump running as per my PM to you a week or two ago?

Thanks

Paul

Regarding the feature request to set the Rhino render preview window material transparency to 50% if there is "something" plugged into the Octane material opacity - it does not appear to be possible for an Octane Material to set Rhino preview window material to a 50% transparency due potentially to a bug in Rhino. I have escalated this to McNeel.

Paul