OctaneRender® for Poser beta WIN - build 1.16a [OBSOLETE] Tweet

[mlru]

Found a vestige from the charset problem:
Changing an image and select it from the [Octane Image Files] list brings up this error:

Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\Node.py", line 1155, in <lambda>
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\Node.py", line 1857, in EventNodeChanged
TypeError: descriptor 'rfind' requires a 'unicode' object but received a 'str'

The other lists do work.
Uwe

[mlru]

And another one.
Happend after I added a prop and used the morphing tool in PP2014 on a V3, not sure, what's the cause:

Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\__init__.py", line 72, in Render
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 3542, in ShowSetupForm
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\Configuration.py", line 131, in LoadSettings
File "D:\Programme\CGI\Poser\Poser Pro 2014\Runtime\Python\lib\xml\etree\ElementTree.py", line 1177, in parse
tree.parse(source, parser)
File "D:\Programme\CGI\Poser\Poser Pro 2014\Runtime\Python\lib\xml\etree\ElementTree.py", line 653, in parse
parser.feed(data)
File "D:\Programme\CGI\Poser\Poser Pro 2014\Runtime\Python\lib\xml\etree\ElementTree.py", line 1624, in feed
self._raiseerror(v)
File "D:\Programme\CGI\Poser\Poser Pro 2014\Runtime\Python\lib\xml\etree\ElementTree.py", line 1488, in _raiseerror
raise err
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 1, column 163

edit: OK, and now I get this error everytime I try to open the plugin, no matter what's in the scene. It's broken.

[face_off]

edit: OK, and now I get this error everytime I try to open the plugin, no matter what's in the scene. It's broken.

Uwe - the config.xml file has become corrupt. Can you pls send me a copy of it (in C:\Users\[username]\AppData\Roaming\Poser Pro\10) and then delete it. You should then be able to run the plugin. I will also change the plugin to handle this situation better.

Found a vestige from the charset problem:
Changing an image and select it from the [Octane Image Files] list brings up this error:

I will fix this in the next release.

Paul

[RGUS]

Just a silly little request....
Can we have the focus returned to the node edit cell when for instance one picks 'gamma' say the focus of the dialogue box automatically goes to the edit cell so we can start entering numbers without having to first pick that cell... did that make sense... hmmmmm

[face_off]

Can we have the focus returned to the node edit cell when for instance one picks 'gamma' say the focus of the dialogue box automatically goes to the edit cell so we can start entering numbers without having to first pick that cell... did that make sense... hmmmmm

Do you mean when you focus pick? This was in an early version, but I pulled it out because having the keyboard focus change from the Viewport to the Setup window when you focus picked meant the tree position moved, and this got quite confusing. Also, focus picking and then the plugin automatically selecting the focus "number" edit box would mean if you mousewheel scrolled, the focus would change and that would be unexpected, since intuitively you would think that the Viewport still had the focus. Hope that makes sense....

Paul

[RGUS]

Yeah... like in the earlier versions... I wasn't confused by it... now when the rendering is going on, changing a setting on the fly takes ages to highlight the value you want change and the numbers take ages to change what you typed. The only way around this is to pause the rendering, make the change and start the rendering again.

[face_off]

now when the rendering is going on, changing a setting on the fly takes ages to highlight the value you want change and the numbers take ages to change what you typed. The only way around this is to pause the rendering, make the change and start the rendering again.

Are you running a separate card for your Windows adapter? If not, are you running "Low Priority" in the Cuda Devices tab?

[RGUS]

Yes separate adapter and yes nvidia card set to high... I think I need a titan... if that's the best card, I can't seem to find out definitively what the best card is for still image Octane rendering.

[face_off]

Yes separate adapter and yes nvidia card set to high

I'm not able to reproduce the GUI performance issue you are experiencing. Is it only on big scenes? If I do anything on the plugin Setup window whilst rendering, I pretty much get an instant response.

Paul

[RGUS]

27" LCD 2560x1440 resolution 60Hz 32bit colour DVI interface