You can play with the sky values in bdg.txt to give more interesting sunset
colours. I don't know what the default numbers are, I've been rolling over
my bdg.txt with each patch update for years now. I did these long ago;
the first was intended to match true sunset colours for midsummer on the
channel, with the sun about 1/5 under the horizon:
Weather_SkyLambda3= 19995260.0
Weather_SkyLambda2= 1754390.0
Weather_SkyLambda1= 1138460.0
Weather_SunLambda3= 0.350
Weather_SunLambda2= 0.423
Weather_SunLambda1= 0.680
Unfortunately those numbers do some violence to the sky colours at midday,
so I have subsequently taken to using these settings, which are a compromise
between good sunsets and sane daylight colours. I'm sure they aren't the optimum,
there's plenty of room for exploration:
Weather_CloudAlbedo= 1.000
Weather_SunGlow= 0.250
Weather_SunFlare= 0.500
Weather_SkyLambda3= 5550000.0
Weather_SkyLambda2= 1604038.0
Weather_SkyLambda1= 1250000.0
Weather_SunLambda3= 0.390
Weather_SunLambda2= 0.497
Weather_SunLambda1= 0.680
Weather_Turbidity= 1.800
Weather_SkyExposure= -0.350
Weather_SkyGamma= 4.700
Weather_SunIntensity= 150.000
Weather_MieG= -1.500
Weather_MMult= 0.0000013
Weather_RMult= 0.018
Weather_SunColor= 1.000
And I should add a brief explanation of how the numbers work, not that we
understood them in any detail:
"The key to tweaking these is that 1,2,3 are R,G,B, and "sun" means the region immediately
around the sun, plus the horizon ( <= possibly only for dawn/dusk); while "sky" is everything
else. Thus my tweak set "sun" to orange. But the two sets of numbers interact with each
other: if you set "sun" blue to zero, you can't seem to get any blue in "sky" no matter how
high a number you use. So, if you mess with the "sun" variables, you'll have to tweak the "sky"
variables to get them back to where they were."
Oh, also, I see you have aliasing (jaggies) showing. If you are using an old
nVidia card, that will happen, regardless of what antialiasing setting you
have, but you can get around it using something other than the BoB2 built
in screen capture. Windows has a capture via alt-printscreen, then use
copy from clipboard to your image editor or viewer after exiting BoB2, but
it will only hold one image, from the last usage of the command. Other
third party screen captures also work, and will do multiple captures per
session with antialiasing, such as IrfanView's, but on my machine that one
always planted a mouse pointer in the exact centre of the image. There
are probably several others out there which will work. I think nVidia solved
their capture problem with the 8000 or 9000 series cards.
Login
Register
FAQ
Search
I'll post a note about that fix over eagle.ru sometime later.
