- User Since
- Nov 14 2015, 4:27 PM (204 w, 5 d)
May 27 2016
May 26 2016
May 25 2016
Response Via Email (Troy) 05/24/2016 04:34 PM
May 23 2016
Ive been communicating with Nvidia Support for several days now, I also made a video for their dev team exactly how to reproduce the issue in win8.1 and win 10. This is the last worthy response I received from them. Supposedly the error has something to do with WDDM 2.0 since thats what windows 10 uses. Windows 7/8/8.1 use WDDM 1.1/1.2/1.3. yw :D
May 17 2016
May 16 2016
Obviously there is problem with cycles. Horrible GPU render performance on GTX Titan X with v2.77a. Basically Titan X is 127% slower than 780 Ti when rendering Mike Pan's BMW scene. But with v2.76 it is only 32% slower, still it should not be slower! I am not super expect but the first thing that comes to mind is most likely bad code in the kernel file kernel_sm_52.cubin OR the larger VRAM on 980ti and Titan X.
Nov 15 2015
Is there a working beta of the split kernel? ETA?
I just rendered this bench test scene BMW27.blend (http://blenderartists.org/forum/showthread.php?239480-2-7x-Cycles-benchmark-%28Updated-BMW%29&highlight=2.7+benchmark), on v2.71 and v2.76, got identical times(1:27) in both versions but v2.76 used 1300MB VRAM and v2.71 used 800MB. You said this is because volume rendering has been added to v2.72 and up but both images look identical so why is it eating up 500MB more VRAM for some feature that I am not even using?
So by adding volume rendering on GPU it uses up twice as much VRAM? Still a simple cube like this should not take up 1/3rd of VRAM. CPU rendering just takes less than 3MB of system RAM to render the same scene but 1,150GB VRAM on GTX780Ti seems a bit extreme dont you agree? Octane just uses under 300MB for comparison, 4x less than Cycles in Blender v2.72-v2.76 to render the same scene. Even with the Quadro K2200 378MB is high. Seems like there is a lot of VRAM being wasted somewhere and the code still has room for performance optimizations.
Nov 14 2015
I ve done multiple render test's with the basic cube scene as far as v2.66 to the latest v2.76 and noticed with GPU-Z that with each new release Cycles uses more and more VRAM then what it actually reports inside Blender while rendering.