OTOY Forums

TRRazor wrote:

With All Medium node of the Specular Material set to the same value it appears ok:

This is definitely not an OCDS plug-in-issue.
It's like that in every version of Octane, since you control light / transmission absorption with those medium nodes.
Setting these to individual values, on a character consisting out of more than 20 materials (Genesis2) is bound to give these errors.

Not a bug, hence doesn't need to be fixed.

rajib wrote:

TRRazor wrote:

With All Medium node of the Specular Material set to the same value it appears ok:

This is definitely not an OCDS plug-in-issue.
It's like that in every version of Octane, since you control light / transmission absorption with those medium nodes.
Setting these to individual values, on a character consisting out of more than 20 materials (Genesis2) is bound to give these errors.

Not a bug, hence doesn't need to be fixed.

TRRazor,

I don't think I agree with that for a simple reason - hidden geometry should not be having an effect on the surface underneath it. The whole point of it being hidden is that it should not impact what is underneath it no matter what material is being used on the underneath surface. It might have been like this since version 1 f Octane, but to me it is still a bug.

01 Unwanted UI interactions between DAZ Studio and the OctaneRender plugin

03 Network rendering

05 Final Render Button
you let a render run not realizing the save button was disabled

07 Instant Crash when adding keyframe to White Point Element

09 Exporting Animated Cameras to standalone Only still cameras seem to be exported from OcDS to OR standalone

15 A button to resize all textures in the texture tab. It would be a real time save for us who render smallish images on smaller cards, instead of having to click each individual texture. A "Default texture size" drop down in Preferences/texture settings would also work

17 Add Out of Core support to network render Slave nodes

22 textures not updating correctly when rendering animation

26 Opacity Maps cause dark layers on objects under the hidden geometry

face_off wrote:

could it maybe have something to do with Spectralis' problem with animations reloading incorrect materials? If it's not getting rid of info, that could certainly lead to issues where it's referencing things it shouldn't be keeping any more on accident, I would think.

I doubt it. I would need to see Spectralis' scene in order to speculate the cause of the issue.

Paul

I will try to send you this scene although it contains content I purchased so not sure if I can send it with content?

What probably was meant is:

Yes this is a bug.
But this bug cannot be fixed by face_off just for the OcDS plugin.
The OctaneRender standalone development team needs to address this in the standalone version / the SDK so ALL plugins do not anymore show this issue.
The question then is: Is the standalone development team aware of all the different issues with transparency maps?
For example use a hair with transparency and place it in a fog volume and you will notice that the volume is completely stopped by the geometry and "not entering" trough the transparencies...
In the issue you describe something similar seems to happen: Some rays seem to be blocked by the geometry or bounced back and not fully entering trough the areas with transparency...
OctaneRender 3 may solve those issues. Guess we need to have another look at this after the OR3 beta release and then post a bug report in the OctaneRender 3 standalone beta threads.

face_off wrote:I just posted 2.24.2.2 at viewtopic.php?f=44&t=51410&p=255739#p255739. With this version I am unable to reproduce the following...

01 Unwanted UI interactions between DAZ Studio and the OctaneRender plugin
05 Final Render Button
07 Instant Crash when adding keyframe to White Point Element
22 textures not updating correctly when rendering animation

Are the people who reported these issues able to retest them with 2.24.2.2 pls.

Thanks

Paul