Sketching bones created bones with 0 radius for envelope #34541

Closed
opened 2013-03-05 23:36:41 +01:00 by Alberto Velázquez · 6 comments

%%%--- Operating System, Graphics card ---
Windows 7 64bits, GTX560

- Blender version with error, and version that worked ---

2.66 official

- Short description of error ---

If you use the Skeleton sketching tool the operation create a lot of bones with 0 in radius, And you must change the radius in each bones because you cannot scale something with 0 in the value.

I don't know if it's normal. But I have asked in blender artistat and nobody answered to the thread.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

only make the same that I write in the description. You can see my result in the blend that I upload.%%%

%%%--- Operating System, Graphics card --- Windows 7 64bits, GTX560 - Blender version with error, and version that worked --- 2.66 official - Short description of error --- If you use the Skeleton sketching tool the operation create a lot of bones with 0 in radius, And you must change the radius in each bones because you cannot scale something with 0 in the value. I don't know if it's normal. But I have asked in blender artistat and nobody answered to the thread. - Steps for others to reproduce the error (preferably based on attached .blend file) --- only make the same that I write in the description. You can see my result in the blend that I upload.%%%

Changed status to: 'Open'

Changed status to: 'Open'
Member

%%%Never used this tool, but it indeed seems to be not setting envelopes. I also get memory errors... seems to be old bugs in this system.

Bone envelopes are quite uncommon these days though. Everyone uses weight groups, which is much more precise for armatures.

%%%

%%%Never used this tool, but it indeed seems to be not setting envelopes. I also get memory errors... seems to be old bugs in this system. Bone envelopes are quite uncommon these days though. Everyone uses weight groups, which is much more precise for armatures. %%%
Member

%%%Just a few notes from my investigations of this issue:

  1. iter->size (in subdivideArcBy()) seems to always be "effectively zero", but is actually some really really small value (e.g. 0.00000000000001). Replacing the "iter->size > 0" checks to use FLT_EPSILON instead of 0 seems to solve the problem of bones getting wrong envelope size

  2. iter->size actually never gets set to anything meaningful. That is, in most places, the size value is just copied from some other place.
    It seems that the only case where size gets set to anything is when some specific volume/snapping settings are enabled, in which case it is taken to be the size difference between two matching depth points AFAICT. But, this is almost never used; even then, I've never really been able to get the volume snapping to behave even semi-reliably.%%%

%%%Just a few notes from my investigations of this issue: 1) iter->size (in subdivideArcBy()) seems to always be "effectively zero", but is actually some really really small value (e.g. 0.00000000000001). Replacing the "iter->size > 0" checks to use FLT_EPSILON instead of 0 seems to solve the problem of bones getting wrong envelope size 2) iter->size actually never gets set to anything meaningful. That is, in most places, the size value is just copied from some other place. It seems that the only case where size gets set to anything is when some specific volume/snapping settings are enabled, in which case it is taken to be the size difference between two matching depth points AFAICT. But, this is almost never used; even then, I've never really been able to get the volume snapping to behave even semi-reliably.%%%

%%%Ton- I don't use this tools because I don't make animations. But I was learning this part of the program to know all the workflow / tools and I saw the problem. I suppose that some people will use this system (I dunno) and I reported the bug. ^^

%%%

%%%Ton- I don't use this tools because I don't make animations. But I was learning this part of the program to know all the workflow / tools and I saw the problem. I suppose that some people will use this system (I dunno) and I reported the bug. ^^ %%%
Member

%%%I committed the mentioned fix (r. 55105) which solves the immediate symptoms of the bug.

However, this does not address why exactly why/how those values got there in the first place. As this code is currently orphaned - i.e. no active developers actually know exactly what all of it is doing - I've noted this issue on the todo list for when someone with the time and interest in improving this system can check on it.%%%

%%%I committed the mentioned fix (r. 55105) which solves the immediate symptoms of the bug. However, this does not address why exactly why/how those values got there in the first place. As this code is currently orphaned - i.e. no active developers actually know exactly what all of it is doing - I've noted this issue on the todo list for when someone with the time and interest in improving this system can check on it.%%%
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
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
3 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#34541
No description provided.