OctaneRender® for Poser beta WIN - build 1.17a [STABLE]

[face_off]

One screen-shot coming up

The plugin is pickup up the AngelStrandBum.jpg texturemap as the specular map, and plugging it into the specular pin, which is what you would expect. But the specular map is very bright, so the specular is overpowering the diffuse. Setting "index" to 1.3 will probably fix it, or reduce the image power. It's only be recently that bringing across the specular map from the Poser material was added, and I haven't had much feedback to tune it yet, so if you have some consistent index or power settings, I can add them to the plugin.

I deleted the "OctaneDefaults.py" by mistake, so of course Poser should give me an error when starting Poser. But I got a whole bunch of errors. Is this triggered from The Octane for Poser plugin or is this a general PoserPro 2014 error ?

With no OctaneDefaults.py file, a python exception is raised when Poser initialises all the plugins, and Poser does not handle this correctly and it looks like it stops loading critical libraries that Reality needs - resulting in the error you are getting.

Paul

[Zay]

Setting "index" to 1.3 will probably fix it, or reduce the image power.

Yes, I can change it manually but should not be the way to go. Can you add it to the "forced" specular settings in the config?

With no OctaneDefaults.py file, a python exception is raised when Poser initialises all the plugins, and Poser does not handle this correctly and it looks like it stops loading critical libraries that Reality needs - resulting in the error you are getting.

Will put a ticket in at Smith Micro as I have seen some weird errors in PP2014, but don't know which addon it's coming from.

[face_off]

Yes, I can change it manually but should not be the way to go. Can you add it to the "forced" specular settings in the config?

Issues like this are a no win situation for me. Users want the plugin to automatically bring across the Poser specular map, and when I add this functionality, someone raises it as a bug

Originally the "index" pin was 0-1, and now it is 1-8. So the skin shader plus a lot of your saved POE files assume index = 0. An index of 0 is the same as the "new" index = 8. The default "new" index is 1.3. So the values in the "specular" pin assume a "new" index of 8 (and are therefore very small). So it is not just a change to force the default "index", since doing so will adversely effect the default skin shader. The default skin shader also needs to be changed at the same time. I looked at doing this last week, and after tweaking settings and not getting results as good as the current skin shader, etc decided "if it"s not broke, don"t touch it!"

I think a good solution is to add a "Convert specular maps from Poser" checkbox in the configuration. You can untick it, and you'll get the old behavior.

Paul

[Zay]

An index of 0 is the same as the "new" index = 8.
I think a good solution is to add a "Convert specular maps from Poser" checkbox in the configuration. You can untick it, and you'll get the old behavior.

Actually it was the power of the specular I was thinking of. Exactly like it was before when forcing it to 0.05 from the config file. If an option to convert the map can do that, then I'm all for it.

[face_off]

Actually it was the power of the specular I was thinking of. Exactly like it was before when forcing it to 0.05 from the config file. If an option to convert the map can do that, then I'm all for it.

If you deselect "Convert Specular Maps" in the Config, it will use the glossy power you have setup in the OctaneDefault.py file - so hopefully that will do the trick for you.

[Zay]

OK, that sounds great

[face_off]

Hi

Just letting people know that release 1.20 of the plugin is ready to go, however there are some contingencies on PoserPro2014 SR2 which I need to see the outcome of prior to posting the build. Apologies for the delay, but it should be worth it! Hopefully only a day or two away.....

Paul

[ch0pper]

is SR2 out now then?

[face_off]

is SR2 out now then?

No, not yet.

[Witpapier]

Is it going to fix the SUB D issue?