Page 2 of 9

Re: OctaneRender® for Poser beta WIN - build 1.20a [TEST]

Posted: Wed Jul 10, 2013 12:08 pm
by face_off
I have updated the installer at the top of this thread with:

1.20a2
- Viewport Material picker now activates the Material tab in the Setup window
- Fixed error with special characters in filenames being saved to the Poser Material
- New configuration option to set materials with transparency = 1 and no transmap to diffuse with opacity 0 rather than a specular material

Paul

Re: OctaneRender® for Poser beta WIN - build 1.20a [TEST]

Posted: Wed Jul 10, 2013 1:56 pm
by mlru
face_off wrote:
I get this error when trying to load that prop. I worked with it before and saved it with Octane materials exported back into Poser. trying to load it fresh ends with this messages:
Hi Uwe

That error is actually coming from special characters in the image map of the Octane node setup for one of the materials. I will fix this in the next day or so.

Paul
Thanks, Paul! :)
Was this something I have an influence on (e.g. weird filenames or the like) or internal?
Though I don't remember using any unusual names...

Re: OctaneRender® for Poser beta WIN - build 1.20a [TEST]

Posted: Thu Jul 11, 2013 12:02 am
by face_off
Hi Uwe - it was a special character (non-ANSII) in the Octane image, alphaimage or floatimage node.

Paul

Re: OctaneRender® for Poser beta WIN - build 1.20a [TEST]

Posted: Thu Jul 11, 2013 11:07 am
by mlru
face_off wrote:Hi Uwe - it was a special character (non-ANSII) in the Octane image, alphaimage or floatimage node.

Paul
Ah, OK. wonder how that got there...

Re: OctaneRender® for Poser beta WIN - build 1.20a [TEST]

Posted: Thu Jul 11, 2013 4:23 pm
by Erick
Is it just me, or is it the way it is now, with the linearity change of the RGBSpectrum, that when I set the value(s) to 255 (pure white) and hit OK, it changes itself back to 254/254/254, hehe ... ???

Re: OctaneRender® for Poser beta WIN - build 1.20a [TEST]

Posted: Thu Jul 11, 2013 11:54 pm
by face_off
Is it just me, or is it the way it is now, with the linearity change of the RGBSpectrum, that when I set the value(s) to 255 (pure white) and hit OK, it changes itself back to 254/254/254
Yes - there is a python rounding error happening. I'll try to fix this in the next version.

Paul

Re: OctaneRender® for Poser beta WIN - build 1.20a [TEST]

Posted: Sat Jul 13, 2013 4:55 am
by KleanZlate
face_off wrote:T
- Added support for subdivided figures. Only available on Poser build 25276 onwards. Refresh times are much longer for subd'd figures, so remember to turn off Auto-refresh. Subdivided props are not yet supported.
Any idea when Poser will be updated to build 25276?

Re: OctaneRender® for Poser beta WIN - build 1.20a [TEST]

Posted: Sat Jul 13, 2013 8:17 am
by face_off
Any idea when Poser will be updated to build 25276?
I'm sorry, I don't know.

Re: OctaneRender® for Poser beta WIN - build 1.20a [TEST]

Posted: Mon Jul 15, 2013 2:14 am
by Ken1171
In the last couple of updates I noticed the plugin is no longer catching some of my default settings from the OctaneDefaults.py file, such as DEFAULT_RESOLUTION_WIDTH, DEFAULT_RESOLUTION_HEIGHT, and DEFAULT_MAXSAMPLES. The plugin just ignores my settings and goes to its own default values.

On the OctaneDefaults.py default skin materials, it claims that they MUST be lowercase, but HiveWire3D's new Dawn figure has material names capitalized. I have changed them to lowercase in the "SkinMaterials" section, and I am hoping this won't become an issue.

The plugin also seems to default to IBL light, even if I start the plugin from a Poser scene with a single directional light (no IBL). I thought the plugin was supposed to get the lighting model from the Poser scene, right? Or would it always start as IBL?

I am using the latest Poser Pro 2014 build 10.0.1.25099, so I am assuming the subdivision support in this plugin version will NOT work since the Poser version that is required (build 25276) still hasn't been released to the public, right?

Lastly, do I have to go through all objects in my scene in the material settings and save them 1-by-1 as "Poser materials" or would the plugin do this automatically if I close it?

Re: OctaneRender® for Poser beta WIN - build 1.20a [TEST]

Posted: Mon Jul 15, 2013 3:34 am
by face_off
In the last couple of updates I noticed the plugin is no longer catching some of my default settings from the OctaneDefaults.py file, such as DEFAULT_RESOLUTION_WIDTH, DEFAULT_RESOLUTION_HEIGHT, and DEFAULT_MAXSAMPLES. The plugin just ignores my settings and goes to its own default values.
There was a big update a while back to change the rendertarget defaults. Now you just rightclick the rendertarget tree and "Save as Default". http://render.otoy.com/forum/viewtopic.php?f=45&t=32641.
On the OctaneDefaults.py default skin materials, it claims that they MUST be lowercase, but HiveWire3D's new Dawn figure has material names capitalized. I have changed them to lowercase in the "SkinMaterials" section, and I am hoping this won't become an issue.
That's fine - the figure doesn't need lowercase material names - just the entry in OctaneDefaults.py needs lower case.
The plugin also seems to default to IBL light, even if I start the plugin from a Poser scene with a single directional light (no IBL). I thought the plugin was supposed to get the lighting model from the Poser scene, right? Or would it always start as IBL?
Again, the introduction of "Import/Export Rendertarget" does away with all this - just set either IBL or daylight as your default, and if you want to change it, Import a previously setup IBL rendertarget.
I am using the latest Poser Pro 2014 build 10.0.1.25099, so I am assuming the subdivision support in this plugin version will NOT work since the Poser version that is required (build 25276) still hasn't been released to the public, right?
Correct.
Lastly, do I have to go through all objects in my scene in the material settings and save them 1-by-1 as "Poser materials" or would the plugin do this automatically if I close it?
When you save the Poser pz3 file, any Ocane settings for that scene will be saved too, and reloaded when you reload that scene.

Paul