OctaneRender for Rhino 3.03.2 [OBSOLETE]

[face_off]

the scale looks good to me, it is just that the position of the texture doesn't match

Thanks for the screenshot. The Octane Material texturemap scale will not be applied to the Rhino preview window - however the easy way to resolve this is to NOT applying a scale to the Octane material Diffuse->UV Transformation->Scale, and instead scale the projection in Rhino (ie. the XYZ Size can be changed from 6 in order to scale the texturemap (by scaling the UV coords). You will need to Refresh the Octane Viewport after changing the UV mapping of any Rhino Geometry.

Paul

[formatio]

Hi Paul

I found another issue with material thumbnails - they are not displaying properly (it looks to me like thumbnails show rhino material instead of octane), and get always updating (or sometimes not - hard to say when - usually when I scroll material window, then it gets stuck for a while to refresh materials, even if I turn of auto update all thumbnails).

Some screenshots in attachment.

Regards,
Mac

[formatio]

Oh, One more thing - another issue - in previous version, after editing values of material, for example roughness, the edited property changed as soon as the value was typed into input box. Now it needs to be clicked away (hitting enter doesn't work) in some blank white area.
That's with materials.

With octane render settings, for example changing max amount of samples - only enter confirms input, clicking away doesn't work in this case.
And every enter hit gives me windows jingle sound - weird

The previous behavior (applying value on the fly, while typing) was much better imo, and we got used to it

Regards,
Mac

[face_off]

I found another issue with material thumbnails - they are not displaying properly (it looks to me like thumbnails show rhino material instead of octane)

You are right. I am talking to McNeel on this issue.

Paul

[face_off]

Oh, One more thing - another issue - in previous version, after editing values of material, for example roughness, the edited property changed as soon as the value was typed into input box. Now it needs to be clicked away (hitting enter doesn't work) in some blank white area.
That's with materials.

With octane render settings, for example changing max amount of samples - only enter confirms input, clicking away doesn't work in this case.
And every enter hit gives me windows jingle sound - weird

The previous behavior (applying value on the fly, while typing) was much better imo, and we got used to it

Yes, I just noticed this too. I'm not aware of anything in the plugin which changed. I am wondering if Rhino SR10 has triggered the change. I will investigate.

EDIT: This was introduced in plugin version 2.13.0.19. I will fix this in the next release.

EDIT2: Seeking feedback on this....the reason for the change was that currently you can have a displacement of 0.001 and if you select the '.0001' and accidently hit '1', a displacement amount of 1 will immediately be sent to Octane and crash Rhino. So forcing the hitting of Enter/Tab was put in place to prevent this. My preference would be to fix the enter/tab detecting and make it work correctly rather than have potential crashes. You thoughts pls?

Paul

[face_off]

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

2.14.0.22
- Fixed issue where importing Specular materials from the LocalDb was not working
- Fixed bug where editing an Octane Material that was NOT used in the scene whilst the Viewport was open would crash Rhino
- Enter or Tab or change focus is required to send new values to Octane (ie. type a new Aperture value in te Aperture box, then press Enter or Tab to update Octane to that Aperture value). This has been done to ensure invalid values are not accidently set for the Displacement amount which can crash Rhino.

NOTE: Material Preview is currently not working correctly. This issue has been reported to McNeel.

Also, McNeel have reported that the lockup when clicking the OctaneRender tab from the Material tab is scheduled for fix in Rhino SR11.

Paul

[formatio]

Hi Paul
I tested newest release.

Only way to send value to octane is by changing focus ("enter" not working in materials tab, but it works in render settings tab and "tab" works here too).
Using "enter" is much more convenient that "tab", after hitting "tab" I need to use mouse to click on the input field to change value again.

By the way I noticed that value sliders got much choppier recently - even in very light scenes, like single sphere only and sun.
As a matter of fact - sliders are choppy even if I change value of material that is not rendered (is not applied to any of the objects that are being currently renderd) - maybe they are updating their thumbnail and that's what slows them down ? - I often turn off auto update of thumbnails to speed up things.

EDIT: It changed - I was testing it again and now the sliders work smooth, even with material currently assigned and rendered - no idea whats going on. I'll report it further.

Yes, I just noticed this too. I'm not aware of anything in the plugin which changed. I am wondering if Rhino SR10 has triggered the change. I will investigate.

I used sr10 with earlier releases and it was ok.

[face_off]

Only way to send value to octane is by changing focus ("enter" not working in materials tab, but it works in render settings tab and "tab" works here too).
Using "enter" is much more convenient that "tab", after hitting "tab" I need to use mouse to click on the input field to change value again.

You are right - it looks like the Material panel is not sending the Tab and Enter events. I will resolve this.

Slider slowness : Once I get more info on the Preview generation issue I will get a better idea on what is causing this.

Paul

[face_off]

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

2.14.0.23
- Removed the change from 2.14.0.22 that meant users needed to press enter or tab to send new values to Octane (since the Rhino Material tab does not appear to support this correctly).

Paul

[face_off]

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

2.16.0.24
- Compiled with Octane 2.16
- Various additions/enhancements to emitters, including addition of "Surface Brightness" and "Cast Illumination" pin. See Octane 2.15 Standalone release notes for details.
- Removed ISO and FStop Imager pins. See Octane 2.15 Standalone release notes for details. Scenes saved with plugin versions prior to 2.16.0.24 will have the exposure converted to the new scale, however your default rendertarget "exposure" will not be converted - so you may need to adjust the default exposure and then "Save a Default"
- Daylight illumination power has been re-calibrated (pls see Octane Standalone 2.16 release notes for details). You may need to tweak the Daylight power of some pre-2.16 scenes to compensate.

- KNOWN ISSUE: If both the Material and Octane tabs are docked to the same panel, changing from the Material tab to the Octane tab after editing an Octane material pin value may lock up Rhino. This will be rectified in the next release of Rhino.
- KNOWN ISSUE: Octane Material thunbnails are based on the Rhino preview version of the material, and not the actual Octane material. This will be rectified in the next release of Rhino.

Paul