[Bf-cycles] Proposal for Compute Device Selection from Blender
info at jensverwiebe.de
Sat Nov 5 17:53:02 CET 2016
Look how we solved this in luxblend25, thats very versatile.
Am 05.11.2016 um 16:51 schrieb Lukas Stockner:
> Regarding where to show the options, I just noticed another problem with having them in the user preferences:
> After all, one of the main goals of the change is to move the options from Blender itself into the Cycles plugin. However, as far as I'm aware, there is no possibility for addons to draw properties directly in the User Preferences. Therefore, we'd need to either allow every addon to draw inside the User Preferences, or add a callback to the Render API that makes the engine draw its device settings. That, however, is tricky because the engine depends on the scene, which isn't defined in the context in which the User Preferences are drawn.
> By drawing these properties in the Render tab, we'd avoid that problem.
> Anyways, it seems that there is no problem with the per-device settings, so as a first step it's possible to implement those and call the drawing from the User Preference script through the _cycles module as a temporary solution.
> Am 05.11.2016 um 13:24 schrieb Brecht Van Lommel:
>> On Sat, Nov 5, 2016 at 4:10 AM, Lukas Stockner
>> <lukas.stockner at freenet.de> wrote:
>>>> The CUDA / OpenCL choice seems like a per system choice rather than a
>>>> per scene choice. If you save a .blend file on a computer with an
>>>> NVidia GPU, I want to be able to open and render it on a computer with
>>>> an AMD GPU, without having to make any scene changes every time we
>>>> exchange .blends.
>>> Yes, that makes sense. In that case, though, I'd turn it into a pure GPU type selection and get rid of the CPU option.
>> The reason for the CPU option is to say: never use my GPU, even if
>> it's enabled in the scene (e.g. because it's too weak). If each GPU
>> gets a toggle to turn it on/off the CPU option indeed is not needed
>> What we could have is an option to toggle usage of the CPU in addition
>> to the GPUs, but that will some deeper internal changes before it
>> Bf-cycles mailing list
>> Bf-cycles at blender.org
> Bf-cycles mailing list
> Bf-cycles at blender.org
Allerskehre 44 - 22309 Hamburg
Tel.: +49 40 68 78 50
mobile: +49 172 400 49 07
mailto: info at jensverwiebe.de
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Bf-cycles