Here is an attempt of using SetAmbientBrightness for implementing time of day again (instead of Gamma).
For me the updating is instant and does not present any problem, would calling this function a lot present any problems?
Known issues: the lava brightness changes with time of day as well.
I hereby license the file ambientnight.png under the CC-BY license
For me the updating is instant and does not present any problem, would calling this function a lot present any problems?
Known issues: the lava brightness changes with time of day as well.
I hereby license the file ambientnight.png under the CC-BY license
I remember when I did/adjusted the SetGamma-part of the day/night cycle that I carefully balanced the color of the ambient light - the night is bluish dark, the dusk is quite red, the dawn is blueish-violet. I would be very sad if we lost that.
The goal should be, in my opinion, to replace SetGamma with SetAmbientLighting (or similar); to be able to tint the ambience color.
Why do you think that using SetAmbientBrightness would cause performance problems?
The goal should be, in my opinion, to replace SetGamma with SetAmbientLighting (or similar); to be able to tint the ambience color.
Why do you think that using SetAmbientBrightness would cause performance problems?
>Why do you think that using SetAmbientBrightness would cause performance problems?
See Sven's reply. Apparently it is not :)
The color spectrum will stay as it is (the sky is still colored), Just that gamma will be removed for now (it already was due to lag issues on linux..., or my machine at least). We can easily reimplement it when it works with the ambient lightning.
If no one objects to the changes here I will put them into master somewhen this week.
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill