- User Since
- Apr 23 2018, 8:39 PM (101 w, 4 d)
Thu, Apr 2
Mar 4 2020
Sorry it took me so long to get back to this. With March 4th version I'm still getting the same issues. Looking at your picture it doesn't look like you had the minimum set above one in the domain. I've attached more pictures.
Feb 23 2020
Both 2.82 (if I import a scene baked in 2.83) and 2.83
Feb 22 2020
Another issue is, when time steps are set to a value greater than one and adding noise up-res I get this in *both* smoke and Smoke+fire in the latest alpha 2.83
Feb 21 2020
Feb 19 2020
Just for fun I set this up. But you can tell when it starts spinning fast the fire is skipping.
Feb 18 2020
I'm still having issues. The smoke works fine by itself. But when I add fire I get this effect. The top one has sub-frames set to 200 while the bottom is default. It seems it's having an effect but I don't believe it's the desired effect.
May 14 2019
You can create a smoke sim in 2.79 and import it I believe. It's worth a try at least. The point data shouldn't care after it's already baked.
Apr 9 2019
Apr 23 2018
I'm having the same issue. Multiple Blender versions, I've switched motherboards (from 2 separate Intel X99s to a Ryzen 2700x just installed today) multiple drivers, multiple formats. The only two things that remain are Blender and this Titan X (pascal first version) Remember, there is two different versions of the Titan X pascals. Switching out the video card solves the issue.