OctaneRender® for Poser beta - build 1.02q [OBSOLETE]

[Zay]

Digging a bit deeper.

I downloaded TextPad as Notepad++ couldn't read more than a 200mb text file and my pz3 file was 280mb. And there I noticed the addon settings can get corrupt.

I found these 3 settings could have a negative value. That will crash the plugin - or in this case give the errors I got above. When I added a positive value for these 3 settings, everything loaded fine again.

"renderWindowHeight"
"renderWindowWidth"
"inputType": "int2resolution", "value": [436, -52]},

It seems that sometimes when streching the viewport up and down, lock, unlock and minimizing, the plugin can't remember the last viewport resolution. That also explains why I saw the viewport as just a bar on the desktop after loading a saved scene just before it crashed.

[face_off]

Hi Zay

Yes are right. It looks like if you shutdown the plugin WHILE the viewport is minimised, it saved the incorrect resolution to the pz3 file.

I will fix this. I have 3 or 4 other small changes, so will fix it in 1.02q and re-post - probably in a few days time.

Paul

[face_off]

Hi Everyone

I have uploaded an experimental version of the plugin, primarily for Zay and Wim to test some features they have requested (however anyone is welcome to try it at your own risk :

1.02q-3
- Fixed issue where the plugin crashes if there were more than 4Mil polys
- Tabbing to the second and third field in float2/3 and int2/3 nodes automatically selects the whole fields text (as happens with the first numeric field)
- Closing the plugin setup window whilst the viewport is minimised no longer corrupts the saved octane settings
- If the "no updates" button is active, setting a prop/figure to be instanced only does 1 scene refresh rather than 2.
- New OctaneDefaults parameter ANALYSE_POSER_MATERIAL_NODE, which if set to True (the default) means when converting materials from Poser to Octane, the plugin will pick up if an image has been scaled (and set the image scale in the Octane material), and will detect specular maps in the Poser material and plug those into the specular pin of the glossy material. NOTE: Setting this parameter to True INCREASES the time required to load the scene into Octane if materials are to be converted.

Zay, regarding the scene refreshes when setting up instances - I've removed half the refreshes, but unfortunately it is mandatory that a scene refresh occurs when switching a ndoe from "mesh" to "scatter", since a scatter node needs to be added to the node network to assign the transform.

Wim, the last point is as we have discussed many times. It doesn't include the conversion of the blend node (yet) - one step at a time . Pls email me your thoughts.

Download the experimental version of the plugin HERE

Paul

[Zay]

Thanks Paul.

Seems "Force Glossy" is broken. Can you confirm that?

While adding some of my settings to the OctaneDefault.py file I saw under SkinMaterials a comma is missing after "mouthinner".

Could you please add force fresnel (Index) so Force Glossy will actually show as glossy again. Otoy changed that a couple of versions ago and added the fresnel (Index) setting.

[face_off]

Seems "Force Glossy" is broken. Can you confirm that?

Did you set GLOSSY_DIFFUSE_RATIO to 0? Remember you need to reload the defaults by reloading a scene or restarting Poser.

While adding some of my settings to the OctaneDefault.py file I saw under SkinMaterials a comma is missing after "mouthinner".

Fixed. TY.

Could you please add force fresnel (Index) so Force Glossy will actually show as glossy again. Otoy changed that a couple of versions ago and added the fresnel (Index) setting.

It sets the default index to 1.3. Is that not the correct index? Does it need to be 0?

[Zay]

If I stretch the viewport to 400x300 and save the file, it will open in 648x491 when reloading the saved file.

[Zay]

Did you set GLOSSY_DIFFUSE_RATIO to 0? Remember you need to reload the defaults by reloading a scene or restarting Poser.

Yes it's set to 0

The values for roughness and specular doesn't get transfered. Some places the specular is just a color and not a value.

It sets the default index to 1.3. Is that not the correct index? Does it need to be 0?

I use 0.0 then it looks like the previous versions.

[Zay]

Might be a user error. I see roughness do change but specular is still a color. What determines what is a color or a floattexture when forcing the settings?

EDIT: Nevermind. Found out I had some props with material names like legs, head, skin and so on that matches the same names in the SkinMaterial list. After deleting the list everything seems to load as I want it to with specular as a value.

[face_off]

Might be a user error. I see roughness do change but specular is still a color. What determines what is a color or a floattexture when forcing the settings?

EDIT: Nevermind. Found out I had some props with material names like legs, head, skin and so on that matches the same names in the SkinMaterial list. After deleting the list everything seems to load as I want it to with specular as a value.

If it is a skin material, then the specular is a color (since skin specular is tinted blue). If it is not a skin material, the specular is a floattexture. It would be great if Poser had a flag to indicate a material was "skin", but alas we need to make do with the material name (which is generally a good indicator).

Just confirming the "index" pin - anything over 1 seems to break the glossy, so I'll put a default in the OctaneDefaults and set it to 0.

Paul

[face_off]

Zay - I will look at that resolution issue later today.

Could you please add force fresnel (Index) so Force Glossy will actually show as glossy again. Otoy changed that a couple of versions ago and added the fresnel (Index) setting.

I have spent some time investigating this issue. In summary, Octane now controls the amount of specular via the index pin, and the "specular" pin is used to control the color. I think this is definitely a good change, since at the moment we have RGB values for specular skin at RGB 8, 4, 2 - which is a tiny amount of specular - and difficult to fine tune. So 1.3 is to correct default value for "index" IF there is a high specular value. I will need to adjust the material conversion to cater for this (in effect the Poser specular_color can now be directly copied into the "specular" pin color).

I will need a day or so to get this change through.

Paul