Driver/Keyframes on object visibility do not update viewport #56635

New Issue

Antonio Vazquez · 2018-08-31T22:16:19+02:00

Antonio Vazquez commented

2018-08-31 22:16:19 +02:00

Blender 2.8 Windows 64 bits version 30/08/2018 20:49

If one objet visibility option is changed using a driver, the visibility only changes after save and reload.

To reproduce:

The attached file has 2 objects, a Cube and a Suzanne monkey. There is a driver attached to suzanne to hide/show and the driver is handled using a custom prop of Cube. I know this is not a common use, but I tried to make a file as simple as possible to reproduce the bug.

Open attached file
Select the cube and in properties change "hide" property value to 1.
Look at the outliner and verify hide property change in Suzanne.
In viewport the Suzanne object still remain visible.
Save and reload, the property now works.

I have tested the same driver hidden a collection and the problem is the same. Tested also in 2.79b and the drive hide/show suzanne without problems.

Driver_280.blend

Blender 2.8 Windows 64 bits version 30/08/2018 20:49 If one objet visibility option is changed using a driver, the visibility only changes after save and reload. To reproduce: The attached file has 2 objects, a Cube and a Suzanne monkey. There is a driver attached to suzanne to hide/show and the driver is handled using a custom prop of Cube. I know this is not a common use, but I tried to make a file as simple as possible to reproduce the bug. 1) Open attached file 2) Select the cube and in properties change "hide" property value to 1. 3) Look at the outliner and verify hide property change in Suzanne. 4) In viewport the Suzanne object still remain visible. 5) Save and reload, the property now works. I have tested the same driver hidden a collection and the problem is the same. Tested also in 2.79b and the drive hide/show suzanne without problems. [Driver_280.blend](https://archive.blender.org/developer/F4488445/Driver_280.blend) ![image.png](https://archive.blender.org/developer/F4488454/image.png) ![image.png](https://archive.blender.org/developer/F4488458/image.png)

Antonio Vazquez commented

2018-08-31 22:16:19 +02:00

Added subscriber: @antoniov

blender-admin commented

2018-08-31 22:16:19 +02:00

#61900 was marked as duplicate of this issue

blender-admin commented

2018-08-31 22:16:19 +02:00

#61395 was marked as duplicate of this issue

blender-admin commented

2018-08-31 22:16:19 +02:00

#61410 was marked as duplicate of this issue

blender-admin commented

2018-08-31 22:16:19 +02:00

#61348 was marked as duplicate of this issue

blender-admin commented

2018-08-31 22:16:19 +02:00

#61034 was marked as duplicate of this issue

blender-admin commented

2018-08-31 22:16:19 +02:00

#60937 was marked as duplicate of this issue

blender-admin commented

2018-08-31 22:16:19 +02:00

#58593 was marked as duplicate of this issue

blender-admin commented

2018-08-31 22:16:19 +02:00

#60642 was marked as duplicate of this issue

blender-admin commented

2018-08-31 22:16:19 +02:00

#58817 was marked as duplicate of this issue

blender-admin commented

2018-08-31 22:16:19 +02:00

#60521 was marked as duplicate of this issue

blender-admin commented

2018-08-31 22:16:19 +02:00

#60162 was marked as duplicate of this issue

blender-admin commented

2018-08-31 22:16:19 +02:00

#58187 was marked as duplicate of this issue

blender-admin commented

2018-08-31 22:16:19 +02:00

#60042 was marked as duplicate of this issue

blender-admin commented

2018-08-31 22:16:19 +02:00

#59639 was marked as duplicate of this issue

Bastien Montagne commented

2018-09-03 16:18:17 +02:00

Added subscribers: @Sergey, @mont29

Sergey Sharybin was assigned by Bastien Montagne

2018-09-03 16:18:17 +02:00

Bastien Montagne commented

2018-09-03 16:18:17 +02:00

Seems to be an update issue, clicking on the show/hide 'eye' icon, or on the render 'camera' one in the outliner fixes to visibility too, but clicking again on the viewport 'grid' one exhibits again the problem. As if driver eval was not updating things properly. not suer what exactly is the problem here, would suspect again some COW/depsgraph thingy, @Sergey?

Antonio Vazquez commented

2018-10-23 11:36:56 +02:00

Added subscriber: @lichtwerk

Antonio Vazquez commented

2018-10-23 11:36:56 +02:00

@lichtwerk I think this could be related to #56636

Could you take a look?

@lichtwerk I think this could be related to #56636 Could you take a look?

Brecht Van Lommel commented

2018-10-23 11:42:55 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2018-10-23 11:42:55 +02:00

This really is an issue for @Sergey to look at, it's a limitation regarding animation visibility in the dependency graph. We may not even support it in the first 2.80 release since it is quite complex to solve.

Antonio Vazquez commented

2018-10-23 12:32:53 +02:00

Thanks for the info!

Brecht Van Lommel commented

2018-12-19 23:54:39 +01:00

Added subscriber: @heini

Philipp Oeser commented

2019-01-02 09:55:19 +01:00

Added subscriber: @FrancescoArena

Philipp Oeser changed title from ~~Driver property does not update viewport~~ to Driver/Keyframes on object visibility do not update viewport

2019-01-02 09:57:17 +01:00

Philipp Oeser commented

2019-01-02 09:58:48 +01:00

Added subscribers: @The_art_of_spinjitsu_1_2_3, @1seby, @Picklejones, @clepsydrae, @MaferM, @JakubSteiner, @JustinJensen

Philipp Oeser commented

2019-01-02 10:01:05 +01:00

@Sergey: just letting you know this gets reported quite often...

Brecht Van Lommel commented

2019-01-04 18:05:08 +01:00

Added subscriber: @HenriqueGonzaga

Bernhard Engstler commented

2019-01-06 01:54:27 +01:00

Added subscriber: @B_Engstler

Mafer M commented

2019-01-09 21:50:51 +01:00

Really hoping this is fixed soon. It feels like a basic feature for all animators.

Jean-Christophe Romain commented

2019-01-14 15:39:53 +01:00

Added subscriber: @Alewinn

Jean-Christophe Romain commented

2019-01-14 15:39:53 +01:00

Still don't work with today build (downloaded from blender.org / beta section / windows 64).

If this can be useful ; I added the file I use to test this feature (see attached blend file).

The cube should desapear if you move up the constrained cone.
With the current build, I noticed that the outliner updates correctly when you hoover it with mouse cursor (icons updates, sometimes with a bit lag, as long as you hoover the outliner with the mouse cursor) but the 3D view won't update. You will have to disable/enable the cube object selection in the outliner, then the 3D view will update.

Also, if you play too much with the 3D view visibility of the cube inside the outliner (the eye icon) it will krashes blender, and/or have unpredictable behaviours.

Hope this would help a bit...

zz_Drivers_Visibility.blend

Still don't work with today build (downloaded from blender.org / beta section / windows 64). If this can be useful ; I added the file I use to test this feature (see attached blend file). The cube should desapear if you move up the constrained cone. With the current build, I noticed that the outliner updates correctly when you hoover it with mouse cursor (icons updates, sometimes with a bit lag, as long as you hoover the outliner with the mouse cursor) but the 3D view won't update. You will have to disable/enable the cube object selection in the outliner, then the 3D view will update. Also, if you play too much with the 3D view visibility of the cube inside the outliner (the eye icon) it will krashes blender, and/or have unpredictable behaviours. Hope this would help a bit... [zz_Drivers_Visibility.blend](https://archive.blender.org/developer/F6286073/zz_Drivers_Visibility.blend)

K Wolf commented

2019-01-14 20:21:36 +01:00

Added subscriber: @KillerWolf

K Wolf commented

2019-01-14 20:21:36 +01:00

i've just found this problem - keyframing renderability for a Plane object and a Point Lamp are not working in an animation file that worked at 2.79

Brecht Van Lommel commented

2019-01-15 08:57:25 +01:00

Added subscriber: @tomnel

Daniel van Westen commented

2019-01-15 14:45:18 +01:00

Added subscriber: @daniel.vanwesten

Brecht Van Lommel commented

2019-01-19 11:11:16 +01:00

Added subscribers: @Cenda, @ZedDB

Brecht Van Lommel commented

2019-01-19 11:11:36 +01:00

Added subscriber: @doakey3

Brecht Van Lommel commented

2019-01-19 11:12:23 +01:00

Added subscribers: @candreacchio, @Micool, @JacquesLucke

Brecht Van Lommel commented

2019-01-28 08:01:36 +01:00

Added subscriber: @JuanCamardella

Fletcher Graham commented

2019-01-29 15:43:01 +01:00

Added subscriber: @fletchgraham

Fletcher Graham commented

2019-01-29 15:43:01 +01:00

To get around the issues with keyframing visibility in 2.80, I used a script instead.

import bpy

# create a list of frames:
frames = []
for i in range(26):
    frames.append([str(i)])


# define which objects are visible on each frame:
frames[1] = ['object1']
frames[2] = ['object2', 'object3']
frames[3] = ['object1', 'object4', 'object2']

# define the function that runs before we advance to the next frame:
def run_script(scene):
    
    objects = bpy.data.collections['subject'].objects

    current_frame = bpy.context.scene.frame_current

    for object in objects:
        if object.name in frames[current_frame]:
            object.hide_viewport = False
            object.hide_render = False
        else:
            object.hide_viewport = True
            object.hide_render = True

bpy.app.handlers.frame_change_pre.append(run_script)

There's probably a more pythonic way to write this but it works!

To get around the issues with keyframing visibility in 2.80, I used a script instead. ``` import bpy # create a list of frames: frames = [] for i in range(26): frames.append([str(i)]) # define which objects are visible on each frame: frames[1] = ['object1'] frames[2] = ['object2', 'object3'] frames[3] = ['object1', 'object4', 'object2'] # define the function that runs before we advance to the next frame: def run_script(scene): objects = bpy.data.collections['subject'].objects current_frame = bpy.context.scene.frame_current for object in objects: if object.name in frames[current_frame]: object.hide_viewport = False object.hide_render = False else: object.hide_viewport = True object.hide_render = True bpy.app.handlers.frame_change_pre.append(run_script) ``` There's probably a more pythonic way to write this but it works!

Immanuel Calvin Herchenbach commented

2019-01-29 21:58:11 +01:00

Added subscriber: @ImmanuelCalvinHerchenbach

Immanuel Calvin Herchenbach commented

2019-01-29 21:58:11 +01:00

I allready had this problem in a few projects.
Thank you @fletchgraham for your suggestion on forcing blender to update through python.

Here is my temporary fix.
After running the script the keyframes should behave as usual.

import bpy

render_only = False

def hide_on_render(scene):
    current_frame = bpy.context.scene.frame_current
    
    for object in bpy.data.objects:
        fcurve = object.animation_data.action.fcurves.find('hide_render')
        
        if fcurve:
            hide = fcurve.evaluate(current_frame) > 0

            object.hide_viewport = hide
            object.hide_render = hide
        

if render_only:
    bpy.app.handlers.render_pre.append(hide_on_render)
else:
    bpy.app.handlers.frame_change_pre.append(hide_on_render)

I allready had this problem in a few projects. Thank you @fletchgraham for your suggestion on forcing blender to update through python. Here is my temporary fix. After running the script the keyframes should behave as usual. ``` import bpy render_only = False def hide_on_render(scene): current_frame = bpy.context.scene.frame_current for object in bpy.data.objects: fcurve = object.animation_data.action.fcurves.find('hide_render') if fcurve: hide = fcurve.evaluate(current_frame) > 0 object.hide_viewport = hide object.hide_render = hide if render_only: bpy.app.handlers.render_pre.append(hide_on_render) else: bpy.app.handlers.frame_change_pre.append(hide_on_render) ```

Sebastian Parborg commented

2019-01-31 12:08:16 +01:00

Added subscribers: @arkadiusz_palki, @WilliamReynish

Hidde Jansen commented

2019-01-31 17:25:39 +01:00

Added subscriber: @HiddeJansen

Austin Dozier commented

2019-02-04 07:31:21 +01:00

Added subscriber: @BlandSauce

Sebastian Parborg commented

2019-02-09 13:42:53 +01:00

Added subscriber: @DBAGibbz

Philipp Oeser commented

2019-02-11 13:50:53 +01:00

Added subscriber: @StephenHamacek

Brecht Van Lommel commented

2019-02-11 13:51:48 +01:00

Added subscriber: @EugenioPignataro

Eugenio Pignataro commented

2019-02-11 13:58:23 +01:00

I've the same problem.
I believe that being able to control visibility on viewport is very important.

Using scripts can be a patch, but I doubt it is the best solution.
It was better than it was before.

I've the same problem. I believe that being able to control visibility on viewport is very important. Using scripts can be a patch, but I doubt it is the best solution. It was better than it was before.

Yassir A. P. commented

2019-02-13 00:34:01 +01:00

Added subscriber: @Yassir

Yassir A. P. commented

2019-02-13 00:34:01 +01:00

I've just discovered this problem. I don't really understand the script workaround, but I know it's something with the internal code not updating. Because if I move a keyframe of Disable Render channel from the object, it will be updated, but then stays like the last render until I move any keyframe of Disable Render channel again.

I've just discovered this problem. I don't really understand the script workaround, but I know it's something with the internal code not updating. Because if I **move** a keyframe of Disable Render channel from the object, it will be updated, but then stays like the last render until I move any keyframe of Disable Render channel again.

Yassir A. P. commented

2019-02-13 00:50:08 +01:00

Also I don't know if I should write here or create another task, but I can't even insert keyframe on viewport visibility, while I can insert one for render visibility. It will show an error as shown in the screenshot:
If some people with earlier build can insert keyframe on viewport visibility, even if they don't update correctly, is this one more regression from earlier build or intended to prevent crash? I've tried this on few builds that I still have, with the earliest build on 552b2287db (01/02/2019) and the latest build blender-2.80-d3870471edd7-win64 (12/02/2019).

Also I don't know if I should write here or create another task, but I can't even insert keyframe on viewport visibility, while I can insert one for render visibility. It will show an error as shown in the screenshot: ![viewport_visibility_error_no_active_keying_set.png](https://archive.blender.org/developer/F6594618/viewport_visibility_error_no_active_keying_set.png) If some people with earlier build can insert keyframe on viewport visibility, even if they don't update correctly, is this one more regression from earlier build or intended to prevent crash? I've tried this on few builds that I still have, with the earliest build on 552b2287db86 (01/02/2019) and the latest build blender-2.80-d3870471edd7-win64 (12/02/2019).

Michael Soluyanov commented

2019-02-20 08:16:38 +01:00

Added subscriber: @crantisz

Conrad Dueck commented

2019-02-22 17:17:00 +01:00

Added subscriber: @ConradDueck

Brecht Van Lommel commented

2019-02-25 11:23:12 +01:00

Added subscriber: @dskjal-1

Sergey Sharybin commented

2019-02-28 16:51:09 +01:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2019-02-28 16:51:09 +01:00

Sergey Sharybin commented

2019-02-28 16:51:09 +01:00

Committed quite some fixes in various related ares and this report is supposed to be fixed now! The minimal revision required is 846d265a06.

Thanks for the report, closing.

Committed quite some fixes in various related ares and this report is supposed to be fixed now! The minimal revision required is 846d265a06. Thanks for the report, closing.

Sylvain commented

2019-03-01 14:55:01 +01:00

On blender-2.80-e795dd4a20a1-win64

This fix created a new issue on the rendering an hidden object test anim.blend :

Please try to render this example when the cube is disabled -> blender crashes.

On blender-2.80-e795dd4a20a1-win64 This fix created a new issue on the rendering an hidden object [test anim.blend](https://archive.blender.org/developer/F6736090/test_anim.blend) : Please try to render this example when the cube is disabled -> blender crashes.

Brecht Van Lommel commented

2019-03-01 15:20:11 +01:00

@Micool, please create a new bug report about that.

Sergey Sharybin commented

2019-03-01 16:37:25 +01:00

@brecht, @Micool, fixed it now.

Sylvain commented

2019-03-01 19:04:04 +01:00

@Sergey : this will make me the happiest man :)
I'll test it in the next build.
Thanks a lot.

@Sergey : this will make me the happiest man :) I'll test it in the next build. Thanks a lot.

Bronson commented

2019-03-02 06:13:22 +01:00

Hi Guys,

Im trying the new build, and still cannot animate the "Hide collection in viewport" (the eye icon). Is there some hidden way to animate this value now that its fixed? The tooltip doesnt give me any clues....

Edit:
Looks like on collections these values are still not animatable on either of them....

collection = bpy.data.collections.new("Frame_" + str(fi))
collection.hide_render = False
collection.hide_viewport = False
collection.keyframe_insert( data_path="hide_viewport",
index=-1,
frame=current_frame)
collection.keyframe_insert( data_path="hide_render",
index=-1,
frame=current_frame)

TypeError: bpy_struct.keyframe_insert() property "hide_viewport" not animatable

Hi Guys, Im trying the new build, and still cannot animate the "Hide collection in viewport" (the eye icon). Is there some hidden way to animate this value now that its fixed? The tooltip doesnt give me any clues.... Edit: Looks like on collections these values are still not animatable on either of them.... collection = bpy.data.collections.new("Frame_" + str(fi)) collection.hide_render = False collection.hide_viewport = False collection.keyframe_insert( data_path="hide_viewport", index=-1, frame=current_frame) collection.keyframe_insert( data_path="hide_render", index=-1, frame=current_frame) TypeError: bpy_struct.keyframe_insert() property "hide_viewport" not animatable

Sergey Sharybin commented

2019-03-02 10:55:55 +01:00

Currently only objects visibility is animated.

Allowing animation of collection animation is possible, but is more tricky to implement without loosing ability to keep memory footprint in control.

For now you can instance the collection and control visibility of the instancer.

Currently only objects visibility is animated. Allowing animation of collection animation is possible, but is more tricky to implement without loosing ability to keep memory footprint in control. For now you can instance the collection and control visibility of the instancer.

Nohra Seif commented

2019-03-06 23:06:48 +01:00

Added subscriber: @NSeif

Nohra Seif commented

2019-03-06 23:06:48 +01:00

Hello, I am facing the same problem.
Can someone give an example or a step by step guide of how to key visibility on instanced collection or object? (with the latest build of blender 2.80)

It would be appreciated a lot!
Thanks,

Hello, I am facing the same problem. Can someone give an example or a step by step guide of how to key visibility on instanced collection or object? (with the latest build of blender 2.80) It would be appreciated a lot! Thanks,

Stephen Hamacek commented

2019-03-13 06:33:59 +01:00

Likewise just tried object visibility keyframing in latest build as of today (Mac) and still no option to keyframe or add drivers to object viewport visibility (eye icon in outliner). This is quite a crucial feature for me to start migrating my main project to 2.80

Brecht Van Lommel commented

2019-03-13 11:57:32 +01:00

For that issue, see #62094 (Unable to insert a hide_viewport keyframe via the UI).

Ben commented

2020-02-16 12:40:47 +01:00

Added subscriber: @TheOldBen

Ben commented

2020-02-16 12:40:47 +01:00

Can confirm, this persists on 2.82.6 and 2.83 alpha.
I have attached a sample file and a demo video.

VIsibilityDriverToggleGlitch.blend
VisibilityDriverGlitch.mp4

The file only has a cube with a single Custom Property called "Visibility" on it. Range is 0 to 1.
This drives both Viewport and Render Visibility.

If you activate and deactivate it by dragging, it goes amiss a little less often, but with the arrows, it glitches out irregularly, roughly about 1 in 5 times.

Can confirm, this persists on 2.82.6 and 2.83 alpha. I have attached a sample file and a demo video. [VIsibilityDriverToggleGlitch.blend](https://archive.blender.org/developer/F8342994/VIsibilityDriverToggleGlitch.blend) [VisibilityDriverGlitch.mp4](https://archive.blender.org/developer/F8342993/VisibilityDriverGlitch.mp4) The file only has a cube with a single Custom Property called "Visibility" on it. Range is 0 to 1. This drives both Viewport and Render Visibility. If you activate and deactivate it by dragging, it goes amiss a little less often, but with the arrows, it glitches out irregularly, roughly about 1 in 5 times.

Mavis von Ixus commented

2020-02-16 12:51:11 +01:00

Added subscriber: @mavixtious

Mavis von Ixus commented

2020-02-16 12:51:11 +01:00

I can confirm this. I have the same problem. I have an armature with a mesh parented to it and a properties bone. I tried to drive the visibility of the mesh both in viewport and render and switch between hiding and revealing them using that bone. But I can't hide/reveal them both at same time. Some times they do, sometimes they interchange. In other words, the driver of hiding the mesh in viewport alone works fine with the bone, but if you also drive the rendering, then it bugs and doesn't allow you to hide/reveal them both at the same time, only one at a time. Saving and reloading the file doesn't work for me.

Visibility drivers are not only extremely useful but most of the time necessary, they speed things up and make life much easier, so we can't have them bugging. I strongly suggest you fix this issue as soon as possible. Thank you.

I can confirm this. I have the same problem. I have an armature with a mesh parented to it and a properties bone. I tried to drive the visibility of the mesh both in viewport and render and switch between hiding and revealing them using that bone. But I can't hide/reveal them both at same time. Some times they do, sometimes they interchange. In other words, the driver of hiding the mesh in viewport alone works fine with the bone, but if you also drive the rendering, then it bugs and doesn't allow you to hide/reveal them both at the same time, only one at a time. Saving and reloading the file doesn't work for me. Visibility drivers are not only extremely useful but most of the time necessary, they speed things up and make life much easier, so we can't have them bugging. I strongly suggest you fix this issue as soon as possible. Thank you.

ML commented

2020-04-23 23:07:57 +02:00

Added subscriber: @MarcelLegindi

JC Bize commented

2022-12-10 12:09:00 +01:00

Added subscriber: @jcbize

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Driver/Keyframes on object visibility do not update viewport #56635