object visibility controlled by driver bug #58187

Closed
opened 2018-11-29 21:50:20 +01:00 by Zeeshan · 26 comments

Operating system: windows 10
Graphics card: gt 730

blender 2.8

hash: 26d5a3625e

date: 29/11/2018

**i can't keyframe object visibilty and worse driver don't work for object visibility.

i can't also add a driver to the object visibility i have to do it by the "disable object on the viewport thing".**

juste key frame the object visibility and after that add a driver and control the mesh visibilty by a bone

2.8 visibility driver bug report.blend

Operating system: windows 10 Graphics card: gt 730 blender 2.8 hash: 26d5a3625ed date: 29/11/2018 **i can't keyframe object visibilty and worse driver don't work for object visibility. i can't also add a driver to the object visibility i have to do it by the "disable object on the viewport thing".** **juste key frame the object visibility and after that add a driver and control the mesh visibilty by a bone** [2.8 visibility driver bug report.blend](https://archive.blender.org/developer/F5759656/2.8_visibility_driver_bug_report.blend)
Author

Added subscriber: @The_art_of_spinjitsu_1_2_3

Added subscriber: @The_art_of_spinjitsu_1_2_3

#59794 was marked as duplicate of this issue

#59794 was marked as duplicate of this issue

#59588 was marked as duplicate of this issue

#59588 was marked as duplicate of this issue

#58303 was marked as duplicate of this issue

#58303 was marked as duplicate of this issue

#58201 was marked as duplicate of this issue

#58201 was marked as duplicate of this issue

Added subscriber: @JustinJensen

Added subscriber: @JustinJensen

Added subscriber: @JakubSteiner

Added subscriber: @JakubSteiner

Added subscriber: @MaferM

Added subscriber: @MaferM

Added subscriber: @clepsydrae

Added subscriber: @clepsydrae
Member

Added subscriber: @Picklejones

Added subscriber: @Picklejones

Added subscriber: @1seby

Added subscriber: @1seby
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

This is a duplicate of #56635, will merge this report into #56635 then

This is a duplicate of #56635, will merge this report into #56635 then
Member

Closed as duplicate of #56635

Closed as duplicate of #56635

Added subscriber: @SidneyMoraesJr

Added subscriber: @SidneyMoraesJr

I guess this is related to #62094 as well, since driver/keying would follow similar workflow.
There is a workaround for this: Add Driver to "Properties > Object > Viewport Display > Display as" and set the values 0 and 5.
(0=Invisible, 1=Bounds, 2=Wire, 3=Solid, 4=???, 5=Textured)
Here is an example: VisibilityDriver_2.8.blend
I don't know if it is intended but it works.

Cheers.

I guess this is related to #62094 as well, since driver/keying would follow similar workflow. There is a workaround for this: Add Driver to "Properties > Object > Viewport Display > Display as" and set the values 0 and 5. (0=Invisible, 1=Bounds, 2=Wire, 3=Solid, 4=???, 5=Textured) Here is an example: [VisibilityDriver_2.8.blend](https://archive.blender.org/developer/F6907772/VisibilityDriver_2.8.blend) I don't know if it is intended but it works. Cheers.

Added subscriber: @StephenHamacek

Added subscriber: @StephenHamacek

Nice Idea Sidney. And in case it hasn't occurred to anyone, I've resorted to adding a mask modifier to relevant objects and keyframing/driving that, in the meantime.

Nice Idea Sidney. And in case it hasn't occurred to anyone, I've resorted to adding a mask modifier to relevant objects and keyframing/driving that, in the meantime.

Added subscriber: @MetinSeven-1

Added subscriber: @MetinSeven-1

If you're absolutely switching from invisible to visible or vice versa, you could also simply scale an object to a value of 0 in the next or previous frame.

If you're absolutely switching from invisible to visible or vice versa, you could also simply scale an object to a value of 0 in the next or previous frame.

Added subscriber: @RainerTrummer

Added subscriber: @RainerTrummer

In #58187#653632, @SidneyMoraesJr wrote:
I guess this is related to #62094 as well, since driver/keying would follow similar workflow.
There is a workaround for this: Add Driver to "Properties > Object > Viewport Display > Display as" and set the values 0 and 5.
(0=Invisible, 1=Bounds, 2=Wire, 3=Solid, 4=???, 5=Textured)
Here is an example: VisibilityDriver_2.8.blend
I don't know if it is intended but it works.

Cheers.

Unfortunately, this won't work as soon as you render with Cycles. Even with Display as set to 0 the object will fully render. In Eevee it disappears.

> In #58187#653632, @SidneyMoraesJr wrote: > I guess this is related to #62094 as well, since driver/keying would follow similar workflow. > There is a workaround for this: Add Driver to "Properties > Object > Viewport Display > Display as" and set the values 0 and 5. > (0=Invisible, 1=Bounds, 2=Wire, 3=Solid, 4=???, 5=Textured) > Here is an example: [VisibilityDriver_2.8.blend](https://archive.blender.org/developer/F6907772/VisibilityDriver_2.8.blend) > I don't know if it is intended but it works. > > Cheers. Unfortunately, this won't work as soon as you render with Cycles. Even with `Display as` set to `0` the object will fully render. In Eevee it disappears.

In #58187#668513, @RainerTrummer wrote:

In #58187#653632, @SidneyMoraesJr wrote:
I guess this is related to #62094 as well, since driver/keying would follow similar workflow.
There is a workaround for this: Add Driver to "Properties > Object > Viewport Display > Display as" and set the values 0 and 5.
(0=Invisible, 1=Bounds, 2=Wire, 3=Solid, 4=???, 5=Textured)
Here is an example: VisibilityDriver_2.8.blend
I don't know if it is intended but it works.

Cheers.

Unfortunately, this won't work as soon as you render with Cycles. Even with Display as set to 0 the object will fully render. In Eevee it disappears.

It doesn't affect the rendering engines, only the viewport. For render it still possible to drive the bpy.data.objects["Object"].hide_render or as in the screenshot attached.
So, in other words, if you want to exclude the object from scene using drivers, you have to driver both options following the values: 0-5 to viewport from display_type and 1-0 to hide_render.

image.png

> In #58187#668513, @RainerTrummer wrote: >> In #58187#653632, @SidneyMoraesJr wrote: >> I guess this is related to #62094 as well, since driver/keying would follow similar workflow. >> There is a workaround for this: Add Driver to "Properties > Object > Viewport Display > Display as" and set the values 0 and 5. >> (0=Invisible, 1=Bounds, 2=Wire, 3=Solid, 4=???, 5=Textured) >> Here is an example: [VisibilityDriver_2.8.blend](https://archive.blender.org/developer/F6907772/VisibilityDriver_2.8.blend) >> I don't know if it is intended but it works. >> >> Cheers. > > Unfortunately, this won't work as soon as you render with Cycles. Even with `Display as` set to `0` the object will fully render. In Eevee it disappears. It doesn't affect the rendering engines, only the viewport. For render it still possible to drive the bpy.data.objects["Object"].hide_render or as in the screenshot attached. So, in other words, if you want to exclude the object from scene using drivers, you have to driver both options following the values: 0-5 to viewport from display_type and 1-0 to hide_render. ![image.png](https://archive.blender.org/developer/F6995494/image.png)

Added subscriber: @bramssking

Added subscriber: @bramssking

i found the solution to hide in 2.80 just clik on -filter in restriction toggles u enable viewport , after than u can add a keyframe to the hide view

i found the solution to hide in 2.80 just clik on -filter in restriction toggles u enable viewport , after than u can add a keyframe to the hide view

Removed subscriber: @MetinSeven-1

Removed subscriber: @MetinSeven-1
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
12 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#58187
No description provided.