OctaneRender for Rhino 1.50 [OBSOLETE]

[Ndawg]

Hi Paul,

I updated to the Rhino plugin 1.5 and loaded and older scene (from 1.20.1), but have lost my HDRI map texture rotation coordinates.

I then re-installed 1.20.1 to try & retrieve the coordinates, but the Octane plugin was not recognized.

Any thoughts how to retrieve the HDRI rotation coordinates (or re-install an old version)?

Thank you,
Nathan

[face_off]

Hi Hathan - if rolling back to an old version - uninstall the current version though the Window Control Panel first.

Paul

[eric_clough]

Hi Paul ..

I just installed a GeForce GT 640 (4GB) to my system and this seems to have allowed me to specify 'high' priority to my render speed which appears to have increased the render speed by about 30% ... as long as the Rhino window is in wireframe all operations are quite smooth.

This is simply an update. The Octane plug-in for Rhino is absolutely great. Thanks

eric

[face_off]

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

1.50.0.17
- Fixed issue where texturemaps were not appearing in the Rhino preview window for Octane materials if Shadows or Use Advanced GPU Lighting were turned OFF
- Fixed issue where pasting an RGB Color was not updating the material preview image
- Fixed issue where video cards with long nams could not be deactivated in the Devices tab

1.50.0.16
- Increased the height of the material tree in the Material panel by 20%. Can go bigger if needed.
- Implemented automatic sun positioning when rendering Sun Studies. To do this, turn the Rhino Sun OFF, then the Rhino render will provide the Octane sun position from the Sun Study sun direction
- Added support for Worksessions. Attached scenes will need their Octane materials already defined (ie. you cannot edit the Octane material of an attached scene object in the worksession).

Paul

[polywog7]

Hey Paul,

Looks good. The activate check box for my long named card is still covered though, is there any way to spread that out?

Thanks!

[face_off]

The activate check box for my long named card is still covered though, is there any way to spread that out?

I definitely fixed this - but perhaps it missed the 1.50.0.17 build. Could you pls try the TEST build 1.50.0.18 (separate thread to this one) and let me know if it's fixed in that version?

Thanks

Paul

[polywog7]

Hi again,

Yep its fixed in the .18 build. Thanks!

[eric_clough]

Hi Paul ...

In the last number of builds including .18 I cannot adjust the daylight turbidity ... it always returns to '2'.
Adjusting 'power' does take care of brightness levels but as I understand turbidity it should soften the scene as well as darken it if turned up and the opposite if decreased. I think I would like 1.25 or 1.50 if possible but I can't get below 2.

cheers,
eric

[archtobi]

Hi Paul,
i had the issue with the slow octane ui redraw and i fixed by your advise, thanks for that. When i updated to the most recent version of the plugin i noticed that the "use priority" checkbox at the settings is not ticked by default. Maybe that would be a good preset to prevent users with single gpu from the redraw issues.

kind regards
Tobi

[face_off]

Adjusting 'power' does take care of brightness levels but as I understand turbidity it should soften the scene as well as darken it if turned up and the opposite if decreased. I think I would like 1.25 or 1.50 if possible but I can't get below 2.

Hi Eric - the minimum value for turbidity is 2, which is why you can't go any lower. That's the same minimum as in Octane Standalone.

When i updated to the most recent version of the plugin i noticed that the "use priority" checkbox at the settings is not ticked by default. Maybe that would be a good preset to prevent users with single gpu from the redraw issues.

From Octane 1.21 onwards, the Enabled and Use Priority status of each card come from the Cuda settings in Octane Standalone (and if you change the settings in the plugin that will also change the settings in Standalone). So setting defaults would need to happen at the Octane Standalone end - and you would need to do a Feature Request for Standalone rather than the plugin for this.

Paul