OctaneRender® for Poser beta - build 1.11u [OBSOLETE]

[face_off]

Thanks for letting me know Zay. Definitely a Reality bug. Nothing to do with the Octane plugin.

Paul

[Pandarr]

There seems to be some conflict with the new Reality 3 plugin and the Octane plugin.

D:\Poser Pro 2012sr3.1\Runtime\Python\addons\Reality\__init__.p y:97: RuntimeWarning: tp_compare didn't return -1 or -2 for exception

Paolo thinks it's an issue with the Octane plugin as there's no tp_compare in the Reality 3 plugin. So who's right and how do we fix it ?

A new version of Reality came out today which fixed this... for me anyway.

[mlru]

OK, there's definitivly some strange in this version.
On several times i have crashes with this version, i never had in the versions before:

Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 10431, in ShowOctaneOptionsWindow
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 7483, in Init
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 8805, in refreshScene
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 9774, in copyMeshToOctane
WindowsError: exception: access violation writing 0x0000000000000000

Sadly it's not very good reproducable, but right now I'm having this when I load a saved file and try to bring it to Octane. Sometimes after hiding or adding a prop, it loads into the plugin and works just fine. That's the only workaround I've found so far. As I said, that never happend in the previous versions and is surely not a matter of texture or poly count.
I've added the logfiles, if that helps.

Uwe

[face_off]

Uwe

I have just uploaded a versed version which potentially fixes this issue. Pls re-download 1.11u (this new version will show "1.11u-5" on the Setup screen title). This version also fixes a bug that was being triggered if texturemap files had special characters in them.

Paul

[face_off]

Hi

I have just uploaded a revised version which addresses the following:

1.11u-6
-------
Fixed bug where sometimes animation settings would not be saved
Fixed issue where non-numeric characters could be entered into the animation "end frame" text box

Pls re-download from the link in the first msg of this thread.

Paul

[orion_uk]

Thanks V-much indeed

[RGUS]

Hi

I have just uploaded a revised version which addresses the following:

1.11u-6
-------
Fixed bug where sometimes animation settings would not be saved
Fixed issue where non-numeric characters could be entered into the animation "end frame" text box

Pls re-download from the link in the first msg of this thread.

Paul

Hi Paul...
I just downloaded and unzipped the X64 version to my poser sub-folders, restarted Poser and now no "Octane Render" under the Render pulldown... how to I get it back?

[face_off]

I just downloaded and unzipped the X64 version to my poser sub-folders, restarted Poser and now no "Octane Render" under the Render pulldown... how to I get it back?

Sounds like it installed in the wrong folder. Did you delete the previous version? (I normally don't - you can safely install new version over the top of the old ones).

You only need ...

Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\__init__.pyc

to get the OctaneRender menu item to show.

Paul

[RGUS]

OK checked the file exists in the correct folder... image attached...
Ran the python script manually from Poser File pulldown menu... and got the second image error message.
If you say re-install Poser, I'm gonna spit the dummy...LOL
Any glues?

[RGUS]

Oh and BTW paul... after doing all that... still no Render Octane option... though I have been able to get it to work under the 32bit version of Octane... sort of defeats the purpose of an i7 though.
Regards,
Deane