4
$\begingroup$

For some reason Blender does not use my GPU when rendering, even though I have my card selected in the user preferences enter image description here

When I render, my CPU usage goes up to 100% and MSI Afterburner shows no increase of GPU usage. It also doesn't show an option to change my compute device in the system area or whatever enter image description here

However, when I switch to Cycles Render, it gives me the option to use my GPU, but not when I am in normal Blender Render. Is there a way to fix this or is it set like this for some reason? enter image description here

$\endgroup$
  • 4
    $\begingroup$ Blender Internal was designed to render using CPU, currently it cannot make advantage of using GPU for rendering, thats why there is no option for that. $\endgroup$ – Denis Apr 22 '15 at 6:18
  • $\begingroup$ @Denis That should be an answer, not a comment. Comments are for clarification. $\endgroup$ – Ray Mairlot Apr 22 '15 at 10:03
5
$\begingroup$

GPU Rendering is not available for Blender Internal

Blender Internal engine was designed to use CPU long before GPU rendering was available. To make the use of GPU in Blender Internal it will be necessary to rewrite the code of this rendering engine in order to adapt to different computation technology, currently it is not in the priority of the developers, but hopefully in the future.

$\endgroup$
  • 1
    $\begingroup$ Highly doubtful, all the focus is currently on Cycles, and Internal has not been updated in a long time. I believe it's being phased out at the moment since cycles is a superior engine. $\endgroup$ – meed96 Apr 22 '15 at 14:46
  • $\begingroup$ I wouldn't ever expect to see BI ported to GPU. It's an old rendering engine and will probably be replaced with the new viewport work. @meed96 It probably won't be going anywhere for a while, but there won't be much development. $\endgroup$ – TARDIS Maker Apr 22 '15 at 18:23
  • 1
    $\begingroup$ @meed96 Blender Internal had minor updates recently in the node editor, and there is no reason that it should be phased out since it has some advantages with much faster non-realistic rendering than cycles. $\endgroup$ – Denis Apr 22 '15 at 22:24
  • $\begingroup$ @Denis I'm not saying I made the decision to do it, but I do support it. I'm just saying that's the way it is. Also, the node editor is for Cycles? $\endgroup$ – meed96 Apr 23 '15 at 0:58
  • $\begingroup$ @meed96 There is node editor in Blender Internal too for making complex materials. $\endgroup$ – Denis Apr 23 '15 at 1:06

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.