On 11/14/19 11:58 PM, Dick Balaska wrote:
> On 11/14/19 7:26 AM, William F Pokorny wrote:
> 
>>
>> Have you tried changing the default ambient back to 0.1 when changing 
>> your version to 3.8?
> 
> The global ambient_light is silently ignored if the #version is 3.8
> 
> I used the Basic Scene 01 - Checkered Plane template
> and added a Wire_Box.  Then at the top changed these 3 lines:
> 
> #version 3.8;
> global_settings{ assumed_gamma 1.7 ambient_light 5.0}
> //#default{ finish{ ambient 0.1 diffuse 0.9 }}
> 
> If the version is 3.7, then that ambient_light 5.0 washes everything 
> right out.  If the version is 3.8, it matters not what I set that number 
> to.
> 
> So I tried
> 
> global_settings{ assumed_gamma 1.7 }
> #default{ finish{ ambient 0.1 }}
> 
> This does look a lot like the effect I want, after a couple of tests on 
> my movie.  However, I am greeted with a plethora of:
> 
> Parse Warning: Scene language version changed after a 'default' 
> statement. The changes in defaults normally associated with the language 
> version change are not applied.
> 
> because the standard includes push the version, change to 3.5, pop the 
> version.
> 
> sigh.
> 

Hey. Sorry, I should've written out 'default{ finish{ ambient 0.1 }}' 
(1) to make clear what's needed if using #version 3.8 and wanting to 
match the 3.7 finish ambient behavior.

The ambient_light color has an effect only when a texture's ambient 
setting is > 0.0 and so has no effect anywhere the v3.8 default ambient 
0 finish is used.

Those parse warnings showed up in one of the last updates and I join you 
in not being a fan of the warning in it's current form. It's very noisy 
in typical use. I worked recently a little in v3.8 with Norbert's 
assumed_gamma scene which included stdinc.inc - and yuck. If the warning 
could not warn when an alternate version is detected but the original 
restored before exiting an include file - or the main file - it would be 
better(2).

Bill P.

(1) - Christoph recommends using default {} over #default {}.

(2) - I recall no discussion around the addition of this parser check 
and warning before its introduction. Perhaps Christoph was thinking all 
the shipped includes would be updated to version 3.8 before any v3.8 
release so those wouldn't be an issue for this warning. I don't know.

Post a reply to this message