Page 3 of 4

Re: OctaneRender® for Poser beta WINDOWS - build 1.14a [TEST

PostPosted: Thu May 23, 2013 3:13 pm
by Nod64
Excellent. This is the excuse that I needed to reinstall Poser. :mrgreen:

Re: OctaneRender® for Poser beta WINDOWS - build 1.14a [TEST

PostPosted: Thu May 23, 2013 4:58 pm
by Erick
I guess I found a minor thingy ..

I opened the LiveDB and accidentally double-clicked on the empty space in between the two material columns and an error window popped up.

Re: OctaneRender® for Poser beta WINDOWS - build 1.14a [TEST

PostPosted: Thu May 23, 2013 5:57 pm
by elenacalderas
I just tried to paste an image into the diffuse node of a glossy material (which held an RGB node before) and got this message:

Code: Select all
Traceback (most recent call last):
  File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\SetupForm.py", line 1582, in MenuSelectionCb
  File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 865, in MenuCommand_PasteReplaceMaps
  File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 906, in Paste
NameError: global name 'newNode' is not defined


Edit: Once that happened, it also throws out errors when you then try to manually put an image into the diffuse node by selecting "image".

Re: OctaneRender® for Poser beta WINDOWS - build 1.14a [TEST

PostPosted: Thu May 23, 2013 6:44 pm
by Zay
Loading a .poc file still crashes Poser2012 Sr3.1.

Re: OctaneRender® for Poser beta WINDOWS - build 1.14a [TEST

PostPosted: Thu May 23, 2013 6:50 pm
by RGUS
When I refresh the Octane scene from Poser, the materials in the Octane Scene are all screwed up. Reloading the scene [geometrygroup] fixes it... is this normal?

Re: OctaneRender® for Poser beta WINDOWS - build 1.14a [TEST

PostPosted: Thu May 23, 2013 6:52 pm
by Erick
Zay wrote:Loading a .poc file still crashes Poser2012 Sr3.1.

Just had a quick test on this ... same result here. A freezing Poser.

Re: OctaneRender® for Poser beta WINDOWS - build 1.14a [TEST

PostPosted: Thu May 23, 2013 7:23 pm
by ch0pper
yep same here Loading a .poc file still crashes Poser2012 Sr3.1.

crash

Re: OctaneRender® for Poser beta WINDOWS - build 1.14a [TEST

PostPosted: Thu May 23, 2013 10:33 pm
by face_off
I have fixed the loading of POC files. However I've found an issue with pasting nodes which is proving harder to rectify. Will hopefully have a fix uploaded and available in the next hour.

Paul

Re: OctaneRender® for Poser beta WINDOWS - build 1.14a [TEST

PostPosted: Thu May 23, 2013 11:12 pm
by face_off
I have refreshed the installer at the top of this thread. Pls re-download and install to fix the following....

1.14a5
- Fixed issue where importing material collections was crashing Poser
- Fixed issue where pasting nodes was causing a python exception
- Fixed issue where double-clicking a "non-item" in the LiveDB would raise a python exception
- Fixed issue where pasting a floattexture was not copying the texture value
- Fixed issue where pasting a material was raising a python exception

It doesn't seem to activate them in real time. The only way I can seem to activate them is close to viewports
And reload the window.
I wonder if it. This is possible to do in real time when we press apply. As this would make quite a few advantages

Chopper - are you clicking the "Apply" button after ticking/un-ticking the "Active" checkbox?

When I refresh the Octane scene from Poser, the materials in the Octane Scene are all screwed up

Deane, what does "refresh the Octane scene from Poser" mean? What button/menu item are you using to do this?

"the materials in the Octane Scene are all screwed up" - not sure what you mean by this? Can you provide a screenshot pls?

Paul

Re: OctaneRender® for Poser beta WINDOWS - build 1.14a [TEST

PostPosted: Fri May 24, 2013 12:20 am
by ch0pper
The multiple graphics card bug.

. It's definitely a bug, it only seems to let me select my first graphics card.

even if I press on the apply, does not select the graphics card and utilise them

Even when I close than the viewport and tick all three graphics cards. boxes

It seems to default back to my first graphics card.

Basically, it's working on the first graphics card .

Not the other 2.

I could in previous versions use all three graphics cards

Basically , I've used the GPU monitoring programme . The first graphic card is it 99% whilst rendering

the other 2 cards even though the boxes are ticked stay at zero , so there's absolutely no load on never two cards

Even though the boxes are applied and ticked