high resolution smoke doesn't collide properly with animated objects #39261

Closed
opened 2014-03-19 12:51:16 +01:00 by Kristian Halvorsen · 9 comments

System Information
Windows 7 Professional 64 bit, NVidia Geforce GT 650M
also reproduced on
Windows 7 Professional 64 bit, NVidia Quaddro 2000

Blender Version
Broken: 2.69.0 r60995, also 2.70 release candidate Date: 12-03-2014 Hash: 2525f9c
working: None that I've tried

Short description of error
The generated smoke from the smoke high resolution settings doesn't seem to calculate animated collisions properly and thus spreads through
animated smoke collision objects.

Exact steps for others to reproduce the error
high_res_smoke_animated_collision.blend
Smoke flow & domain is set up with animated collision object,
so just play the animation.

**System Information** Windows 7 Professional 64 bit, NVidia Geforce GT 650M also reproduced on Windows 7 Professional 64 bit, NVidia Quaddro 2000 **Blender Version** Broken: 2.69.0 r60995, also 2.70 release candidate Date: 12-03-2014 Hash: 2525f9c working: None that I've tried **Short description of error** The generated smoke from the smoke high resolution settings doesn't seem to calculate animated collisions properly and thus spreads through animated smoke collision objects. **Exact steps for others to reproduce the error** [high_res_smoke_animated_collision.blend](https://archive.blender.org/developer/F81774/high_res_smoke_animated_collision.blend) Smoke flow & domain is set up with animated collision object, so just play the animation.

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @krisoyo

Added subscriber: @krisoyo
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Lukas Tönne self-assigned this 2014-03-19 15:54:34 +01:00
Member

This is not a bug. The whole point of the "HighRes" feature in smoke sim is to provide additional detail at little to no cost. This means it cannot take into account things like collision or forcefields, otherwise it would work just like regular smoke and not be a separate feature.

To use this properly your colliders have to have some thickness to them. A "zero thickness" plane like in the test file is not suitable as a smoke collider really.

This is not a bug. The whole point of the "HighRes" feature in smoke sim is to provide additional detail *at little to no cost*. This means it cannot take into account things like collision or forcefields, otherwise it would work just like regular smoke and not be a separate feature. To use this properly your colliders have to have some thickness to them. A "zero thickness" plane like in the test file is not suitable as a smoke collider really.
Member

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'
Member

Added subscriber: @miikah

Added subscriber: @miikah
Member

Discussed this with @miikah, looks like this could actually be considered a bug. Unfortunately there is no good solution to the problem either way ...

Collision with animated objects clears cells marked as "obstacles" entirely, which leads to blocky appearance (just see what happens when you disable highres smoke in the example). Doing the same for highres smoke might be less obvious, but could still show undesirable artifacts (gap between collider and smoke).

Added this to the ToDo list: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Smoke

Discussed this with @miikah, looks like this could actually be considered a bug. Unfortunately there is no good solution to the problem either way ... Collision with animated objects clears cells marked as "obstacles" entirely, which leads to blocky appearance (just see what happens when you disable highres smoke in the example). Doing the same for highres smoke might be less obvious, but could still show undesirable artifacts (gap between collider and smoke). Added this to the ToDo list: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Smoke
Lukas Tönne removed their assignment 2014-03-19 16:35:12 +01:00
Daniel Genrich was assigned by Lukas Tönne 2014-03-19 16:35:12 +01:00
Member

Added subscriber: @LukasTonne

Added subscriber: @LukasTonne
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
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#39261
No description provided.