Mantaflow - force fields have very low influence compare to 2.90.1 #82488
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#82488
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?
System Information
Operating system: Linux-5.4.0-52-generic-x86_64-with-debian-bullseye-sid 64 Bits
Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.80.02
Blender Version
Broken: version: 2.92.0 Alpha, branch: master, commit date: 2020-11-06 19:20, hash:
d2c102060d
Worked: 2.90.1
Force fields appear to be approximately 50X less powerful in master and 2.91.0
To reproduce the error: go to frame 1, change the resolution to 34 for updating the parameters, and play/cache the simulation in both 2.90.1 and 2.91.0 or master.
Liquid_forcefield_test.blend
Added subscriber: @flaviengiroud
Added subscriber: @sebbas
Changed status from 'Needs Triage' to: 'Confirmed'
Yes, this should not be like that. Fix is coming up!
This issue was referenced by
0e6820cc5d
Changed status from 'Confirmed' to: 'Resolved'
Thanks, that was fast!
Now i can test the new apic solver.
It appear that the problem persists, although less pronounced.
Here is a video comparing blender 2.90.1 and a build from today.
Mantaflow_force_field_tests0001-0300.mkv
Added subscriber: @lichtwerk
Changed status from 'Resolved' to: 'Confirmed'
@sebbas: mind checking again?
Of course, with pleasure.
I did a new test with a turbulence field:
add a quick liquid
disable gravity in both scene and domain
add a turbulence field
increase resolution to 34 to update parameters
This time I redid the same scene from the beginning instead of opening a scene saved in 2.90.1
Result: the turbulance field is much weaker in 2.91.0 beta
Made some further adjustments to forces in
d0c1d93b7e
. Forces should be stronger than before but weaker than in 2.90.1. This change is on purpose as forces in 2.90.1 turned out to be too aggressive.It should be noted that very, very large forces flowing out of open domain boundaries can currently cause smoke to "to explode". This will be fixed separately.
@flaviengiroud Can you try out the latest build (make sure the build is newer than this comment) and report your findings back again?
I buid 2.92.0 and I didn't see any differences
Maybe the commit is not merge to 2.92.0?
I am waiting for builbot and I will test againt
Here is a test with the last buidbot (2020-11-12 19:14, hash: `d59fa12f2a)
Mantaflow_force_field_Nov13.mkv
The difference is really subtle, if there is any.
Added subscriber: @dfelinto
@sebbas remember to update the release logs as well. Any intentional regression needs to be mentioned there.
Short test to illustrate a problem with forces in 2.90.1. And how 2.91 improves this:
2.90.1: Scale (domain and inflow) "as in test file" vs Scale (domain and inflow) by 0.01:
2.91: Scale (domain and inflow) "as in test file" vs Scale (domain and inflow) by 0.01:
While the new scaling of forces in 2.91 would be different, I think the benefits outweigh the cost.
Once this has been added to the release notes, I think this task can be closed.
what do you mean by "scaling of forces", strength of effector, domain scale or resolution?
EDIT: I have edited the post with the videos to make it more clear.
Added subscriber: @zeauro
Is it possible to make mantaflow respecting Unit Scale in Scene properties ?
This is just a simple factor to take into account and that would solve the issue of having to scale down particles display size.
Ok, as we're nearing the 2.91 release I have decided to postpone the changes made in this task. I.e. 2.91 will have the same force behavior as 2.90.1.
One of the reason for this is that if the behavior of forces changes it should be in line with other physics modifiers (e.g. cloth). This is currently not the case and needs more work.
The task will remain open and hopefully there will be improvements for 2.92.
@zeauro Yes, such changes should be part of the improvements for 2.92