"Mr" <nomail@nomail> wrote:
> clipka <ano### [at] anonymousorg> wrote:
> > Am 31.01.2015 um 09:25 schrieb clipka:
> > > Am 27.01.2015 um 09:34 schrieb Mr:
> > >> Hi, there is something I want to do with the version directive, could you
> > >> confirm it's possible? I want to add some options to a texture which are
> > >> specific
> > >> to uberpov in a scene, but still be able to run it with pov 3.7 just
> > >> ignoring
> > >> them. would it be possible?
> > >
> > > Not yet, but I'm currently building UberPOV v1.37.1.0-beta.9, which will
> > > auto-define a variable for this purpose, allowing you to use the
> > > following procedure for feature detection:
> >
> > There. Dunnit:
> >
> > https://github.com/UberPOV/UberPOV/releases/tag/v1.37.1.0-beta.9
>
> Just tested and it works like a charm, that's exactly what I meant. Thank You!

However, what I have so far in the exporter is that it tests for the string
"uber" in the name of the engine found and if so, activates the plain writing of
the feature and this keeps a cleaner readable pov scene file with less
conditions. at the price of some more complex Python, so now I'm hesitating to
implement this procedure instead, what do you think? probably this is more
reliable and futureproof?

Post a reply to this message