Diffusion vs Viscosity #93383
Labels
No Label
Meta
Good First Issue
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 & Devices
Module
Python API
Module
Rendering & Cycles
Module
Sculpt, Paint & Texture
Module
User Interface
Module
VFX & Video
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information 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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-manual#93383
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?
Pagename:
physics/fluid/type/domain/liquid/viscosityBlender Version:
3.0Documentation Language:
enPermanent link
Short description of error
Any direction for more details - How differs Liquid > Viscosity Strength from Liquid > Diffusion Viscosity?
Like now if I go to study what Diffusion means, page mainly contains Viscosity topic as part of Diffusion.
That's quite confusing for me as end user.
It gives me a feeling if text shouldn't be here on page Viscosity ... or Viscosity properties panel in blender shouldn't be part of Diffusion panel = Viscosity page under Diffusion page.
Sorry for that I just can't figure out what is going on here.
Thank you
Added subscriber: @FilipMond
Added subscriber: @tianer2820-2
Added subscribers: @Blendify, @lichtwerk
Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
@Blendify: do you prefer closing reports like these (which seem like a request for doc improvements [without looking at code, I agree btw. that this is confusing], not actual errors in the documentation)?