Flow particle_size range is too limiting #80564

Closed
opened 2020-09-07 15:30:27 +02:00 by Stefano Lazzaroni · 4 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.2.2 26.20.15019.19000

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-09-04 21:32, hash: cf0ba59e31
Worked: (newest version of Blender that worked as expected)

Short description of error
While testing Mantaflow i discovered that some values are clamped for apparently no reason. I was doing some tests with particle system as smoke inflows. According to the documentation , the field Size "When this setting is enabled, it allows the Size setting to define the maximum distance in voxels at which particles can emit smoke, similar to the Surface Emission setting for mesh sources.". It is clamped to 20 but we could want to go higher and i don't see any user motivation to clamp this value (as the domain resolution clamped to 10000 instead of letting it unclamped). Here is a video:
0000-0150.mp4

As you can see i was trying to check the different results with different resolution and cell sizes. Why should i not be able to for a 30 or 50 cell size value? In fact, higher domain resolution causes a better and physically accurated simulation.

If there are no limitation due to real problems, i suggest to let the user decide the maximum value needed. In the other hand, if there is a reason to clamp the value so write it in the documentation.

(Sorry for my english, i don't wanna sound arrogant or disrespectful, i'm very proud of mantaflow and i want to improve it as much as i can)

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.2.2 26.20.15019.19000 **Blender Version** Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-09-04 21:32, hash: `cf0ba59e31` Worked: (newest version of Blender that worked as expected) **Short description of error** While testing Mantaflow i discovered that some values are clamped for apparently no reason. I was doing some tests with particle system as smoke inflows. According to the [documentation ](https://docs.blender.org/manual/en/dev/physics/fluid/type/flow.html#flow-source), the field Size "When this setting is enabled, it allows the Size setting to define the maximum distance in voxels at which particles can emit smoke, similar to the Surface Emission setting for mesh sources.". It is clamped to 20 but we could want to go higher and i don't see any user motivation to clamp this value (as the domain resolution clamped to 10000 instead of letting it unclamped). Here is a video: [0000-0150.mp4](https://archive.blender.org/developer/F8850731/0000-0150.mp4) As you can see i was trying to check the different results with different resolution and cell sizes. Why should i not be able to for a 30 or 50 cell size value? In fact, higher domain resolution causes a better and physically accurated simulation. If there are no limitation due to real problems, i suggest to let the user decide the maximum value needed. In the other hand, if there is a reason to clamp the value so write it in the documentation. (Sorry for my english, i don't wanna sound arrogant or disrespectful, i'm very proud of mantaflow and i want to improve it as much as i can)

Added subscriber: @Lazza

Added subscriber: @Lazza
Richard Antalik changed title from Mantaflow: clamped values limit mantaflow power to Flow particle_size range is too limiting 2020-09-11 05:48:43 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'

This issue was referenced by 61abd77648

This issue was referenced by 61abd776487eeb383833f95d602e318e59f42395
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Jacques Lucke self-assigned this 2020-09-14 12:02:34 +02:00
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
4 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#80564
No description provided.