Page 6 of 28

Re: OctaneRender® for Poser (Windows) 2.0 [TEST]

Posted: Mon Jun 23, 2014 10:49 am
by face_off
I have refreshed the installers at the top of this thread with:

2.01.0.18
- Compiled against Octane 2.01
- Fixed python error "ValueError: Error in SetOctaneApiNodeValue - null Octane node for node maxsamples, node type = int"

Octane 2.01 removes the previous texturemap number limits - which is fantastic news for Poser users, since we were often hitting these limits when there were many figures/props in the scene.

Paul

Re: OctaneRender® for Poser (Windows) 2.0 [TEST]

Posted: Mon Jun 23, 2014 11:05 am
by samhal
face_off wrote:I have refreshed the installers at the top of this thread with:

2.01.0.18
- Compiled against Octane 2.01
- Fixed python error "ValueError: Error in SetOctaneApiNodeValue - null Octane node for node maxsamples, node type = int"

Octane 2.01 removes the previous texturemap number limits - which is fantastic news for Poser users, since we were often hitting these limits when there were many figures/props in the scene.

Paul
YAY!!! :D

Re: OctaneRender® for Poser (Windows) 2.01 [TEST]

Posted: Mon Jun 23, 2014 11:47 am
by Zay
It looks like it works :)
textures.jpg

Re: OctaneRender® for Poser (Windows) 2.01 [TEST]

Posted: Mon Jun 23, 2014 11:49 am
by Zay
StoneMasons Bigcity, AbandonedCity 1 and AbandonedCity 2 crash Poser (octane.dll).

Re: OctaneRender® for Poser (Windows) 2.01 [TEST]

Posted: Mon Jun 23, 2014 12:40 pm
by face_off
StoneMasons Bigcity, AbandonedCity 1 and AbandonedCity 2 crash Poser (octane.dll).
I had a crash on a very large Modo scene - and I wondered if perhaps it was due to running out of VRAM. Could that be happening to you? What does the scene texturemap Poser script report as the total VRAM required for that scene?

Paul

Re: OctaneRender® for Poser (Windows) 2.01 [TEST]

Posted: Mon Jun 23, 2014 12:41 pm
by face_off
It looks like it works
Number of HDR textures looks wrong in that screenshot. I will check that out.

Paul

Re: OctaneRender® for Poser (Windows) 2.01 [TEST]

Posted: Mon Jun 23, 2014 1:06 pm
by Zay
For AbandonedCity 1 :
----------------------
Total Num Texture Maps (rgb) : 50
Total Num Bump/Trans Maps (grayscale) : 48
Total Memory Required for Textures : 609.9MB (assumes only LDR textures)
----------------------

DEBUG:root:Opening Viewport - setting rendertarget
And then it crashes.

It also crash in v.2.0.9.17

Re: OctaneRender® for Poser (Windows) 2.0 [TEST]

Posted: Mon Jun 23, 2014 1:12 pm
by RGUS
face_off wrote:
Did all this and bugger me days... it works fine with standalone versions... but only works up until poser plug-in version 1.54... everything after that turns to custard.
Obviously something I'm doing wrong since no else is experiencing any similar problems... think I should go back to firefly and stop annoying people.
Sounds like a plugin issue in that case. Are you able to send me a pz3 with the head and hair geometry and the transmap?

Also, have you tried a complete uninstall and re-install of the latest version of the plugin?

And did you try the "scale" workaround?

Paul
Been trying top send this for the last couple of days... but obviously the ZIP file is too big for the site servers to accept, just hangs ans sits for ages after the submit button pressed.

Re: OctaneRender® for Poser (Windows) 2.0 [TEST]

Posted: Mon Jun 23, 2014 1:14 pm
by RGUS
face_off wrote:I have refreshed the installers at the top of this thread with:

2.01.0.18
- Compiled against Octane 2.01
- Fixed python error "ValueError: Error in SetOctaneApiNodeValue - null Octane node for node maxsamples, node type = int"

Octane 2.01 removes the previous texturemap number limits - which is fantastic news for Poser users, since we were often hitting these limits when there were many figures/props in the scene.

Paul
Do you mean Octane 2.01 Standalone or Octane Poser Plugin 2.01... "removes the previous texturemap number limits"... ?

Re: OctaneRender® for Poser (Windows) 2.01 [TEST]

Posted: Mon Jun 23, 2014 1:15 pm
by face_off
For AbandonedCity 1 :
----------------------
Total Num Texture Maps (rgb) : 50
Total Num Bump/Trans Maps (grayscale) : 48
Total Memory Required for Textures : 609.9MB (assumes only LDR textures)
----------------------

DEBUG:root:Opening Viewport - setting rendertarget
And then it crashes.

It also crash in v.2.0.9.17
Not a memory issue then. Could it be that scene uses a displacement map and the displacement amount is too high? Are you using Octane Subd for any props? (there is a known issue with certain props with the OpenSubDiv library). If you can't work it out, pls send me the scene and I'll take a look.

Paul