OTOY Forums

Hi Guys,
Please see attached pdf and image below.

Workflow issues aside, we have an unreliable visibility toggle.
With the same settings, I have 3 results shown in the attached .pdf.

For a given object, toggleing visibility OFF :
Preview is correct
Still image is correct
Animation is wrong.

But wait, there's more. If I start the animation on the errant frame. I can get a correct result. But, this is no way to get through a render with objects appearing and disappearing.

Please see if this can be fixed. Yes, there are work arounds. Not crazy about them.

Separately, it would be really helpful to have the Preview visibility settings strictly match the Render settings. That is, the Octane Camera Visibility setting would be reflected in the Preview window.

----------------------------------------------------------------
Following an overnight render in which I have an object completely pulled out of view once its visibility is reduced through General Visibility within Octane properties from 100 to 0,
you will see that a ghost remains.
The object, is off the stage, yet still rendered as a ghost for the next 400 frames. Running out of work arounds here. Please let me know if I am doing something wrong here.

Thank you for your help,
Rick

Win10pro
dual xeon
32g
4 GPU- titan x2, 1080, 970
nvidia 4.17.17

Continued....
This again shows the inconsistency between render preview and render. In this case, the indicated flecks were opacity channel controlled.
They are supposed to be gone. I have re-rendered with the correct results.....but I am confused as to why.

Is there some scenario in which having a render preview not match outcome is an advantage? Totally screws up workflow from where I stand.
Losing a ton of time.

Some help please?

Hello protovu,

Thanks for your report. I will look into it.
Btw, could you please set the mesh type("Data-Octane properties-Mesh type") of the "ivbubble" as "Reshapable" and try again? Thanks.

Cheers,
DrawFun

Thanks for looking at this, Drawfun.

Sorry for being a dolt.

I Cannot find what you are referring to : ("Data-Octane properties-Mesh type") of the "ivbubble" as "Reshapable" )

Octane Properties, yes? But, nothing about Data, other than Geometry Data....

[quote="protovu"]I Cannot find what you are referring to : ("Data-Octane properties-Mesh type") of the "ivbubble" as "Reshapable" )

Thank you for the precise location, Drawfun.

The "reshapable proxy" selection did properly allow for the visibility OFF for the bubble.

The "reshapable proxy for the IVbag did not work.
Other than being a more complicated model with multiple shaders, the IVbag employs a fade out through "General Visiblity" just prior to toggling OFF "Camera visibility".

I am looking at the BlenderOctane manual on mesh types.

Hi DF,
Not sure if this is helpful information.....in addition to OctaneBlender, I use Octane Carrara.

In it, I am able to use General Visibility for fade outs with complex models with multiple shaders. No ghosting.

Additionally, the Carrara native visibility toggle functions predictably, perfectly matching the preview.

Thanks

protovu wrote:Hi DF,
Not sure if this is helpful information.....in addition to OctaneBlender, I use Octane Carrara.

In it, I am able to use General Visibility for fade outs with complex models with multiple shaders. No ghosting.

Additionally, the Carrara native visibility toggle functions predictably, perfectly matching the preview.

Thanks

Hi!

It would be nice if you could share a Blender scene (possibly some very basic content showing the issue).

I've tried to reproduce it but it looks like it's working fine here.

Thanks!

Hi Lino,
Thank you for looking at this.

Please see attached Zip file.
Within the zip:
A .blend file that has a disc shape which is supposed to Not Render from frame 196 onward.
and...
In the few rendered frames that I have included, you will see that it does, in fact render at frame 196, even though all available render disables are keyframed (Octane properties, Outliner ), and I am further tricked by the Preview Render, which behaves correctly regarding keyframed visibility.

This problem has been going on since my first Octane Blender use, starting with my August 2018 subscription.

In my work, I have models swapping in and out often. Yes, there are work arounds, but not great ones.

One clue: If I start the render on frame 196, the model visibility behaves correctly.

Win10
dual xeon
32g
4nvidia cards 2xTitan, 1080,970
driver 4.17

Anything happening on this bug?

Has anyone been able to reproduce the problem with the file I provided?