Moving keys of hair particles is very viewpoint depended #33647

Closed
opened 2012-12-21 16:45:03 +01:00 by Tobias Oelgarte · 7 comments

%%%Depending on how the view is positioned (looking from above or below, or from another angle) the strength with which i can comb or grab the keys of hair particles is very different. From some view angles i nearly can't move them at all, and from others the key moves very strongly.

I noticed that it is very depended on the origin of the emiter mesh. A sphere as an emiter with the origin at its center works fine. But if the sphere (the mesh in edit mode) is moved upwards (in z-direction) then the behavior changes. If i now look down (more or less top-view) then the key move much stronger as i drag them, if i look from below, then they are very unresponsive.

I appended an example file with one hair particle and a sphere like mesh moved in z-direction. The view is currently looking upwards, so grabbing the key of the particle has nearly no effect. If you rotate the view, so that you can drag the keys from above, will move the keys very wide in comparison to the mouse movement.

Ideally it should work like dragging vertices in edit-mode, but it doesn't. It is more or less the same issue as with moving vertices if the 3D-Manipulator is somewhere else, which can also make vertices hard to drag.%%%

%%%Depending on how the view is positioned (looking from above or below, or from another angle) the strength with which i can comb or grab the keys of hair particles is very different. From some view angles i nearly can't move them at all, and from others the key moves very strongly. I noticed that it is very depended on the origin of the emiter mesh. A sphere as an emiter with the origin at its center works fine. But if the sphere (the mesh in edit mode) is moved upwards (in z-direction) then the behavior changes. If i now look down (more or less top-view) then the key move much stronger as i drag them, if i look from below, then they are very unresponsive. I appended an example file with one hair particle and a sphere like mesh moved in z-direction. The view is currently looking upwards, so grabbing the key of the particle has nearly no effect. If you rotate the view, so that you can drag the keys from above, will move the keys very wide in comparison to the mouse movement. Ideally it should work like dragging vertices in edit-mode, but it doesn't. It is more or less the same issue as with moving vertices if the 3D-Manipulator is somewhere else, which can also make vertices hard to drag.%%%

Changed status to: 'Open'

Changed status to: 'Open'
Member

%%%Confirmed, checking old code...%%%

%%%Confirmed, checking old code...%%%
Member

%%%Fix is in svn now.

Because you had the transform manipulator visible in the file, I noted the same effect for transform (using manipulator or Gkey).
That is fixed now too.

Thanks :)%%%

%%%Fix is in svn now. Because you had the transform manipulator visible in the file, I noted the same effect for transform (using manipulator or Gkey). That is fixed now too. Thanks :)%%%
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

%%%Thank you very much!

I as well noticed that the amount you can drag depends strongly on the 3D-manipulator position. It actually dragging the manipulator and copying it's offset onto the vertices/keys/etc.

I can understand why it is that way, but there are scenarios in which the control over the 3d manipulator isn't there. For example while editing shape keys on a posed figure mesh. The 3D manipulator is rightfully placed at the vertex location. But it is placed at the rest location (not posed), which is not the actual position/normal of the vertex i edit in the 3d view. Thats why the 3D manipulator is often very close or even behind the view, which gives the same effect. Could it be placed at the transformed vertex location and aligned to it's normal?%%%

%%%Thank you very much! I as well noticed that the amount you can drag depends strongly on the 3D-manipulator position. It actually dragging the manipulator and copying it's offset onto the vertices/keys/etc. I can understand why it is that way, but there are scenarios in which the control over the 3d manipulator isn't there. For example while editing shape keys on a posed figure mesh. The 3D manipulator is rightfully placed at the vertex location. But it is placed at the rest location (not posed), which is not the actual position/normal of the vertex i edit in the 3d view. Thats why the 3D manipulator is often very close or even behind the view, which gives the same effect. Could it be placed at the transformed vertex location and aligned to it's normal?%%%
Member

%%%I guess I can do that :) will go on my own todo list though, that has 40+ items already :)

We'll keep working on solving usability issues, but don't flood me with tips yet, enough todo for a couple of weeks!%%%

%%%I guess I can do that :) will go on my own todo list though, that has 40+ items already :) We'll keep working on solving usability issues, but don't flood me with tips yet, enough todo for a couple of weeks!%%%

%%%I won't flood you. The items on the todo list are also if not even more important. It was just a random thing that came to my mind as i noticed how the 3D manipulator affects the movement of things and what happens if it is placed not at the right location. ;-)%%%

%%%I won't flood you. The items on the todo list are also if not even more important. It was just a random thing that came to my mind as i noticed how the 3D manipulator affects the movement of things and what happens if it is placed not at the right location. ;-)%%%
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
2 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#33647
No description provided.