|
 |
clipka <ano### [at] anonymous org> 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
Between the previous build I used (1.37.0.0-beta7) and this one, the background
color got broken:
background {rgbt<0, 0.00218, 0.0509, 0>}
now gives a black background instead of a blue one. or is this a planned change
of behaviour?
Post a reply to this message
|
|
|
|
Am 04.02.2015 um 18:32 schrieb Mr:
> Between the previous build I used (1.37.0.0-beta7) and this one, the background
> color got broken:
>
> background {rgbt<0, 0.00218, 0.0509, 0>}
>
> now gives a black background instead of a blue one. or is this a planned change
> of behaviour?
Not planned; I'll look into it soonish.
Post a reply to this message
|
|
|
|
Am 05.02.2015 um 05:05 schrieb clipka:
> Am 04.02.2015 um 18:32 schrieb Mr:
>
>> Between the previous build I used (1.37.0.0-beta7) and this one, the
>> background
>> color got broken:
>>
>> background {rgbt<0, 0.00218, 0.0509, 0>}
>>
>> now gives a black background instead of a blue one. or is this a
>> planned change
>> of behaviour?
>
> Not planned; I'll look into it soonish.
Culprit found, fix in progress.
Post a reply to this message
|
|
