[Bf-cycles] RenderSettings.use_border

[Brecht Van Lommel]

It could be more helpful but this is also just the way python works.
This page describes the data type, which is distinct from a particular
instance of that data type. There are multiple ways to access a scene
and its render settings: bpy.data.scenes[0] works but also
bpy.context.scene, screen.scene, scene.background_set, ...

Brecht.

On Mon, Jun 25, 2012 at 7:27 PM, Jordan Miller <jrdnmlr at gmail.com> wrote:
> ok thank you, this is great news. The doc said this is a feature that will NOT be implemented soon so I was trying to find my own way thorugh it.
>
> But how is one supposed to know that:
>
> bpy.types.RenderSettings.border_max_x cannot be called directly? instead it is set at:
>
> bpy.data.scenes[0].render.border_max_x
>
> and so on...?
>
> For example:
> The mouse-over tooltip for the Border checkbox incorrectly lists: RenderSetting.use_border when instead it should specify, I think, bpy.data.scenes[0].render.use_border.
>
> It took me a could hours digging around the internet along with a LOT of trial and error to figure this out (i had to control-space autocomplete each bpy.data variable to find the one I was looking for).
>
> This little bit from the docs is really unhelpful... it says the problem is obvious but doesn't explain all mappings from class to active variable:
> http://www.blender.org/documentation/blender_python_api_2_63_12/info_quickstart.html#data-creation-removal
>
> Soooo confusing!
>
> jordan
>
>
>
>
>
> On Jun 25, 2012, at 6:43 AM, Brecht Van Lommel wrote:
>
>> Hi,
>>
>> Here are the properties:
>> http://www.blender.org/documentation/blender_python_api_2_63_12/bpy.types.RenderSettings.html#bpy.types.RenderSettings.border_max_x
>>
>> This will become a builtin Cycles feature soon though, to render tiled
>> with less memory.
>>
>> Brecht.
>>
>> On Sun, Jun 24, 2012 at 4:36 PM, Jordan Miller <jrdnmlr at gmail.com> wrote:
>>> Hi,
>>>
>>> This works in Cycles!
>>>
>>> I am trying to scale-up my renders for printing poster-size. Obviously I run out of memory quickly with my video card. However, if we could break up the scene into chunks and render those then it would be a lot faster to use GPU since it could fit on the GPU memory.
>>>
>>> My experiments here are true, the use border setting followed by shift-B to define the rendered area. A scene that barely does not fit on my video card DOES fit if I create 4 versions of the .blend file with a shift-B defined quadrant in each one for rendering.
>>>
>>> How do I script the border size option? I found:
>>> RenderSettings.use_border
>>>
>>> But that is a boolean and does not have values for x,y.
>>>
>>> So if we can find the python definition for these then I could add a preference for rendering "Tiles" with cycles that the user could assemble afterwards.
>>>
>>> This could allow crowd-sourcing of Mango rendering, for example, where even weak GPU cards could render pixels for the final movie.
>>>
>>> please help me find how to programmatically set the shift-B border size and position so that we can add this feature to Blender!
>>>
>>> thanks,
>>> jordan
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Bf-cycles mailing list
>>> Bf-cycles at blender.org
>>> http://lists.blender.org/mailman/listinfo/bf-cycles
>> _______________________________________________
>> Bf-cycles mailing list
>> Bf-cycles at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-cycles
>
> _______________________________________________
> Bf-cycles mailing list
> Bf-cycles at blender.org
> http://lists.blender.org/mailman/listinfo/bf-cycles