OctaneRender 2 for Poser (Windows/OSX) [OBSOLETE]

[face_off]

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

2.2.0.19
- Compiled against Octane 2.02

Paul

[wimvdb]

Thanks Paul,
719 error is fixed with the plugin as well

[mlru]

There is an error when importing saved materials to a node that has a displacement assigned:

I couldn't reproduce this. Are you able to provide a workflow that I can follow to get this error pls?

Paul

Ok, there you go:
1 load a V4
2 in the material room add a displacment map to eg Skin Torso
3 open Octane plugin
4 select the material zone with the displacement
5 right-click import material - retain existing imagemaps
6 error.

hope that helps,
Uwe

[Zay]

Under Configuration if I change the Subdivision Scheme and Save I get this:

Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\Configuration.py", line 675, in EventSave
AttributeError: 'ConfigurationForm' object has no attribute 'videoCardComboBox'

[face_off]

1 load a V4
2 in the material room add a displacment map to eg Skin Torso
3 open Octane plugin
4 select the material zone with the displacement
5 right-click import material - retain existing imagemaps
6 error.

Fixed in the next release.

Under Configuration if I change the Subdivision Scheme and Save I get this:

Fixed in the next release.

Paul

[face_off]

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

2.2.0.20
- Fixed error when importing with Retained texturemaps was displaying the incorrect error if there were multiple displacement maps
- Fixed error raised when saving the Configuration

Paul

[face_off]

Selecting a material from the Live DB - FAB_Velvet-1a from Non-organic/Cloth

Deane - I checked this issue out, and it is due to that LiveDb material having an Octane Gradient node, and at this stage the Poser plugin does not support the Gradient node. But it is something I'm planning on implementing in the next few months.

Paul

[Zay]

Any chance that an exported animation to orbx can have it's own geometry nodes in standalone like it does when exporting without animation?

[Zay]

Camera path motion doesn't show when using the plugin in Poser. Nor does it get exported when exporting to standalone.

[face_off]

Any chance that an exported animation to orbx can have it's own geometry nodes in standalone like it does when exporting without animation?

At the moment, the plugin sets the rendertarget mesh pin item Geometry Group as the Alembic container - so in effect, all scene vertices get stored in that ABC node. In theory, each figure/mesh could be split up and store separately in an ABC node (and the geometry group NOT animated), but that would make the scene very difficult to edit in Octane Standalone - I'm not sure what you are trying to achieve by having separate geometry nodes. In summary, it's possible, but a bit of work to implement, and may not work as well as the current system.

Camera path motion doesn't show when using the plugin in Poser. Nor does it get exported when exporting to standalone.

Not sure what you mean here. If I set a camera position at frame 1 and another at frame 30 and then export to ORBX, the camera positions at each frame re correctly stored in the Thin Lens Camera node when loaded into Standalone.

Paul