Modifier - VertexWeightProximity - Resize target object to be smaller - Apply Rotation & Scale #85852

Closed
opened 2021-02-21 19:24:02 +01:00 by Petr Smrtka · 6 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40

Blender Version
Broken: version: 2.91.2, branch: master, commit date: 2021-01-19 16:15, hash: 5be9ef4177
Worked: (newest version of Blender that worked as expected)

Short description of error
When resizing ( down-scaling ) target objects ( Sphere ) used at VertexWeightProximity, then applying Rotation & Scale, the effected plane resets back based on previous, larger size.

Exact steps for others to reproduce the error

#85852.blend

Very simple scene with one plane, one sphere. The sphere is used as VertexWeightProximity target object to effect the plane vertificies. Plane has 20 by 20 loopcuts, to get more verticies, which are all assigned into Vertex group. This plane has just 2 modifiers in following order : VertexWeightProximity( vertex group = group, target object = sphere, proximity mode = geometry, geometry = vertex, lowest = 1, highest = 0, falloff = smooth, mask vertex group = group ), Displace( using standard built-in cloud texture, coordinates = object, object = sphere, vertext group = group ). When moving the sphere ( target object ), all works fine, the plane verticies are effected by the sphere in proper radius. When scaling the sphere using "S" to be smaller or larger, plane verticies are also effected properly. Now the issue : if the sphere is scaled to be smaller and applying the Rotation & Scale, the effected verticies of the plane are effected in much larger radius than is should be. It seems to me, it's taking the prior sphere size, before applying Rotation & Scale. I got the same issue with Blender 2.93.0 Alpha

regards Petr

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40 **Blender Version** Broken: version: 2.91.2, branch: master, commit date: 2021-01-19 16:15, hash: `5be9ef4177` Worked: (newest version of Blender that worked as expected) **Short description of error** When resizing ( down-scaling ) target objects ( Sphere ) used at VertexWeightProximity, then applying Rotation & Scale, the effected plane resets back based on previous, larger size. **Exact steps for others to reproduce the error** [#85852.blend](https://archive.blender.org/developer/F9837862/T85852.blend) Very simple scene with one plane, one sphere. The sphere is used as VertexWeightProximity target object to effect the plane vertificies. Plane has 20 by 20 loopcuts, to get more verticies, which are all assigned into Vertex group. This plane has just 2 modifiers in following order : **VertexWeightProximity**( vertex group = group, target object = sphere, proximity mode = geometry, geometry = vertex, lowest = 1, highest = 0, falloff = smooth, mask vertex group = group ), **Displace**( using standard built-in cloud texture, coordinates = object, object = sphere, vertext group = group ). When moving the sphere ( target object ), all works fine, the plane verticies are effected by the sphere in proper radius. When scaling the sphere using "S" to be smaller or larger, plane verticies are also effected properly. Now the issue : if the sphere is scaled to be smaller and applying the Rotation & Scale, the effected verticies of the plane are effected in much larger radius than is should be. It seems to me, it's taking the prior sphere size, before applying Rotation & Scale. I got the same issue with Blender 2.93.0 Alpha regards Petr
Author

Added subscriber: @PetrSmrtka

Added subscriber: @PetrSmrtka
Member

Added subscribers: @mont29, @lichtwerk

Added subscribers: @mont29, @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Member

Distance calculation of the VertexWeightProximity modifier happens in target local space.

Codewise, check usages of BLI_SPACE_TRANSFORM_SETUP, BLI_space_transform_apply, ...

This means that when scaling down the sphere (object scaling) to e.g. 0.5, then the effective distance of the VertexWeightProximity modifier is 0.5m [when it is set to 1.0m in the UI].
But this also means that when applying scale, the effective distance will be 1.0m again.

Dont think this can be called a bug.
Sure, depending on the usecase, you might want the distance calculation to happen in world space, but this is more of a design decision (or maybe a feature request), but not a bug necessarily.

This is also a nice example of the Geometry Nodes project bringing more flexibility.
You can do this in worldspace there:
T85852_geonodes.blend

So unless @mont29 has objections, I think this can be closed.

Note that for requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Distance calculation of the `VertexWeightProximity` modifier happens in target local space. Codewise, check usages of `BLI_SPACE_TRANSFORM_SETUP`, `BLI_space_transform_apply`, ... This means that when scaling down the sphere (object scaling) to e.g. 0.5, then the effective distance of the `VertexWeightProximity` modifier is 0.5m [when it is set to 1.0m in the UI]. But this also means that when applying scale, the effective distance will be 1.0m again. Dont think this can be called a bug. Sure, depending on the usecase, you might want the distance calculation to happen in world space, but this is more of a design decision (or maybe a feature request), but not a bug necessarily. This is also a nice example of the Geometry Nodes project bringing more flexibility. You can do this in worldspace there: [T85852_geonodes.blend](https://archive.blender.org/developer/F9837858/T85852_geonodes.blend) So unless @mont29 has objections, I think this can be closed. Note that for requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Changed status from 'Needs Developer To Reproduce' to: 'Archived'

Changed status from 'Needs Developer To Reproduce' to: 'Archived'

This is indeed expected behavior currently.

This is indeed expected behavior currently.
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#85852
No description provided.