"jr" <cre### [at] gmailcom> wrote:
>
> when I run the beta with '-cc +w400 +h300 +a +rtr +kla', the preview window pops
> up but shows nothing.
>
Those settings work OK in the Windows version.

Do you correctly have *multiple* camera in your scene for rtr and kla to work
properly? (or a #while/#for loop to generate the multiple cameras?) With just a
single camera in such a scene, the parsing/rendering seems to go into an
endless(?) loop-- although I still see a single render of my scene in the
preview, not a blank screen like you mention.

Post a reply to this message

"Kenneth" <kdw### [at] gmailcom> wrote:
> ...With just a
> single camera in such a scene, the parsing/rendering seems to go into an
> endless(?) loop--

I mean an endless loop with the computer chugging away, but doing nothing. The
real-time raytracing feature, when working properly, also generates an endless
looping animation-- but that's with all the new camera positions, one after the
other.

Post a reply to this message

hi,

"Kenneth" <kdw### [at] gmailcom> wrote:
> "jr" <cre### [at] gmailcom> wrote:
> >
> > when I run the beta with '-cc +w400 +h300 +a +rtr +kla', the preview window pops
> > up but shows nothing.
> >
> Those settings work OK in the Windows version.
>
> Do you correctly have *multiple* camera in your scene for rtr and kla to work
> properly? ...

I think so, yes.  the code (and command-line) works fine with one particular
executable (WFP's povr) but not with the official "unofficial" alpha + beta
versions I have.  cheers.


regards, jr.

Post a reply to this message

Rendering a 3.8 version scene which includes functions.inc, I get the 
following parse warning:

"functions.inc" line 167: Parse warning: use of POV-Ray v3.7 keyword 
('deprecated') detected in alleged v3.5 scene.

The only place were version 3.5 is mentioned is precisely at the start 
of functions.inc:

#ifndef(Functions_Inc_Temp)
#declare Functions_Inc_Temp = version;
#version 3.5;
...
#end

At the mentioned line 167 of this /new/ functions.inc shipped with the 
beta, a /new/ if statement has been introduced, not there in previous 
versions:

#if (Functions_Inc_Temp < 3.8)
     #declare deprecated once "f_enneper was broken prior to v3.8; 
results will most likely differ."
              f_enneper = function { internal(18) }
#else
     #declare f_enneper = function { internal(18) }
#end


-- 
Thomas

Post a reply to this message

I still do not understand this parse warning as I do *not* run a version 
3.5 scene. Does it refer to POV-Ray includes which /mention/ version 3.5?
functions.inc seem to be the only include file containing this.

Just a short explanation would be enough about this mysterious warning.

Thanks,

Thomas

Op 19-7-2021 om 14:17 schreef Thomas de Groot:
> Rendering a 3.8 version scene which includes functions.inc, I get the 
> following parse warning:
> 
> "functions.inc" line 167: Parse warning: use of POV-Ray v3.7 keyword 
> ('deprecated') detected in alleged v3.5 scene.
> 
> The only place were version 3.5 is mentioned is precisely at the start 
> of functions.inc:
> 
> #ifndef(Functions_Inc_Temp)
> #declare Functions_Inc_Temp = version;
> #version 3.5;
> ...
> #end
> 
> At the mentioned line 167 of this /new/ functions.inc shipped with the 
> beta, a /new/ if statement has been introduced, not there in previous 
> versions:
> 
> #if (Functions_Inc_Temp < 3.8)
>      #declare deprecated once "f_enneper was broken prior to v3.8; 
> results will most likely differ."
>               f_enneper = function { internal(18) }
> #else
>      #declare f_enneper = function { internal(18) }
> #end
> 
> 


-- 
Thomas

Post a reply to this message

Am 29.07.2021 um 17:45 schrieb Thomas de Groot:
> I still do not understand this parse warning as I do *not* run a version 
> 3.5 scene. Does it refer to POV-Ray includes which /mention/ version 3.5?
> functions.inc seem to be the only include file containing this.
> 
> Just a short explanation would be enough about this mysterious warning.

It's a bug in `functions.inc`: At the start it claims that it needs only 
v3.5, but later it uses the `deprecated` keyword, which wasn't 
introduced until v3.7.

In other words, if someone were to use genuine POV-Ray v3.5, and render 
the scene with that very same include file, they'd get an error message.

The fact that POV-Ray warns about such scenarios is a brand new feature 
of v3.8.0-beta.1.

Post a reply to this message

Op 29/07/2021 om 21:54 schreef clipka:
> Am 29.07.2021 um 17:45 schrieb Thomas de Groot:
>> I still do not understand this parse warning as I do *not* run a 
>> version 3.5 scene. Does it refer to POV-Ray includes which /mention/ 
>> version 3.5?
>> functions.inc seem to be the only include file containing this.
>>
>> Just a short explanation would be enough about this mysterious warning.
> 
> It's a bug in `functions.inc`: At the start it claims that it needs only 
> v3.5, but later it uses the `deprecated` keyword, which wasn't 
> introduced until v3.7.
> 
> In other words, if someone were to use genuine POV-Ray v3.5, and render 
> the scene with that very same include file, they'd get an error message.
> 
> The fact that POV-Ray warns about such scenarios is a brand new feature 
> of v3.8.0-beta.1.

OK. Thanks for this. I shall just close my eyes ;-)

-- 
Thomas

Post a reply to this message

hi,

clipka <ano### [at] anonymousorg> wrote:
> Am 29.07.2021 um 17:45 schrieb Thomas de Groot:
> > I still do not understand this parse warning as I do *not* run a version
> > 3.5 scene. Does it refer to POV-Ray includes which /mention/ version 3.5?
> > functions.inc seem to be the only include file containing this.
> >
> > Just a short explanation would be enough about this mysterious warning.
>
> It's a bug in `functions.inc`: At the start it claims that it needs only
> v3.5, but later it uses the `deprecated` keyword, which wasn't
> introduced until v3.7.

fwiw, same bug/keyword use for 'glass_old.inc'.


regards, jr.

Post a reply to this message