- User Since
- Mar 15 2016, 4:13 PM (183 w, 5 d)
Sep 2 2018
Over the three weeks I think Ive managed to eliminate the deleting of bake files. I did this by making all the bake files READ ONLY after they were done baking. Today I viewed the process output from one render job and I noticed a ton of errors where blender was reporting that it could not delete a file. Could it be, that blender is trying to delete my bake files, but cant because I made them read-only??
Aug 3 2018
Did a bake with 5 new domains a couple days ago for torches. Started at frame 1. Baked the domains. Then moved the playhead to a half-way point through the animation to check the fire and they were all there. Then I did a F12 render and 2 of the torches were missing. Checked the bake files and the files for those two domains were gone. Guys, this happens over and over and over again. It’s killing me. I’m literally not able to do anything that requires a bake. We are losing bake files at work that take days to bake! Please help us find a fix or a work-around or something.
Jul 30 2018
here is a link to a dramatically simplified .blend with only 5 smoke domains. (Imagine 4-5 more smoke domains on 10 more layers and that is my scene for the torches). Bake these domains using the external settings, only maybe changing the folders, and then save the project. Close it. Restart the computer or just wait awhile and then make move the playhead to some different frames, and eventually the bake files will disappear. I dont even know what's causing this (thats the problem), or else I would give more specific steps to reproduce it, but again, the behaviour is consistent across 3 machines and different .blend projects on different platforms (mac & windows). We REALLY need some help with this. Cant get any bakes to stay put... and with large bakes (over 200gb collectively and 12+ hours into bakes) this is a HUGE HUGE problem.
Bake sample can be downloaded here: bake_sample.zip
Jul 22 2018
Feb 10 2017
Oct 21 2016
Yes its still an issue. To my knowledge nobody has even worked on fixing this issue. Furthemore Blender 2.78 renders the light intensity differently on the GPU than it does on the CPU. We have a renderfarm with some machines rendering on the CPU and some on the GPU where available, and on our animations the fire was flickering because the light was different. So we went back to 2.77. 2
Jun 7 2016
This task is approaching 90-days since it was opened. Is there any progress or work being conducted on this yet on the Mac side of things?
Jun 1 2016
May 23 2016
May 16 2016
How can it be an Nvidia driver issue when previous versions of Blender worked fine with the 980Ti and Titan on the same OS and Nvidia driver. The only thing that changed was the Blender version, which tells me it's something in The new blender version that is the issue. Furthermore this is a cross platform issue. I have OSX 10.10.4 and have the same problem.
May 6 2016
No activity here for awhile. Any progress on this?
Apr 21 2016
Here is a visual example of what Im talking about..
Apr 20 2016
I just got this same timeout error in OSX using a dedicated Titan X GPU (no monitors or devices connected to the card). Im using 2.77a and OSX 10.10.4
Apr 15 2016
The 980 Ti fan is activated only after reaches a certain temperature. And if a maximum load is put on the card, the fan will still idle until it reaches the temperature necessary to trigger the fan.
Apr 14 2016
Apr 12 2016
I see there has been no activity here for awhile. Just dropping this post to keep the issue fresh. I know a lot of bugs get submitted every day. I did a render last night of a scene with a fire & smoke, and the smoke is a different color on each frame rendered with the GPUs than with the CPUs.
Apr 3 2016
Mar 24 2016
As you can see from the previous smoke benchmarks and the BMW benchmarks I ran this morning, somewhere between 2.76b and 2.77 the TitanX took a big hit on performance (at last a 75% reduction in performance in non smoke and a massive 90% performance loss when compared to the 780ti when rendering smoke).
@Sergey Sharybin (sergey) we leave this in your capable hands. :)
Are there non-smoke/fire scenes with huge performance difference between 2.76 and 2.77/latest master?
Mar 21 2016
ok Im going to pipe in. I've got the same problem. Have two 2013 MacPro's, one with a GTX 980 Ti and the other with a Titan X. Rendering smoke effects in 2.77 takes 2-4x longer for me. Not knowing of this case, I already started a similar report here https://developer.blender.org/T47808
I see this case is assigned to "none" and priority is "incomplete." Is this bug submission a lost cause?
Mar 18 2016
Any thoughts after seeing the .blend or the images Thomas?
Thanks for the help Joel. Im out of ideas but, I know this will affect a ton of users, as the Titan and 980 Ti cards are among the the top cards on the market right now.
Mar 17 2016
Ok here is a comparison. We rendered the "Altar of Sacrifice without smoke.blend" but added the smoke domain into it.
Render Results for Test.blend:
yeah Ill give it a try.
Here is the rendered CPU image of frame 623.
Joel, do you have a .blend file for this that I could try on OSX to compare render times?
Mar 16 2016
Sorry. I thought maybe you guys would've heard of this before and therefore might be able to explain it from just the images. Ive attached the .blend file.
ok, so you meant to say "GPU uses more powerful Volume sampling code, that might explain why it takes longer on GPU?"
Mar 15 2016
The CPU render time in 2.76 was 4:25, and the CPU render time in 2.77 rc2 was 4:13. A slight increase, but again, this is irrespective of the drastic loss in GPU speed. This is concerning as we just spent $2000 in GPUs to increase render times, and in 2.77 all that is lost. I'd stick with 2.76, but quite a few of our scenes have smoke, which was just enabled for GPU rendering in 2.77.
"CPU uses more powerful Volume sampling code, that might explain why it takes longer on GPU."