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
Visibility Toggle not working for animation
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
- Attachments
-
- visibility toggle.pdf
- (353.42 KiB) Downloaded 258 times
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?
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....
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" )
Win 10
3.7Ghz i9 10900k / 64GB
ASUS STRIX Z490-E
PSU: PowerSpec 850Wd
RTX 3090 Asus Tuff
Network rendering:
Win 10
4.2Ghz i7 7700k / 64GB
AsRock SuperCarrier
PSU: EVGA 1200w
RTX 3080 Ti EVGA Hybrid
RTX 3080 ASUS Tuff
GTX 1080ti SC Black (wc)
3.7Ghz i9 10900k / 64GB
ASUS STRIX Z490-E
PSU: PowerSpec 850Wd
RTX 3090 Asus Tuff
Network rendering:
Win 10
4.2Ghz i7 7700k / 64GB
AsRock SuperCarrier
PSU: EVGA 1200w
RTX 3080 Ti EVGA Hybrid
RTX 3080 ASUS Tuff
GTX 1080ti SC Black (wc)
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.
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
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
- linograndiotoy
- Posts: 1355
- Joined: Thu Feb 01, 2018 7:10 pm
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
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
- Attachments
-
- visbust.zip
- (31.59 MiB) Downloaded 173 times