Animating hide_viewport propertie deselect objects #71335

New Issue

Samuel Bernou · 2019-11-04T12:35:05+01:00

Samuel Bernou commented

2019-11-04 12:35:05 +01:00

System Information
Operating system: Linux-4.15.0-20-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.87.01

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-03 03:57, hash: 8ab6ef30ab

Short description of error
When animating the "hide_viewport" propertie of an object it deselect it, this was not the case in 2.79.
Not only the selection is lost but this make the user unable to use filters "Selected only" in combination with "Display hidden" like you could do in 2.79

{F7930271, size=full}

Exact steps for others to reproduce the error
Animate the hide_viewport visibility of an object, in graph editor toggle on Selected only and Display hidden. Select the object and then scrub in/out the animated hide range, object gets deselected.
Example blend : animated_display_on_cube.blend

Someone also mentionned it in blender stack exchange with gifs to compare 2.79 and 2.8+ behavior : https://blender.stackexchange.com/questions/147876/hiding-object-in-2-80-via-animated-disable-in-viewport-loses-selection

Thank you !

**System Information** Operating system: Linux-4.15.0-20-generic-x86_64-with-debian-buster-sid 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.87.01 **Blender Version** Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-03 03:57, hash: `8ab6ef30ab` **Short description of error** When animating the "*hide_viewport*" propertie of an object it deselect it, this was not the case in 2.79. Not only the selection is lost but this make the user unable to use filters "*Selected only*" in combination with "*Display hidden*" like you could do in 2.79 {[F7930271](https://archive.blender.org/developer/F7930271/losing_selection_and_only_select_filter.gif), size=full} **Exact steps for others to reproduce the error** Animate the hide_viewport visibility of an object, in graph editor toggle on *Selected only* and *Display hidden*. Select the object and then scrub in/out the animated hide range, object gets deselected. Example blend : [animated_display_on_cube.blend](https://archive.blender.org/developer/F7930267/animated_display_on_cube.blend) Someone also mentionned it in blender stack exchange with gifs to compare 2.79 and 2.8+ behavior : https://blender.stackexchange.com/questions/147876/hiding-object-in-2-80-via-animated-disable-in-viewport-loses-selection Thank you !

Samuel Bernou commented

2019-11-04 12:35:05 +01:00

Added subscriber: @Pullup

blender-admin commented

2019-11-04 12:35:05 +01:00

#94757 was marked as duplicate of this issue

blender-admin commented

2019-11-04 12:35:05 +01:00

#85150 was marked as duplicate of this issue

Philipp Oeser commented

2019-11-04 12:54:12 +01:00

Added subscribers: @dfelinto, @lichtwerk

Philipp Oeser commented

2019-11-04 12:54:12 +01:00

Changed status from 'Open' to: 'Archived'

Philipp Oeser closed this issue

2019-11-04 12:54:12 +01:00

Philipp Oeser self-assigned this 2019-11-04 12:54:12 +01:00

Philipp Oeser commented

2019-11-04 12:54:12 +01:00

Afaict, blender always made hidden objects unselected [animating viewport visibility was an exception there, so to say]
So in a way, 2.8 is more consistent here, and I assume this is all by design [@dfelinto: correct me if I am wrong.]

Will have to close this, as I dont see a bug here.
(there might be usecases where this is inconvenient, for more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug)

Afaict, blender always made hidden objects unselected [animating viewport visibility was an exception there, so to say] So in a way, 2.8 is more consistent here, and I assume this is all by design [@dfelinto: correct me if I am wrong.] Will have to close this, as I dont see a bug here. (there might be usecases where this is inconvenient, for more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug)

Samuel Bernou commented

2019-11-04 14:38:14 +01:00

Ok, thank you for your quick answer. I guessed this was maybe by design but was not sure...
If it is though, I consider this a regression since this exception allowed to keep selections and, more importantly, retime animation of visibility without showing every object in dopesheet (life-saver in dense scenes).

Is there a workaround to move visibility keyframes without them disappearing (by losing selection) ?

Ok, thank you for your quick answer. I guessed this was maybe by design but was not sure... If it is though, I consider this a regression since this exception allowed to keep selections and, more importantly, retime animation of visibility without showing every object in dopesheet (life-saver in dense scenes). Is there a workaround to move visibility keyframes without them disappearing (by losing selection) ?

Evan Wilson commented

2019-11-04 17:47:50 +01:00

Added subscriber: @EAW

Evan Wilson commented

2019-11-04 17:47:50 +01:00

You can click off the check box labeled "Does F-Curve contribute to result."

You can click off the check box labeled "Does F-Curve contribute to result." ![Does F-Curve contribute to result v2.jpg](https://archive.blender.org/developer/F7933823/Does_F-Curve_contribute_to_result_v2.jpg)

chakravarthy commented

2020-01-27 12:54:50 +01:00

Added subscriber: @chakravarthy

chakravarthy commented

2020-01-27 12:54:50 +01:00

Sorry to add an entry here although this thread says closed (I'm new to this, but I had to share on this this topic)

Please consider this as use-case. Consider 3d motiongraphics, where you need to key the visibility of objects often. for the time being we cannot have the visibility animation show up in viewport without losing our selections. It is very important to be able to play/scrub the animation as we refine the timing of keyframes. Below is the situation shown as an image. For now the workaround I am having is to keyframe the scaling to zero if I want objects hidden. Something tells me this is not the right way.

Please don't hesitate to point out, if I am missing something.

Sorry to add an entry here although this thread says closed (I'm new to this, but I had to share on this this topic) Please consider this as use-case. Consider 3d motiongraphics, where you need to key the visibility of objects often. for the time being we cannot have the visibility animation show up in viewport without losing our selections. It is very important to be able to play/scrub the animation as we refine the timing of keyframes. Below is the situation shown as an image. For now the workaround I am having is to keyframe the scaling to zero if I want objects hidden. Something tells me this is not the right way. ![image.png](https://archive.blender.org/developer/F8304803/image.png) Please don't hesitate to point out, if I am missing something.

Germano Cavalcante commented

2021-01-28 21:20:01 +01:00

Added subscribers: @comvico, @mano-wii

Philipp Oeser was unassigned by Germano Cavalcante

2021-01-28 21:30:35 +01:00

Germano Cavalcante commented

2021-01-28 21:30:35 +01:00

Given the repercussion of this issue with even a post on the rightclickselect about it (https://blender.community/c/rightclickselect/Zgfbbc/),
I think it is worth setting this as at least a "Known Issue".

Given the repercussion of this issue with even a post on the rightclickselect about it (https://blender.community/c/rightclickselect/Zgfbbc/), I think it is worth setting this as at least a "`Known Issue`".

Germano Cavalcante commented

2021-01-28 21:38:35 +01:00

Changed status from 'Archived' to: 'Confirmed'

Germano Cavalcante reopened this issue

2021-01-28 21:38:35 +01:00

Sybren A. Stüvel commented

2021-02-08 10:48:36 +01:00

Added subscriber: @dr.sybren

Sybren A. Stüvel commented

2021-02-08 10:48:36 +01:00

This is indeed not a bug, but a design choice that was made for Blender 2.80. It's certainly annoying for certain workflows. The idea behind the change was as a solution to a very annoying other problem, where artists lost a lot of work because they unknowingly performed operations on invisible objects. By the time they made them visible, it was too late because their changes had already been saved so many times, the incremental backups didn't help either. AFAIK this decision was made by prioritising the loss of work over other work becoming more cumbersome.

Germano Cavalcante commented

2022-01-12 16:42:24 +01:00

Added subscriber: @phoenixart

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Animating hide_viewport propertie deselect objects #71335