OctaneRender® for Poser (Windows) - build 1.20.2 [OBSOLETE]

[face_off]

I just saved a render target real quick and it appears it only saves the data from the rendertarget tree (which makes sense). So unless it's hidden in some fancy way, it does not save material setups

When you Poser -> File -> Save, ALL the Octane information (rendertarget and materials) get saved to the pz3 file. When you File -> Open, they will all be reloaded. If this is not happening, then either you are opening the pz3 by doubleclicking the file icon in Explorer (which the FAQ and Manual both indicate will not work), or your python installation is corrupt, and you should be able to fix this by reinstalling the latest Poser 2014 SR.

Paul

[Pandarr]

Goal for today... read manual. Sorry about that!

[Zay]

Sometimes when I set a custom render target - delete the scene objects - open a new scene and wants to change the render target again I get this looping error.

Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\ViewportForm.py", line 782, in on_timer
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\ViewportForm.py", line 547, in processUpdatedImage
File "D:\Poser Pro 2014\Runtime\Python\lib\site-packages\wx-2.9.1-msw\wx\_gdi.py", line 823, in CopyFromBuffer
return _gdi_.Bitmap_CopyFromBuffer(*args, **kwargs)
ValueError: Invalid data buffer size.

I have to close the plugin and start it again to fix it.

[face_off]

Hi Zay

I know there is a minor issue where if you start a new Poser scene after rendering with the plugin, the previous rendertarget and materials are used (they are not cleared and re-created). I suspect that is causing the issue you are getting. I am planning an update when Octane 1.5 is released, so I will make sure this is fixed in that release.

Paul

[denver2]

Why after installing the update (build 1.20.2 )dynamic hair render so bad as before? Why nothing has changed? (my step - i deinstal old version plugin, and instal new version, but render not change)

[face_off]

Why after installing the update (build 1.20.2 )dynamic hair render so bad as before? Why nothing has changed?

I have not made any change to improving dynamic hair - so it renders as if always has. Improving the rendering of dynamic hair is on the top of my enhancement list, but it is quite complex because the Poser strand hair (which is a vertex stands) needs to be converted to polygons. I have the code written, but it is not working to the high standard the is needed, so it's on hold for the moment, but I will get back to it t some point.

Paul

[denver2]

Thank you, Paul! I hope you find a solution. Because if in octane will not function dynamic hair, plugin is useless for 80 percent. program Poser is designed to work with the characters - people and animals. These characters are nonsensical without hair. And your plugin does not work fully with the hair. I hope for a speedy decision. thank you

[face_off]

Thank you, Paul! I hope you find a solution. Because if in octane will not function dynamic hair, plugin is useless for 80 percent. program Poser is designed to work with the characters - people and animals. These characters are nonsensical without hair. And your plugin does not work fully with the hair. I hope for a speedy decision. thank you

You are actually the first person who has said dynamic hair is a necessity. Polygon/transmapped hair for human figures produces superior results to dynamic hair - and is fully supported by the plugin. As for animals - none of the Poser or Daz animal figures (that I am aware of) use dynamic hair, so you shouldn't have a problem there.

Paul

[face_off]

Sometimes when I set a custom render target - delete the scene objects - open a new scene and wants to change the render target again I get this looping error.

Hi Zay - I had a look at this but could not reproduce it. What exactly do you mean by "set a custom render target"? Also, when you open a new scene, the Setup window and viewport should close - is that not happening for you? Is the looping error happening when you open the Setup window or the Viewport?

Thanks

Paul

[face_off]

I have updated the installers at the top of this thread with the following:

1.20.2.2
- When changing a node type to "image", "floatimage" or "alphaimage", the select file dialog is immediately displayed
- Fixed issue where the "mix"-"amount" pin was incorrectly set if it was an image/floatimage/alphaimage when pasting to all skin materials
- Figures and Props that are made invisible are now still shown in the Materials tab of the plugin, so Octane materials setup for these figures/props will no longer be lost
- Added Materials menu item "Reload All Texturemaps" to reload the texturemaps for all image, floatimage and alphaimage nodes from file
- The plugin will now convert Poser gradient bump maps to the Octane "normal" pin IF the Poser material gradient mode is Normal Map. The normal power is always set to 1

The above changes required some big changes to the code, so exercise the usual caution associated with "Test" releases.

Paul