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

[RGUS]

What scene are you playing with Paul that causes the crash... nobody has said they are using the one I posted... so perhaps there is another out there that is crashing and my eye colour matches what I'm full of.

We are all trying the scene you posted Deane.

Paul

Oh good... well not good really... but sorta you know what I mean...

Anyways... using lesser Poser plugin versions and lesser nvidia drivers this is what is suppose to happen.

http://rgus.deviantart.com/art/Flights- ... -466510180

[Zay]

Paul, can you add a checkbox in the configuration window to prevent any displacement maps to be added to the scene? Or is there a way to do that already?

[face_off]

Paul, can you add a checkbox in the configuration window to prevent any displacement maps to be added to the scene? Or is there a way to do that already?

Do you mean...
a) Disable the conversion of displacement maps from Poser materials when initially converting the Poser materials to Octane materials, or
b) Disable the rendering of displacement maps even if there is a displacement map for an Octane material?

Paul

[RGUS]

Paul, can you add a checkbox in the configuration window to prevent any displacement maps to be added to the scene? Or is there a way to do that already?

Do you mean...
a) Disable the conversion of displacement maps from Poser materials when initially converting the Poser materials to Octane materials, or
b) Disable the rendering of displacement maps even if there is a displacement map for an Octane material?

Paul

LOL... I read this several times... geees Paul... I think he means disable anything that causes an Octane crash.

[Zay]

Do you mean...
a) Disable the conversion of displacement maps from Poser materials when initially converting the Poser materials to Octane materials, or
b) Disable the rendering of displacement maps even if there is a displacement map for an Octane material?

The first one (a). An option to have the displacement node forced empty when converting a scene. I have seen many times now Poser rendering extremely slow when displacements are used and it's extremely time consuming to located and disable displacement now when you have 100's of materials.

[face_off]

The first one (a). An option to have the displacement node forced empty when converting a scene. I have seen many times now Poser rendering extremely slow when displacements are used and it's extremely time consuming to located and disable displacement now when you have 100's of materials.

OK, I will add this.

Paul

[face_off]

I finally got one...
A scene that consistently gives me an nVidia 999 failure using standalone and Poser plugin versions greater than 1.54
At version 1.54 everything works perfectly, and all geometry in the scene is rendered.
Anything greater than 1.54 is missing scene geometry in the render and crashes to 999 after a minute or so.

Deane - Otoy have found the error, and it is related to the displacement map rendering, and will be fixed in the next release of Octane.

Paul

[RGUS]

I finally got one...
A scene that consistently gives me an nVidia 999 failure using standalone and Poser plugin versions greater than 1.54
At version 1.54 everything works perfectly, and all geometry in the scene is rendered.
Anything greater than 1.54 is missing scene geometry in the render and crashes to 999 after a minute or so.

Deane - Otoy have found the error, and it is related to the displacement map rendering, and will be fixed in the next release of Octane.

Paul[/quote
Thanks Paul... I really did think it was just me for a moment then...

[Stevenyang0430]

Hi Paul
When I hit the "Stop all the scene and setting update" to active then hit it again , it starts refreshing all material even if I didn't touch anything and then error occurs (Viewport opened at the beginnin) (No subdiv is added):

Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\SetupForm.py", line 469, in EventNoUpdates
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 5271, in RefreshSetupForm
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 183, in CreateNodesFromPoserScene
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 212, in ConvertMaterial
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 3476, in createNodeFromSavedTree
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 3476, in createNodeFromSavedTree
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 3243, in createNodeFromSavedTree
WindowsError: exception: access violation reading 0x000000011AD37004



This do not happen when first loading and first render, only occur when you activate the "stop update" and deactivate it. And wait for around a minute "Video card not responding" notice occur, but when you close it and open the view port again, it starts working again. Sometimes the notice didn't occur and I close-reopen the viewport and it still works . Is that a problem with displacement map as well? (Then error should occur when I first load the scene into octane).

(The problem only occur when you stop update and reactivate it, if I don't use 'stop update' everything works fine)

Config:
Win7 professional 64 bit
i7-4930K processor
dual Geforce 770 SLI
Poser 2014 pro

Steven

[face_off]

When I hit the "Stop all the scene and setting update" to active then hit it again , it starts refreshing all material even if I didn't touch anything and then error occurs (Viewport opened at the beginnin) (No subdiv is added):

Yes, if you unclick that button it force a scene refresh, because the plugin does not know if you changed anything whilst the "No Updates" button was pressed.

Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\SetupForm.py", line 469, in EventNoUpdates
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 5271, in RefreshSetupForm
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 183, in CreateNodesFromPoserScene
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 212, in ConvertMaterial
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 3476, in createNodeFromSavedTree
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 3476, in createNodeFromSavedTree
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 3243, in createNodeFromSavedTree
WindowsError: exception: access violation reading 0x000000011AD37004

I couldn't reproduce this problem, so I suspect there is an figure/prop in your scene which is triggering this. Does the above error occur with the default Andy scene? If you can send me the simplest scene this occurs with, I can track the problem down. Also, there are some issue with displacement in 2.02 which are fixed in the next release (available very soon). So if that scene had a displacement map, it may have caused that error, but will be fixed in the next release.

Paul