hiker {l Wrote}:I've added support for weather settings to the track exporter. I also converted fog color from [0.0,1.0] to [0,255], before noticing that you already do this for sky-color. Now I am a bit confused
I don't care where we do it, but it should be done in the same program
First off let me say, unequivocally, that the browser should supply the correct value. If it doesn't it's my problem to solve.
A guiding principle in the browser is that it doesn't change any property until it is... changed. Even more so: The properties that have not yet been changed from it's default value aren't even
created. It works similar to XSD vs. XML. In the XSD a node is defined with a default value, but that doesn't mean it has to be present in the corresponding XML.
So my guess is that the value has been set with the old version of the browser (set to 0.0,0.0,1.0) and hasn't been changed since (which automatically changes it to 256,256,256 format)... If it has been changed and it's still in the 1.0,1.0,1.0 format this is a bug I need to squash.
Also just like XSD you can define types. Both fog-color and sky-color are defined as type_COLOUR, and therefore handled exactly the same.
hiker {l Wrote}:I also added animated textures for water nodes (identical to animated textures in the normal track). But I think that this is not yet supported by the browser (or did I miss something)?
There is
not supported and not
supported. The datamodel of the browser isn't configured to allow water objects to be animated. It's a question of changing the proverbial XSD.