[Bf-committers] Do drivers have to be blocked as python scripts?

Mike Pan mike.c.pan at gmail.com
Fri May 23 22:20:54 CEST 2014


Agree with Daniel. Perhaps a 'Halt on Error' checkbooks that prevent the
rendering if there are any missing libraries, textures or disabled
scripts.  This should be helpful in a studio environment.

M
On May 23, 2014 1:13 PM, "Daniel Salazar - patazstudio.com" <
zanqdo at gmail.com> wrote:

> I'm happy this is getting some attention. Apart from the usability
> issues this sheds some light into another problem which is: Blender
> should not render crippled scenes ever. At least on background mode
> Blender needs to stop if drives aren't functioning and/or if textures
> are missing. The fact that it happily continues is making us loose
> valuable render time.
> Daniel Salazar
> patazstudio.com
>
>
> On Fri, May 23, 2014 at 1:50 PM, patrick boelens <p_boelens at msn.com>
> wrote:
> > Imho doing something like this will only worsen the situation. Right now
> a lot of .blends fail entirely, leaving many users to wonder why. This
> sucks. If we were to allow *some* expressions, but not others, potentially
> only half a .blend will fail. This sucks even more.
> >
> > At least when everything breaks it's clear there is an underlying
> reason; whether that is a user preference as is the case here, a bug in
> Blender or an unsupported version or whatever. At least more experienced
> users may quickly realize they did not allow script execution for this
> .blend. If only, say, one out of ten drivers fail, I would imagine it being
> tempting to go look for the cause of this at the drivers themselves;
> perhaps someone accidentally made a typo in an expression?
> >
> > I'm not sure if this has been proposed before, but would it be possible
> to show a pop-up when opening a (external) .blend file for the first time?
> Something similar to what OSX does when opening a freshly downloaded app or
> document:
> >
> > ------------------------------------------
> > "This .blend was created on another machine and contains executable code
> that could be harmful. Do you wish to allow Blender to execute these
> scripts?"
> >
> > [Yes | No]
> > ------------------------------------------
> >
> > It wouldn't solve the issue for render farms, but would at least provide
> clearity (as well as a much improved sense of control!) to the user.
> >
> > Just my two cents.
> >
> > Cheers,
> > Patrick
> >
> >> From: pildanovak at post.cz
> >> To: bf-committers at blender.org
> >> CC: bf-committers at blender.org
> >> Date: Fri, 23 May 2014 17:57:31 +0200
> >> Subject: [Bf-committers] Do drivers have to be blocked as python
> scripts?
> >>
> >> thanks for the reactions.
> >> From the proposed solution I think that most sane solution would be some
> >> limitation for the one-line expressions, assumably all of those which
> Joshua
> >> proposed.
> >>
> >>
> >>
> >>
> >> Maybe there is a simple way to put all these limitations into a simple
> >> string-checking operation, just check if expression does not have:
> >>
> >> anything else but driver vars, operators, math functions(this might be
> the
> >> complex part, to define what should be included in this.)...
> >>
> >>
> >>
> >>
> >> I mean- rather check if there's what is allowed, then you don't have to
> care
> >> what all should be forbidden, because that is everything else...
> >>
> >>
> >>
> >>
> >> Of course, this can again lead to similar situation - an artist does
> >> something not allowed, he is again stuck with not knowing what is wrong
> >>
> >> (e.g. on the renderfarm), but I assume it would be much less cases. I
> cannot
> >> currently imagine creative cases which would end like this.
> >>
> >>
> >>
> >>
> >> Regards
> >>
> >> Vilem
> >>
> >>
> >>
> >> _______________________________________________
> >> Bf-committers mailing list
> >> Bf-committers at blender.org
> >> http://lists.blender.org/mailman/listinfo/bf-committers
> >
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>


More information about the Bf-committers mailing list