OctaneRender 2 for Poser (Windows/OSX) [STABLE] Tweet

[RGUS]

Yes
1.55.0.33 causes the same problem... but no worries... it seems I'm the only one having the problem. I guess development versions above 1.54 just aren't for me. A bugger I upgraded to version 2.00... oh well.. early adopters should expect this I suppose.

[face_off]

1.55.0.33 causes the same problem... but no worries... it seems I'm the only one having the problem. I guess development versions above 1.54 just aren't for me. A bugger I upgraded to version 2.00... oh well.. early adopters should expect this I suppose.

Looks like 1.55/2.0 has introduced this problem. Have you reported it to Otoy?

[face_off]

Deane - you could also try exporting from the 1.54 version of the plugin an importing into 2.0 Standalone. If the problem shows in Standalone but not the plugin that will prove it's not n issue at your end, and Otoy can look into it. But if Otoy don't have your test scene showing the problem, it's hard for them to fix.

In the meantime, a workaround might be to simply increase the Scale factor in the plugin Settings.

Paul

[RGUS]

The real problem with reporting problems is that the forum index is not very intuitive... and if one makes a mistake posting in the wrong area one gets their proverbial kicked and one feels like a dick trying to resolve issues where ever they may occur.
So what would be really helpful would be for people that recommend they post here and there, if they would leave a link to the appropriate forum so none of this mis-posting occurs. So having said all that Paul... which forum or link to forum should I be posting the image results and ORBX file too? Just too many places to post and get it wrong.

[face_off]

So what would be really helpful would be for people that recommend they post here and there, if they would leave a link to the appropriate forum so none of this mis-posting occurs. So having said all that Paul... which forum or link to forum should I be posting the image results and ORBX file too? Just too many places to post and get it wrong.

http://render.otoy.com/forum/viewtopic.php?f=24&t=40381

I suggest getting a scene which exhibits this problem, deleting all geometry except the hair and hear, delete all the texturemaps except the hair transmap. Then export to ORBX. Load into Octane 1.54 Standalone and render (where the problem will not be present) and take a screenshot. Then load the ORBX into Octane 2.0 Standalone and render (where the problem WILL be present). Zip up the ORBX and post it with the 2 screenshots to that thread (mention that 1.55 has the problem too). Then Otoy can investigate.

Paul

[RGUS]

Did all this and bugger me days... it works fine with standalone versions... but only works up until poser plug-in version 1.54... everything after that turns to custard.
Obviously something I'm doing wrong since no else is experiencing any similar problems... think I should go back to firefly and stop annoying people.

[face_off]

Did all this and bugger me days... it works fine with standalone versions... but only works up until poser plug-in version 1.54... everything after that turns to custard.
Obviously something I'm doing wrong since no else is experiencing any similar problems... think I should go back to firefly and stop annoying people.

Sounds like a plugin issue in that case. Are you able to send me a pz3 with the head and hair geometry and the transmap?

Also, have you tried a complete uninstall and re-install of the latest version of the plugin?

And did you try the "scale" workaround?

Paul

[Erick]

... think I should go back to firefly and stop annoying people.

Awww .. that'd be a shame (even tho your FierFly renders are exceptional as well =) )

What is a good way, to (trying to) re-create this issue? ... just with different props and figures, as I don't have the exact same ones, as in you render.
Maybe I could try and help here.

[Zay]

In the Render Options List, if you for example select Maxsamples, in the Node Type below you can enter the value of Max samples. BUT - if you hit the Refresh button first and then type a value, you will get this error:
Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\Node.py", line 1253, in EventTextCtrlKey
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\Node.py", line 2695, in EventNodeChanged
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\Node.py", line 831, in SetOctaneApiNodeValue
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 3034, in displayError
ValueError: Error in SetOctaneApiNodeValue - null Octane node for node maxsamples, node type = int

My guess is that when you hit the refresh button, the option you have selected in the list will become unselected after you refresh the scene. But the node type is still there for you to enter a value. This happens for all the options in the list I have tried.

[face_off]

In the Render Options List, if you for example select Maxsamples, in the Node Type below you can enter the value of Max samples. BUT - if you hit the Refresh button first and then type a value, you will get this error:

Thanks. Fixed in the next release.

Paul