First again sorry when it sounded like rant.
But I must admit I was dissapointed seeing the results on my system here.
> Having said that:
> To the best of my ability to determine from the screenshots, the skydome > shader doesn't work for you (for some yet to be determined reason). As a > result, you can see no haze and no change in the sky when on the ground, > because the haze from that position would affect mainly the skydome.
> Since we're looking at close hills and buildings in your shots, the
> differences in fog for the terrain are not really apparent.
> As you go to high altitude (and presumably good visibility), more and
> more of the haze you see is created by the terrain shader rather than
> the skydome shader, which is why I'm guessing you see better results at > high altitude (but then, there should actually be a visible mismatch
> between sky and terrain if I am correct).
Thanks for that detailed explanation!
I didn't see any error messages in the console so I guessed there shoulden't be any shader-problem, but good to know that there should be a change to see from the ground.
> Actually, no. All that needs to be on is the skydome shader button, no
> matter altitude or shader settings. When you move water or landmass
> above 4, the detailed version of the shaders come on. It is possible
> that the non-detailed version of the shader doesn't run for you either
>(Emilian told me yesterday of some implementation-specific things which
> my nVidia unfortunately tolerates without complaint). So my second
> guess is that you don't have an nVidia card.
I actually have a new nVidia Geforce GTX460 with 1GB RAM. So that should be not the problem.
I have tried with the skydome shader button on, and the effect was even worse. All colors went dull.....
So indeed for any reasons the shader seems not to work here.
> The GUI is actually rather fool-proof - it switches almost everything
> which is not compatible with the scheme off no matter where the sliders > are and parses only the sliders which are implemented. Your problem is
> not GUI related.
After your description it seems indeed so.
> As I've said a few times on this list already, the scheme runs with
> basic weather in principle, but the default settings may not be
> appropriate for the actual weather conditions. It's no technical
> difficulty to change these, but this requires decisions which I don't
> want to make without any feedback from the maintainers of Basic Weather.
Which should be no problem, as from reading here on the list from time to time I can see that it is even wished to make this work available for Default Weather as well. Not all people can run Advanced Weather without having a bigger unusuable fps impact; on my system here (DualCore 2,6Ghz with 4 GB RA) framerates are now worse than with Default Weather. (That was different to last autumn...)
> I've done by now about 100 hours of flight in the scheme at pretty much > all possible times, weather conditions and altitudes ranging from zero
> to 150 km. When working correctly, it is probably the most seamless
> scheme Flightgear ever had (the default scheme doesn't do suborbital
> flight correctly).
I can still remember my first and second flight as pax in a glider 15 years ago. The scattering effect was even visible from 1000-1500ft AGL, visibility wasn't that great as you show in your screenshots. (less than 100km visibility)
I actually had the impression from the various sceenshots and my own experience that it only works in higher altitudes.
Sorry for misinterpreting.
> So what I would like you to do is:
> a) watch the console for any error message from shaders trying to
> compile but not succeeding
> b) get me a screenshot from ~20.000 ft with good visibility over land
> facing the rising sun at dawn with skydome shader on and landmass shader > on 3
> c) do the same exercise with landmass slider set to 4
Good, I will provide this this evening/ tomorrow, as I'm probably not at the computer until later evening today.