Blender 2.83 Buggy and Glitchy Mantaflow fire animation in Cycles #77678
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
12 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#77678
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
PC 1
Operating system: Windows-10-10.0.18362-SP0 64 Bits
CPU Ryzen 1700X
Graphics card: Radeon RX 560 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.1 26.20.15029.20013
8GB RAM
PC 2
Operating system: Windows-10-10.0.18362-SP0 64 Bits
CPU Ryzen 2700X
Graphics card: nVidia 1660 TI, latest driver
32GB RAM
Blender Version
Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash:
211b6c29f7
Worked: v2.83 beta (from sometime in May)
Short description of error
When rendering a mantaflow fire or fire + smoke animation in Cyclesthe result is a glitchy and buggy mess of a file/files.
Exact steps for others to reproduce the error
So I've tried this on 2 different computers and 2 different versions of Blender 2.83 LTS and 2.9 alpha I've been doing this for a week. The results are the same.
And none of the PC's run out of memory or anything. This is a simple mataflow fire animation but there are some really serious show-stopping bugs. I've had Blender crash on me several times. No matter if the output are pictures or a single .mp4 file.
When I render a single frame in Cycles the render is correct most of the time, but not always.
When I render the animation in Cyles, 50% or more of the frames are glitched out.
When I render in EEVEE everything is fine, no problems.
I have also cleared the baked cache many times. And tried different locations.
I have only a single node, Principled Volume attached to the Volume input in Material Output in the Shader editor.
I have tested with many new files not just a single one .blend file.
This is how it Renders in EEVEE, which is correct.
This is the same file rendered in Cycles, that glitches out. This was with jpg output. Have tried with many mantaflow samples settings. Many different output settings. The results are always buggy in Cycles but not EEVEE.
Here's another Cycles render example with another file.
This is the file from the first example. But I have many more with the same problems.
mantaflow fire.blend
#77601 was marked as duplicate of this issue
#77501 was marked as duplicate of this issue
#77543 was marked as duplicate of this issue
Added subscriber: @Arken
Added subscriber: @PaulGriffin
Added subscribers: @Lazza, @nacioss
Changed status from 'Needs Triage' to: 'Confirmed'
I would like to add that the viewport for Cycles works correctly.
So I managed to manually render with the "Save Screenshot" menu command.
And this is what it should look like in the final Cycles render
Added subscriber: @schmicky
I have the same issue https://developer.blender.org/T77601
Happens only with Adaptive Domain + Noise.
Note: your eevee render is wrong as well. You've got fire were you should have smoke.
Try the same simulation on 2.82a. Get it on https://download.blender.org/release/Blender2.82/
While the bug is fixed, open your file on 2.82a, bake it on 2.82a and save.
Open on 2.83.0 and it should render fine.
Added subscriber: @ankitm
Added subscriber: @wenderversaofull
Added subscriber: @Adam-Burke
Removed subscriber: @nacioss
Added subscriber: @lichtwerk
There is also an issue with VDBs in the volume object [not sure this is related though] #77882 (Cycles VDB Artifacts (EEVEE WORKING))
Here's another example with only smoke.
Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-06-16 18:15, hash:
c7b03fe9c0
If you pay attention you'll see halfway through the smoke simulation the simulation brakes, not to mention the glitchy final render.
mantaflow smoke 256 cycles 32.mov
Added subscriber: @peterjavidpour
Added subscriber: @JacquesLucke
This has been fixed by
461ba2c74c
.Changed status from 'Confirmed' to: 'Resolved'
Added subscriber: @sebbas
I've been playing around with this a bit - the crash seems to be fixed.
@Arken Can you check what problems you still have. I had some jitter, this time with Eevee though.
Never mind - seems to be fixed now.
Added subscriber: @Catalyst100
In which version?
@Catalyst100 The commit is in both the upcoming 2.90 and 2.91 (master).