Most invalid drivers return is_valid==True #119468
Labels
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#119468
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Blender Version
Broken: version: 4.2.0 Alpha, branch: main, commit date: 2024-03-12 22:12, hash:
443ea628c5c8
Worked: I think never
Short description of error
Blender's driver editor clearly knows at least almost always when a driver is valid or not, because the
show_only_errors
toggle works pretty well to find invalid drivers.However, whatever flag the Driver Editor is using to determine if a driver is valid or not is completely out of sync with the
is_valid
flag that is exposed to the Python API. This Python flag almost always returns True, even if the driver is obviously invalid.Exact steps for others to reproduce the error
I prepared a file with various styles of invalid drivers; One per bone, and the name of the bone describes why the driver is invalid.
invalid_drivers_think_they_are_valid.blend
I also included a script file that prints each driver's data path and their Python is_valid flag.
In the below graph, ALL values should return False, because none of these drivers are valid at all.
If anybody can think of other cases of dead drivers that should be reported, please leave a comment.
Docs say, that
is_valid
property only says, if the driver can be evaluated (by python).In your .blend file you are printing state of
FCurve
, not the driver -fc.driver
.Other than that, the code seems to be working correctly - it represents, what is seen as this in UI:
Damn, you're right, my bad.
Still in that case, I still see one remaining issue that a driver targetting a non-existent bone doesn't get reported as invalid, and I think it definitely should. Trying my luck with that in a new report here.