OTOY Forums

RGUS wrote:need a 'remove all displacement automatically assigned by plug-in' command.

I was also disappointed that Octane doesn't support procedural displacement. So many options for procedural nodes, but none can be used for displacement. Bummer.

Tried to access attribute via invalid ID A_VALUE (171)
Tried to access attribute via invalid ID A_VALUE (171)
Tried to access null item
Tried to access attribute via invalid ID A_VALUE (171)
We can't evaluate items of a different version (version 0)!
Tried to access null item
Tried to access attribute via invalid ID A_VALUE (171)
We can't evaluate items of a different version (version 0)!
This source doesn't contain any primitives!
This source doesn't contain any primitives!

Lots of displacement stuff assigned automatically in the scene. DM Productions stuff.
I'll turn off displacement see if it goes away....

Yup.. that did it... need a 'remove all displacement automatically assigned by plug-in' command.

Hi Deane - if you export the scene to ORBX, does Octane Standalone 2.16 pop the errors too (you need to check the Cuda Log)? If so, could you send me the ORBX pls? Alternatively, would it be possible to isolate the prop or figure giving this error?

Thanks

Paul

The Cuda errors that Deane/RGUS is experiencing are due to having a negative Displacement in the Poser material, which the plugin is setting to 0 in Octane. So a 0 Displacement in Octane = Cuda error. I will report this to Otoy.

Paul

I saved a Material collection that was working fine in the plugin from a V4 figure. When applying the saved material to a new figure the plugin gave me this error:

Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\SetupForm.py", line 2078, in MenuSelectionCb
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 1115, in MenuCommand_ReimportPropFigureMaterialsFromPoser
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 220, in ConvertMaterial
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 886, in createOctaneMaterialFromPoserShaderTree
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 886, in createOctaneMaterialFromPoserShaderTree
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 869, in createOctaneMaterialFromPoserShaderTree
ValueError: invalid literal for float(): 1.0_3

Zay - can you pls send me the file? No need for the texturemaps.

Paul

face_off wrote:Zay - can you pls send me the file? No need for the texturemaps.

Paul

File sent.

Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\SetupForm.py", line 2078, in MenuSelectionCb
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 1115, in MenuCommand_ReimportPropFigureMaterialsFromPoser
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 220, in ConvertMaterial
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 886, in createOctaneMaterialFromPoserShaderTree
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 886, in createOctaneMaterialFromPoserShaderTree
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 869, in createOctaneMaterialFromPoserShaderTree
ValueError: invalid literal for float(): 1.0_3

Regarding the exception that Zay posted....

This is caused when the Octane nodes are saved to the Poser material by the plugin, and then Poser renames the nodes in the Poser material (in this case, it's on the SkinToro material). I have not seen this happen before, however I suspect it may occur when saving the Poser material as a collection (and Poser renames some elements to keep certain name unique). The solution is to:

1) Import the MC6 material collection in the Poser Material room
2) Start the plugin
3) In the plugin Materials tab, for the SkinTorso material, "Delete Octane Node From Poser Material"
4) For the figure, "Reconvert Materials....." (this will reload the Octane nodes from the Octane nodes saved in the Poser Materials)
5) Copy and paste SkinHip to SkinTorso (since the SkinTorso Octane nodes were cleared in step 3)
6) Save the material collection (since the original one was corrupt).

If this problem happens again I will add some code to the plugin to better handle this situation.

Thanks

Paul

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

2.20.0.39
- Compiled with Octane 2.20 (see Octane Standalone for details)
- Implemented Render Layers from Octane 2.20 (assign the Layer Id on the Mesh item, and then select the Layer Id to render in the Render Layer section of the Settings tree).
- Fixed issue when input from the LocalDb was not working for materials downloaded from the LiveDb
- Added Tooltips to the Octane pins for all nodes in the Setup and Materials trees
- Fixed Octane Log error resulting from converting Poser materials with negative displacement. In this case, the Poser material will convert to an Octane material with a displacement amount of 0.00001

Paul

think I found bug. look like you can no longer import poc poe files .
on Genesis 2 female looks like you can no longer inport

think I found bug. look like you can no longer import poc poe files .
on Genesis 2 female looks like you can no longer import

Rightclick the figure in the tree to import/export all materials, or rightclick a material to import/export a single material.

Paul