Blender 3.6.3 -VS- 4.0 bug Properties Data on Layers Armature #112317
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#112317
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
System Information
Operating system: macOS-13.6-x86_64-i386-64bit 64 Bits
Graphics card: Metal API AMD Radeon Pro 575 1.2
Blender Version
Broken: version: 4.0.0 Alpha, branch: main, commit date: 2023-09-05 22:48, hash:
b5c89822ac40
Worked: (newest version of Blender that worked as expected)
Short description of error
Blender 3.6.3 -VS- 4.0 bug Properties Data on Layers Armature
Exact steps for others to reproduce the error
See my video about Blender 3.6.3 it worked on Armature Data on Layers but 4.0 bug.
https://youtu.be/hlvB70dzFyg?si=BtRcgxNgLGcS1pyI
Hi, thanks for the report. From video, it seems bones from active "bone collection" are not highlighting.
This is not a bug. Now layers have been moved to new UI list and interaction is slightly changed. Use
visibility
property (eye icon) or aselect
property to view the bones that belong to active bone collection.Closing the report. Feel free to comment if I've misunderstood your report.
@PratikPB2123
Would you like show me your screen record and i will follow from 3.6.3 to 4.0 on bone show and hidden?
@Kent-Davis , see image:
These two buttons will help you to achieve old 3.6 behavior
I did not get it.
Blender 3.6.3 there have show and hide (eye) it work but 4.0 show and hide (eye) not work.
I see there is an internal problem with the file.
The bone collections in it are already messed up. (The eye icons don't work).
This was perhaps caused by the use of some still-in-development version of Blender.
One way to get around the problem is:
@Kent-Davis, can you try this workaround?
@mano-wii
You are smart to answer. I did not know why.
It worked what you said.
It worked for now.
Glad it worked :)