Page MenuHome

mantaflow smoke simulation does not appear in cycles gpu render
Closed, ArchivedPublic

Description

System Information
Operating system: windows 10 prof. 64-bit
Graphics card: 1650 4gb

Blender Version
Broken: (2.83 cycles engine)
Worked: (2.83 eevee engine)

Blender was downloaded from STEAM
Short description of error

I made a simple scene with smoke simulation (MANTAFLOW). After I baked the simulation, and checked in render view under cycles engine it worked well. After I tired to render a simple 1920x1080 image (with 32 render samples render volume 0.075, step size:1024.) the objects rendered well, but the smoke did not. I shift to CPU rendering (CPU type: i7-9750h 6 cores 12 threads) it works well, but under OpenCl again fail. Under EEVEE engine it rendered well.

How can I solve the problem, or it will be fixed in the future?

Thanks
Exact steps for others to reproduce the error
I used a 250 sample cache, all other included in *.blend file. Cache file type: OpenVDB, with final type.

Event Timeline

Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.Jun 25 2020, 12:38 PM

Could you please upload simpler file that could be baked and tested ideally in few seconds?

Could you please upload simpler file that could be baked and tested ideally in few seconds?

At the moment maybe a solved the problem. I checked the "Vector" pass in the original blend file, and while this was checked, the cycles does not work, only eevee. I made a short, animation without checking the vector pass, and it is work well.

Sorry for the late comment, I solved it just a few mintes earlier than your comment. Of course I will make a small bake asap.

Philipp Oeser (lichtwerk) closed this task as Archived.Jul 6 2020, 11:02 AM
Philipp Oeser (lichtwerk) claimed this task.

No activity for more than a week.

Will close for now, but feel free to comment again if issues persist, we can always reopen then (make sure to include the smaller example file in that case, also, if this turns out to be an issue with the Vector pass specifically, please also note that in the report description...)