OcDS: High Priority Issues and Request - State 2.23

[rajib]

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.

[linvanchene]

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.

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]

01 Unwanted UI interactions between DAZ Studio and the OctaneRender plugin

I cannot reproduce this on the next release (2.24.2.2) - but I could reproduce it on the previous version. So /may/ be fixed.

03 Network rendering

Will be resolved in the next release - 2.24.2.2.

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

I could not reproduce this on 2.24.2.2.

07 Instant Crash when adding keyframe to White Point Element

Fixed in 2.24.2.2.

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

This should be fixed in the current 2.24.2.1 release if you export to ABC.

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

May I suggest enabling Out-of-core textures instead.

17 Add Out of Core support to network render Slave nodes

This is resolved in the current release 2.24.2.1 - where you manually setup the slaves.

22 textures not updating correctly when rendering animation

I fixed a major issue related to texturemap name setting in the next release 2.24.2.2 - so pls re-check this issue then.

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

This is a general Octane issue - and does not appear to be related to the plugin - so suggest removing it from this list and pursuing a resolutions via the Octane Standalone 2.24.2 thread.

Paul

[linvanchene]

Update / Edit 2015 - 11 - 24:
- added status to the issues on the first page
green = issue considered solved by face_off
orange = issue partially solved or needs to be checked again in the next build

- - -

Face_off has allready fixed the first issues and is working his way trough the list.
Therefore the original purpose of the poll to give some feedback where to start has run its course.

The final results as of Midnight 2015 - 11 - 24 are:

Thank you all for participating and helping out providing feedback!
- - -

[Spectralis]

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?

[face_off]

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

Hold off until you re-test with 2.24.2.2. I found an issue that might explain the problem.

Paul

[TRRazor]

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.

This.

[face_off]

Quick update on the progress of fixes for this list......whilst assessing some of these issues I've found some deeper issues which are probably causing memory issues and potentially crashes. Resolving these is taking much longer than expected, since they are not trivial problems to fix, but they need to be done before rectifying the items on this list. Hopefully all the internal fixes will be done in the next 48hrs and I can get back to the more visible issues.

Paul

[face_off]

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

[Spectralis]

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

Great! I will test this on the scenes where I had rendering problems this evening. I know exactly which projects and which frames were causing problems so it should be easy to test and report back.