OTOY Forums

face_off wrote:

The "OctaneRender: ShadowVisiblity" button, under the Parameters tab, toggles shadows ON/OFF for Daylight Environments and Mesh Lights, but not for HDR Texture Environments. Is this working as intended?

This functionality is not working. I will see if I can fix it.

Paul

In general the Shadow Visibility button in the DAZ STUDIO paramters tab is sometimes working and sometimes not even when using the same environment.

To experiment:

- place a plane into the scene
- add a cube
- select cube in the scene tab
- go to parameters tab
- try to toggle shadow visibility off
- do some random things
- try to toggle shadow visibility off

- - -

Also tested: I was able to have Shadow Visibility OFF work together with an HDR environment.

In general the Shadow Visibility button in the DAZ STUDIO paramters tab is sometimes working and sometimes not even when using the same environment.

This is fixed in the next release (2.24.2.3).

Paul

Installed it and found a very big issue...

I've set up a scene with Genesis 3 and added some hair... (Fraser hait for M3 which will work on G3 also)
Started the octane plugin... The hair rendered without any transmaps (I don't know if this happens all the time and maybe it a problem with the hair-file itself)
G3 rendered correctly.
But then I changed the materials settings in DAZ and rendered again: G3 witout her eyes and also the arms are missing...
Tried that several times with different settings - no changes. Original texture rendes fine but after a change - bag - I get a kind of "crippled" Genesis 3.
Tested this also with the redspec-tgx-shaders - same problem.
I hope it's possible to install the old version again.

Edit/added: I've saved the scene, closed DAZ, deleted all temporary files and started DAZ again, loaded the scene and started renederin using the plugin:
All I can see now is the HAIR but no GENESIS 3. Checked the visabilty settings - should be ok.
So I've deinstalled the new version of the plugin, re-installed the old one, opened the scene again. G3 won't be rendered although I can see her in tha DAZ-viewport. :-/

Could you post a screenshot of the "crippled" G3?

I have refreshed the installer at the top of this thread with:

2.24.2.3
- Added Network Render Status indicator in the System Tab -> Processed Data group box
- Added additional material conversion rules for Iray Materials - Opacity Cutout's are now picked up as opacty maps, and if there is a Refraction Weight > 0.5, the Octane opacity will be (1 - Refraction Weight). This should allow for better conversion of transmapped and clear surfaces
- Fixed issue where the camera comboboxes in the Animation and System tabs where blank.
- Set the maximum Bump and Normal power to 1 (to resolve cases where the power would be converted to 2)
- Stopped a blank Image node being added to the Glossy material of skin materials when there was no normal map in the DS surface
- General Visibility and Shadow Visibility Properties now work for figures/actors. Pls let me know if this has an adverse effect elsewhere
- Mesh and figure/actor transforms are no longer applied to the Octane Viewport if "Live" is disabled. This may assist reducing lag in large scenes
- Iray Uber materials with an "SSS Amount" >= 0.3 will be converted to Octane Material Mix SSS materials. This should resolve the Iray skin surface conversion issues being experiences by users, but will however require significant testing by users to ensure it is working correctly for all materials

* RECOMMENDATION: Edit->Preferences->Interface->Display Optimization->set to BEST

Paul

niiice work

maybe possible to remove that stupid automatic enviroment setting save spam? or some kind of "clear all" button... or to put it on that list? its just annoying

maybe possible to remove that stupid automatic enviroment setting save spam? or some kind of "clear all" button... or to put it on that list? its just annoying

Unsure what you are referring it with this. Can you provide more details pls?

Paul

face_off wrote:

maybe possible to remove that stupid automatic enviroment setting save spam? or some kind of "clear all" button... or to put it on that list? its just annoying

Unsure what you are referring it with this. Can you provide more details pls?

Paul

When you merge .duf scenes by default all unused materials, render settings, and environment presets are added as well.

Especially for people who are creating comics or animations in the past this lead to countless duplicated presets that then all have to be manually deleted.

Instead of one "Default Render settings", "default HDR environment", "default daylight environment" they have xy duplicates in the pull down menus.
Maybe someone who has collected a lot of duplicates could post a screenshot?

Because of that people have asked in the past for a "Delete unused Environment presets" and "Delete unused Render settings" button.
This would work the same way as the right click option in the unused materials section "Delete unused materials".

- - -

Nevertheless it seems in the OcDS Preferences tab there are actually Scene Loading options:

- Don't load Render Settings
- Don't load Environments
- Don't load unused Materials
- Don't load Project Settings

Those options could in theory be used for the following workflow to remove unwanted settings when loading scenes:
To remove unwanted duplicate Environments, Render Settings and unused Materials

- place checkmarks in the “Scene Loading” section of the OcDS Preferences.
- load the scene you want to clear
- save the scene
- remove the checkmarks

- - -

Does this workflow do the trick for those having issues?

While looking at this I came up with a question of my own:

Anyone knows which exact values are not loaded when you select "Don't load Project Settings" ?

Side Note:
In general a remaining issue might be that t_3 stealthily added a lot of features in the "last beta" that people never actually detected.
There was always the promise that the new features would be explained in follow up posts but then in some cases that never happend.
Some people may have discovered some of those features but because they were never mentioned in forum posts a lot of them are rather unknown to the vast majority of users...

face_off wrote: 2.24.2.3
- Mesh and figure/actor transforms are no longer applied to the Octane Viewport if "Live" is disabled. This may assist reducing lag in large scenes

\o/ \o/ \o/

This has completely removed the lag i was experiencing moving objects in large scenes. Thank you very much.

Can I confirm the correct/best procedure to update the scene, when I'm done moving objects, is to re-enable "Live" and then click "Reload on Demand?"

This has completely removed the lag i was experiencing moving objects in large scenes.

Nice!

Can I confirm the correct/best procedure to update the scene, when I'm done moving objects, is to re-enable "Live" and then click "Reload on Demand?"

That is correct.

Paul