![]() ![]() But I have many more with the same problems. Here's another Cycles render example with another file. ![]() The results are always buggy in Cycles but not EEVEE. Have tried with many mantaflow samples settings. This is the same file rendered in Cycles, that glitches out. ![]() This is how it Renders in EEVEE, which is correct. I have tested with many new files not just a single one. I have only a single node, Principled Volume attached to the Volume input in Material Output in the Shader editor. I have also cleared the baked cache many times. When I render in EEVEE everything is fine, no problems. When I render the animation in Cyles, 50% or more of the frames are glitched out. When I render a single frame in Cycles the render is correct most of the time, but not always. No matter if the output are pictures or a single. I've had Blender crash on me several times. This is a simple mataflow fire animation but there are some really serious show-stopping bugs. The results are the same.Īnd none of the PC's run out of memory or anything. 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. When rendering a mantaflow fire or fire + smoke animation in Cyclesthe result is a glitchy and buggy mess of a file/files.Įxact steps for others to reproduce the error Worked: v2.83 beta (from sometime in May) Graphics card: nVidia 1660 TI, latest driverīroken: version: 2.83.0, branch: master, commit date: 14:38, hash: 211b6c29f7 Graphics card: Radeon RX 560 Series ATI Technologies Inc. Operating system: Windows-10-2-SP0 64 Bits ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |