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

[face_off]

Hi Deane

Is Reality working?

Have you installed/changed anything else between the old Octane plugin working, and the latest version not working?

If you install the previous version of the Octane plugin does it work?

Paul

PS: Can you provide the octaneplugin.log file pls.

PPS: There is only one file that has changed between the version you where running and this latest version....and that file is not even loading, so it's is highly unlikely that the installation of the latest version has caused the issue. I would say something else is amiss.

[RGUS]

Found it... geees... all python is equal but some python is more equal than others...
Seems this bugger: http://www.runtimedna.com/Scripts-Auto-Launch.html
caused the problem... it's possessive, it want total control and stuff anything else that tries to use my space!!!

I found by re-installing the latest Poser Service patch... and then Octane ... everything was back to normal.

Sorry to waste your time Paul...
I'll go and stick my head in a bucket of water now.
Thanks
Deane (RGUS)

[mlru]

new version works fine for me - until now...

[KeithM]

I'm getting the same problem (no Octane render option), and I've removed the Scripts Auto Launch from Poser.

[RGUS]

I'm getting the same problem (no Octane render option), and I've removed the Scripts Auto Launch from Poser.

You have to re-install the latest Poser service patch 3.1 (I think), then Octane... and the problem will go away. Well it did for me anyway.

[face_off]

I'm getting the same problem (no Octane render option), and I've removed the Scripts Auto Launch from Poser.

There is currently a bug in Poser, where if whilst all the plugins are being initialised, one of the plugins throws an exception, then the remaining plugins do not get loaded. When this occurs, there are NO error messages reported to the user! I reported it to Smith Micro late last year. So in your case, one of the plugins you have installed is being initialised and is crashing, resulting in the Octane plugin not being initialised. The developer of the plugin causing the issue needs to be notified that this is happening.

Could you pls send or attach your octaneplugin.log?

Thanks

Paul

[face_off]

1.13 build posted. http://render.otoy.com/forum/viewtopic.php?f=45&t=31101.

Paul

[RGUS]

1.13 build posted. http://render.otoy.com/forum/viewtopic.php?f=45&t=31101.

Paul

Thanks Paul...
I tried it... but the limitation of crashing when swapping from daylight to environment makes this almost un-useable.
Is Octane Standalone going to update soon? I've gone back to v1.11u6, it seems to be more stable.

[face_off]

I have received the new libraries from Otoy (looks like they pulled an all-nighter to fix this for us!), and it seems to fix the crash. You can now re-download the installer from the link at the top of this thread. Pls let me know how you go, and thank you for your patience.

[EDIT: I am looking for a Mac user to test the Mac version of the plugin. Preferably a user who already has this plugin (Windows version), but could be a Mac user who has Octane Standalone only too. Pls PM if interested].

Paul

[VirginieC]

Hello,
I'm just here to mention that for me octane pluggin and reality work fine together on my poser (pro 2012, windows 7).
I'm staying for now on the 1.11u because of other compatibilities reasons.
Yet, I'd like to mention a little "bug".
Yesterday, I exported a material in a folder, then I moved the folder elsewhere. Just after, when I tried exporting another material, poser crashed just when I right clicked to export. It was probably because the pluggin did not find anymore the folder where it was supposed to export. Not a big problem, but there may be a little code to add in order for the pluggin to come back to the "initial pluggin folder" if the actual folder does not exist anymore. Note I think it is the reason, but I'm not 100% sure of it