Am 23.05.2018 um 18:53 schrieb Stephen:

>>> Which reminds me. I use that facility to overwrite the version number
>>> B3D exports by declaring it after the first one. Will that workaround
>>> still work?
>>
>> Uh... please elaborate. How would the resulting scene file look like?
>>
> 
> #version 3.6;
> 
> 
> //------- Scene Raw Script Begin -------
> #version 3.7 ;
> //------- Scene Raw Script End ---------
> 
> [The rest of the scene...]

If `#version 3.6;` is the very first statement in the scene, then that's
fine.(*)

If there's anything before that (other than whitespace and/or comments),
it is still fine unless you replace `#version 3.7;` with `#version 3.8;`.


(* In the sense that you won't get a parse error. It may have side
effects, e.g. the new v3.8 default values currently don't apply unless
you specify `#version 3.8` at the very first line. I intend to change
that though.)

Post a reply to this message