Mantaflow rendering unstable (when using multiple fluid domains) #80154
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#80154
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: Ubuntu 18.04
Graphics card: Radeon R9 FURY
Blender Version
Broken: 2.83.5
Worked: none
Short description of error
Mantaflow seems unstable during rendering of 6 simultaneous domains and it relates to the cycles AA samples.
The error it shows:
Exact steps for others to reproduce the error
Render Animation
Added subscriber: @Rabit
Changed status from 'Needs Triage' to: 'Needs User Info'
Looks like it's happening during animation rendering once per ~150 frames, still trying to figure out the minimal configuration.
Ok, just reproduced the issue on a simple blend file and default blender 2.83.5 . Will reproduce one more time from nothing and will attach the steps to reproduce and the file.
Simple test blend file: mantaflow-render-test.blend
Steps to reproduce:
Render Animation
Added subscriber: @Raimund58
Hello Guys, anyone could reproduce? @Raimund58
Changed status from 'Needs User Info' to: 'Needs Triage'
Added subscriber: @sebbas
@Rabit Are you able to get a crash with the latest daily build too?
Blender 2.83.5 just crashed for me. Where do I find the logs?
So, I checked recently released 2.90 - even worse it crashed on 2th step "baking" (5th domain bake, 215 frame):
Restarted blender and restarted 5th domain baking, it's going significantly (2-3 times) slower from 4th domain bake - and failed again on 180 frame. So I can't even reproduce the previous 2.83.5 steps.
On 2.83.5 (left domain to right):
Next I switched to 2.90 to render with baked caches from 2.83.5:
So in 2.90 we have another issue with baking the example blend file, as well as with the rendering.
@Raimund58 The logs I posted is right in the stderr/stdout of blender - just check it's system console (on windows) or run it directly from the console.
@Rabit Just had my first crash - it took some time as you mentioned already. Will look into this now.
@Rabit Could you still try and see if you can get a crash with a daily build: https://builder.blender.org/download/
I had my crash with 2.90 too. It would be interesting to know if the issue is present in 2.91 as well.
Changed status from 'Needs Triage' to: 'Confirmed'
I just tested the latest blender-2.91.0-ba188e721899-linux64 build:
Warnings during baking:
Baking domains 2nd pass (left to right):
Fresh baked caches render:
So it looks quite the same as for 2.83.5 - but I did not catch the failure during 2 passes of baking as for 2.90 version.
@Rabit Thanks a lot for all the tests! I also got some more crashes in my tests, it looks like this is an issue in general when having multiple domains in the scene.
Investigating this ..
Mantaflow rendering unstableto Mantaflow rendering unstable (when using multiple fluid domains)Just found another thing with baking on 2.90 - if I'm changing the initial fuel level (0-1.3 bezier) for example and not starting from 1.3 - it's dissolving before reaching top of the domain, than it probably will not fail. Not sure how it's related, but maybe it's a workaround for now - just make sure the fire particles not reaching the domain limits.
Added subscriber: @VGSymphony
I still have an issue with baking in 2.92 with multiple domains. Any update on the bug?
Added subscriber: @ankitm
I confirmed a report with same error with simpler steps and reliable crash in #87828 (Mantaflow error when using blender in background mode). There's also an assert hit there.
Keeping this open since steps to redo are very different.
Added subscriber: @evantryan
Mantaflow (fluid simulator) has no active developer at the moment. Moving those bugs as known issues so at least other users can find their issues already reported.