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

[face_off]

Hi Everyone. I have resolved all the above issues and testing now. New version should be available in the next 2hrs.

Paul

[morphious2013]

OK, cool. Thanks Chopper.

[face_off]

I have refreshed the installer. Pls re-downlaod from the link at the top of this thread and install.

1.16a3
- Fixed issue where installer was adding "Poser Pro 2014" to a selected path after using the Select Directory button
- If the Refresh button is pressed while rendering is paused, the Pause/Resume buttons are now correctly enabled/disabled
- Resolved issue where Genesis sub2 mesh was not rendering (resolves remapped V5 to V4 figure rendering too)
- Materials for a figure/prop are now sorted in the Material Tab.
- NOTE: Because the scene geometry is now not loaded until the Viewport is opening, it is not possible for the plugin to determine if the "Preview" material is used by geoemetry or not so it will always appear for a figure/prop.
- "Replace [type] node to all skin materials" now correctly retains the existing texturemaps
- Resolved issue where default material attributes from the OctaneDefaults.py file where not being applied when converting Poser materials to Octane materials

grainy until about 200 -300 samples.

Increasing "kernel"->"caustic_blur" to 1 can reduce graininess substantially for some scenes. Depends on the lighting...

A render Queue would be nice, so I don't have to open each poser scene manually.

This has been suggested before and is a good idea. The other idea put forward by Zay was the ability to start rendering then open another scene and have the render continue. I'll look at the viability of these options once 1.16a is stable.

EDIT: Paul, have you disabled the OctaneDefaults.py totally? If yes, why?

The original 1.14a release notes detail the OctaneDefault.py parameters that are no longer used. http://render.otoy.com/forum/viewtopic.php?f=45&t=32641. Those parameters are now stored in the config.xml file, and can be editing manually, or via the Setup button or are just "remembered" values. The OctaneDefault.py file was stopping me being able to package the plugin in an installer. Having an installer is critical to removing my own packaging errors (since it's an automated script), and for reducing user install errors. The current installer only copy OctaneDefaults.py if it doesn't already exist (so it doesn't overwrite the existing copy). Any new parameters added to the plugin will go in config.xml.

The installer adds the \Poser Pro 2014 string automatically.

I had never noticed this, and was a problem in the Revit and ArchiCAD installers too. Fixed now.

Paul

[KleanZlate]

Thanks Paul. Great to have the subdivision working again

[Witpapier]

Thanx for the effort Paul. I see its working now I am so happy now. Thanx.

[Zay]

The original 1.14a release notes detail the OctaneDefault.py parameters that are no longer used.

I read that. But i'm confused. So some settings are read from the OctaneDefault.py while others are not? I found the XML file, but the setup window only shows 4 setttings of those.
I tried to change the kernel settings in the plugin but they didn't get saved. Nothing in the XML file. I'm really confused.

[face_off]

Thanx for the effort Paul. tell me, Is it possible to fix this issue Im having that I explained previously regarding the bump settings when i import a material for v4?

I need to look into this more closely. Was just trying to fix the obvious bugs first. I will look at this in the next 24hrs.

I read that. But i'm confused. So some settings are read from the OctaneDefault.py while others are not? I found the XML file, but the setup window only shows 4 setttings of those. I tried to change the kernel settings in the plugin but they didn't get saved. Nothing in the XML file. I'm really confused.

Parameters like the "skin materials list" will stay in the OctaneDefaults.py file. Whereas more dynamic parameters like the setup window position, refresh rate etc are better suited to the config.xml file. You should never need to edit the config.xml file - it should be "invisible" the to the user. Whereas you might want the edit the OctaneDefaults.py file is you need to add another defined resolution size (for example).

Your default rendertarget settings (like kernel, etc) are all now setable - so just set them in the plugin Settings tab tree, then rightlclick and "Save as Default". Then when you next load a fresh Poser scene, those defaults will be used. Alternately, if you have a favorite setup for Final rendering, export that rendertarget, calling is "Final Render settings", and import it when you next need it. You can even import rendertarget settings whilst rendering, and the Viewport will immediately reflect the new settings. You can setting IBL image rendertargets with the correct power settings, etc and export them, so you just import them the next time you want to use them, rather than having to reload the IBL image and set the correct power.

I hope that makes sense - it's the way it should have been from the start, but easy to say in hindsight.

Paul

[Witpapier]

I realize how this works, When i load a V4 figure and i open octane I first have to choose remove bump maps from this prop /figure. then when I import my custom material the bump strengths and settings stay as I intended them. , Only thing tho is that, the bump image itself is that of the original character it was saved with. Paul is it possible to change the settings to a default setting that automatically change the bump strengths upon converting the poser image to octane. Or maybe Something like a bump strenth window that lets you change the settings for each skin material( for instance, i change the settings of SkintorsoB and automatically every skin material that uses it has the settings I set for that material, instead of me going to nipple and changing it, Torso and changing it, and so on. I could even work for Diffuse and glossy sets.) Im just thinking of ways to improve on a already great plugin.

[Zay]

then rightlclick and "Save as Default"

Aha! Missed the "Save As Default" Thanks Paul!

And just so nobody else doesn't get confused about what to edit in the OctaneDefault.py, could you please remove the lines that has no effect to edit anymore?

[morphious2013]

I'm still new at this, but what reasons that I am not aware of, that I would need to change the OctaneDefault.py file? Are there advantages to changing the parameters in this file? Thanks.