OctaneRender® for Poser (Windows) - build 1.20.2 [OBSOLETE]

[face_off]

Thanks Deane - I need the octaneplugin.log too - from the same point in time.

Paul

[RGUS]

I really need to read the manual to try and find all these files scattered over hard drives... where the heck do I fine that file... it ain't in the c:user... blah, blah, blah

[face_off]

http://render.otoy.com/manuals/Poser/?page_id=26 has the file location Deane.

[RGUS]

Don't just love Windows and it's required file structure...
Sorry to piss you around Paul... I did find it...
Attached...

[face_off]

Hi Deane

When you are starting Poser, it is opening a startup scene which already has Octane values set for it - including the Progressive Save Folder - so that is overriding the location on the config.xml. So you need a blank startup scene, or recreate a new startup scene and DON'T start the plugin before saving it.

Paul

[RGUS]

Yeah that was it Paul... trap for young players eh! Octanes way or no way at all...LOL
Thanks for your help mate.

[Pandarr]

Hi Deane

When you are starting Poser, it is opening a startup scene which already has Octane values set for it - including the Progressive Save Folder - so that is overriding the location on the config.xml. So you need a blank startup scene, or recreate a new startup scene and DON'T start the plugin before saving it.

Paul

Ohhhh that's interesting and completely makes sense. I don't have that issue but can certainly see getting bit by it. I'll file that away for the future when it happens to me 8 years down the road!

[Zay]

I have noticed a couple of times this error when refreshing the scene using subdivision level 1:

Traceback (most recent call last):
File "D:\Poser Pro 2014\Runtime\Python\lib\site-packages\wx-2.9.1-msw\wx\_core.py", line 16291, in <lambda>
lambda event: event.callable(*event.args, **event.kw) )
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\SetupForm.py", line 571, in callAfterRefreshVertices
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 2682, in refreshVertices
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 1059, in updateMesh
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 638, in createMeshNode
AttributeError: PropMeshNode instance has no attribute 'numPolysToLoad'

[face_off]

I have noticed a couple of times this error when refreshing the scene using subdivision level 1:

Traceback (most recent call last):
File "D:\Poser Pro 2014\Runtime\Python\lib\site-packages\wx-2.9.1-msw\wx\_core.py", line 16291, in <lambda>
lambda event: event.callable(*event.args, **event.kw) )
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\SetupForm.py", line 571, in callAfterRefreshVertices
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 2682, in refreshVertices
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 1059, in updateMesh
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 638, in createMeshNode
AttributeError: PropMeshNode instance has no attribute 'numPolysToLoad'

Hi Zay

I've had a look at the but couldn't reproduce it. When this next happens, can you pls immediately take a copy of the octaneplugin.log file and send it to me and save the pz3 somewhere to. The octaneplugin.log should indicate which figure or prop caused the issue.

Also, could you make a note of whether auto-fresh was ON or not pls.

In tracking this down I noticed if you have Unimesh skinning ON and the figure is NOT visible, it renders in the default stance! I will fix this.

Thanks

Paul

[mlru]

Hi Paul,
I wonder if it would be a too big effort to add a function like "change all floatimages to images for this figure"?
Would make life easier when running over the grayscale image limit while still having enough room for RGBs.
just suggesting....