|
|
On 07/02/2018 10:34, Bald Eagle wrote:
> Mike Horvath <mik### [at] gmailcom> wrote:
>> Does `#version 3.7` have to appear at the very top of a scene file? Or
>> can I store it as a variable or use it in a condition first? E.g.
>>
>>
>> #declare MyVersion = version;
>> #if (something = true)
>> #version 3.7
>> #else
>> #version 3.6
>> #end
>
> Both.
> POV-Ray expects to fins a #version directive (and a global settings block with
> gamma) at the beginning of every file, and will issue a warning is those are not
> present.
> You can, however, then go on to change the version the parser uses to interpret
> your code by issuing another #version directive.
> IIRC, this is done with some include files or macros, where the current version
> is stored like you do above, and then after that block of code is run, the
> version is restored by
> #version MyVersion
>
> Hope that makes sense.
>
>
Parse Warning: This scene had other declarations preceding the first
#version directive. Please be aware that as of Pov-Ray 3.7, un1ess
a1ready specified via an INI option, a #version is expected as the first
declaration in a scene file. If this is not done, POV—Ray may apply
compatibility settings to some features that are intended to make pre -
3.7 scenes render as designed. You are strongly encouraged to add a
#version statement to the scene to make your intent c1ear. Future
versions of Pov-Ray may make the presence of a #ver51on mandatory.
Which means it might not work in the future.
--
Regards
Stephen
Post a reply to this message
|
|