[Bf-committers] Getting Cycles to update in viewport when property changes

[Smells Like Donkey]

Ok that explains why I couldn’t get it to work. The use case is that I’m implementing light linking using the grouping mechanism and I needed a place to put some controls for it. After talking with my client, we chose to put this on the groups themselves. But since this parameter changes lighting, it has to cause a viewport update.

Thanks!
Tod.

> On Sep 22, 2015, at 11:55 AM, Sergey Sharybin <sergey.vfx at gmail.com> wrote:
> 
> The idea is that any render engine will be triggered for re-render or
> update when data which affects actual render is changed. This is handled
> via dependency graph, not via notifier system.
> 
> I also not sure why custom property which was manually created will have
> affect on render results.
> 
> One of the possible hacks here to force viewport re-render is to tag
> related object with 'object.update_tag()' tho.
> 
> On Tue, Sep 22, 2015 at 6:51 PM, Smells Like Donkey <
> contact at smellslikedonkey.com> wrote:
> 
>> HI,
>> 
>> I’ve added a property on the groups that, when changed, needs to update
>> the viewport (Cycles render border or whatever) and I can’t get that to
>> happen. I have added an RNA enum property and I suspect that the magic
>> would have to happen in a line like this:
>> 
>>        RNA_def_property_update(prop, NC_OBJECT | ND_DRAW, NULL);
>> 
>> but I can’t get it to work. Any ideas on how I can force an update? Am I
>> using the wrong combination of flags? I tried a bunch but didn’t hit upon
>> the right one.
>> 
>> Thanks,
>> Tod.
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>> 
> 
> 
> 
> -- 
> With best regards, Sergey Sharybin
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers