OctaneRender® for Poser (Windows) - build 1.20a [OBSOLETE] Tweet

[face_off]

I checked the priority settings and tried using only 1 of my gpus, which resulted in a speed up(didn't matter which one, same result), still a little less than half of what I get with 1.13u.

Do you have SLI enabled in your NVidia settings? (It should be disabled).

Paul

[CorDox]

I checked the priority settings and tried using only 1 of my gpus, which resulted in a speed up(didn't matter which one, same result), still a little less than half of what I get with 1.13u.

Do you have SLI enabled in your NVidia settings? (It should be disabled).

Paul

Yes, it was disabled. tried re-enabling SLI and disabling it again, and that seems to have cleared it up. Starting to think it's a driver issue or bad installation. Still wonder why it didn't affect the older version though.

[TakashiKurashima]

Poser Pro 2014 Sr2 was released, this build seems 25473.

Can I render soft-body dynamics figure with Oc for Poser 1.20a5 ?

[face_off]

Can I render soft-body dynamics figure with Oc for Poser 1.20a5 ?

You should be able to - yes. I haven't thoroughly tested it yet though - but initially, it seems to work.

[Lledeline]

Hello!
I tried to use the latest 1.20 release of poser pluging in poser pro 2014 with SR1.
When the scene is loaded some figures are ignored in the texture tree if if they appears they can't be textured even by DB
Captures of messages à get when I load the scène or try to change the textures.
This is since I changed the defaut temp folder in PP but now I have resetted and all seems as before

Why does it search in PP 2012 ? The plug is in the right place in PP 2014 runtime Python addons and scrptmenu.
Thank you
I use it in PP2012 and all is OK

[face_off]

I tried to use the latest 1.20 release of poser pluging in poser pro 2014 with SR1.
When the scene is loaded some figures are ignored in the texture tree if if they appears they can't be textured even by DB
Captures of messages à get when I load the scène or try to change the textures.
This is since I changed the defaut temp folder in PP but now I have resetted and all seems as before

Hi - this looks like end error being generating within PoserPython. I wonder if it's related to the '~' in your username? I see that your Poser temp folder does not seem to be pointing to a valid folder (since it has ignore the '~' in your username). Does that sound feasible?

Also....what SR for 2014 do you have installed? If everything is OK on 2012, re-installed SR1 (and the new SR2 for PP2014), and also reinstall the plugin to be sure.

Why does it search in PP 2012 ? The plug is in the right place in PP 2014 runtime Python addons and scrptmenu.

That msg simply means the python code was compiled on 2012.

Paul

[face_off]

OK, I found it - or at least one reproducible way:
open Poser
load a figure or prop from the library
open the Octane plugin and the viewport
close the plugin
open a saved Poser scene, do not save the actual scene
open the plugin

then it will not find the saved settings and start new with the default rendertarget and fresh converted materials.

Hi Uwe. Poser Pro 2014 SR2 (now available) should rectify this issue for you.

Paul

[face_off]

New version available.

http://render.otoy.com/forum/viewtopic.php?f=45&t=34442.

Paul

[Lledeline]

Hello!
Ive corrected the temp destinatory folder.
I've reinstaller poser pro 2014, SR1 ans SR2 and tried to reinstall the plug (1.20a2 and yesteday's one) after having deleted the previous one in Window.
I still have the same messages of error and added figures are not textured and dont appears in the texture tree. If one appears, I can't texture it and DB doesn't work)
In fact in PP 2012 I used the 1.13 version. when trying to run the installer of 1.17 pr 1.20. I have the same issues. Back to 1.13, all is OK.
The curious thing is that some figures loads well (alfassed clothes are OK)and the material tree is OK for them.
But 80% of the clothes doen't works and 50% of hair.
Are the objects or material nodes of this elements compatibles with octane ? But they works in 1.13 (in PP 2012, I didn't try in 2014)
I saw in the beginning of the thread that somebody had the same issue but it seems to had been fixed with an nex version of the plug/
I'm lost, as I'm not a computer's master.
Thanks if you can give me some other keys

[face_off]

Are the objects or material nodes of this elements compatibles with octane ? But they works in 1.13 (in PP 2012, I didn't try in 2014)
I saw in the beginning of the thread that somebody had the same issue but it seems to had been fixed with an nex version of the plug/
I'm lost, as I'm not a computer's master.
Thanks if you can give me some other keys

I'm really sorry you are having problems with the plugin. At this stage of development, I'm finding most of the issues people have are with corrupt or non-standard figures or props.

Have you tried determining if it's a particular prop or figure causing the problem? To do this, shutdown the plugin, delete a figure or prop, reopen the plugin and see if the error persists. If it does, delete another figure or prop. You may well find it is a particular figure or prop you are using in all your scenes which has an issue with it.

Also - can you open a scene which gives you the problem, then rightclick the Settings tab tree and select the last option ("print node save tree" or similar), and then email to me or post here.

Plus, can you pls create the simplest scene you can which gets this error - using the Standard Poser 2014 figures (Roxie) and standard 2014 hair props. Save the pz3 then send it to me and I will have a look. Email to paul at physicalc-software dot com.

Also, what is your Poser temp folder set to now pls?

And can you pls download the very latest version of the plug (1.20.2) and install it and post the python exception window for get on an erroneous scene - so I can pinpoint the exact line throwing the error.

Sorry for all the questions. Just trying to get you up and running.

Paul