Smoke in some cases doesn't update animation state in Cycles after first render. #40195

New Issue

Kai Kostack · 2014-05-14T17:10:13+02:00

Kai Kostack commented

2014-05-14 17:10:13 +02:00

System Information
Windows 7 x64

Blender Version
Broken: All

Short description of error
When working in scenes with smoke sometimes the scene turns into a state that make Cycles unable to render any animated smoke anymore. This is a strange problem since even newly created domains doesn't update after the first render. In viewport everything looks fine and even with BI it renders correctly. The only way to fix it is to create a completely new .blend file and append everything from the corrupted file.

Exact steps for others to reproduce the error
This is the second time it happens to me and even though I cannot reproduce it's cause, I at least can provide a damaged scene. This file has a fresh smoke domain with some baked data but it's not updating in Cycles, just render an animation and see.

bug_smoke-in-cycles.blend

**System Information** Windows 7 x64 **Blender Version** Broken: All **Short description of error** When working in scenes with smoke sometimes the scene turns into a state that make Cycles unable to render any animated smoke anymore. This is a strange problem since even newly created domains doesn't update after the first render. In viewport everything looks fine and even with BI it renders correctly. The only way to fix it is to create a completely new .blend file and append everything from the corrupted file. **Exact steps for others to reproduce the error** This is the second time it happens to me and even though I cannot reproduce it's cause, I at least can provide a damaged scene. This file has a fresh smoke domain with some baked data but it's not updating in Cycles, just render an animation and see. [bug_smoke-in-cycles.blend](https://archive.blender.org/developer/F88937/bug_smoke-in-cycles.blend)

Kai Kostack commented

2014-05-14 17:10:13 +02:00

Changed status to: 'Open'

Kai Kostack commented

2014-05-14 17:10:13 +02:00

Added subscriber: @KaiKostack-3

Lukas Tönne commented

2014-05-14 17:22:33 +02:00

Added subscriber: @LukasTonne

Lukas Tönne commented

2014-05-14 17:22:33 +02:00

I noticed this in the very first cycles smoke builds already, but reporting at that stage didn't seem necessary.

IIRC it is possible to reset the smoke representation in cycles somehow, but it's very cumbersome and i can't remember what works exactly. It's certainly a cycles issue (like you said, actual data in viewport is fine), i guess the database tagging doesn't work nicely in those cases. It might be a depsgraph issue, as usual ...

I noticed this in the very first cycles smoke builds already, but reporting at that stage didn't seem necessary. IIRC it is possible to reset the smoke representation in cycles somehow, but it's very cumbersome and i can't remember what works exactly. It's certainly a cycles issue (like you said, actual data in viewport is fine), i guess the database tagging doesn't work nicely in those cases. It might be a depsgraph issue, as usual ...

Brecht Van Lommel was assigned by Lukas Tönne

2014-05-14 17:45:22 +02:00

Kai Kostack commented

2014-05-15 01:15:56 +02:00

I found the cause, it's the "persistent images" option which prevents not only images to be reloaded on frame change but also smoke data. Disabling this instantly fixed the problem.