Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G


Jump to: navigation, search

Advanced weather

35 bytes removed, 17:34, 25 October 2013
Update forum links
== Unification of basic and advanced weather system ==
It is planned to unify the weather systems in FlightGear. Possibly for the upcoming version 3.0. It is therefore needed to improve the usability of the advanced weather configuration system. Join the [http://wwwforum.flightgear.org/forums/viewtopic.php?f=69&t=16630 discussion on this topic in the forums].
== History ==
== Related Discussions ==
* [http://wwwforum.flightgear.org/forums/viewtopic.php?f=5&t=8365 Weather algorithms] (06/2010)* [http://wwwforum.flightgear.org/forums/viewtopic.php?f=5&t=8137 A smart cloud altitude algorithm] (05/2010)* [http://wwwforum.flightgear.org/forums/viewtopic.php?f=5&t=7591 Weather dynamics] (04/2010)
* [http://flightgear.org/forums/viewtopic.php?f=5&t=6968 New thunderstorm AI scenario alpha release] (02/2010)
* [http://flightgear.org/forums/viewtopic.php?f=5&t=7107 Cirrus sky (download link in first post)] (02/2010)
== Feature requests on the C++ side ==
Intended as a base for discussions on how to implement particular features in the C++ code. Also see [http://wwwforum.flightgear.org/forums/viewtopic.php?f=5&t=8365 Weather algorithms discussion] from 06/2010.
As of version 0.81, the local weather system runs on a high-end system, but has problems on slower machines and could use performance boosts from implementing some features which currently are done from Nasal in C++. Guiding principles for that should be '''performance''', '''accessibility''', a '''clear structure''' and '''backward compatibility'''. The decision if a particular function should be implemented on the C++ level should be investigated with these in mind - usually performance is served better from C++, but Nasal structures remain more accessible. For example, cloud configurations (assembling a vector of coordinates where to place clouds) can usually be done in Nasal in a single frame and thus the performance boost when porting to C++ is marginal. On the other hand, cloud configurations are crated by functions which turn a set of parameters into cloud positions, and it is useful to have quick access to the parameters and functions to tune the system to reproduce a real sky better and better without the need to recompile the code. Thus, cloud configuration computations are an example for structures which should probably not be ported to C++.
* (06/2012) Sun is always painted on top of the skydome, you even see it through what is supposed to be terrain from high altitude. That's an issue for the maintainer of the sun code, it isn't curable via Nasal. See [https://code.google.com/p/flightgear-bugs/issues/detail?id=788&sort=-id&colspec=ID%20Type%20Status%20Priority%20Summary%20Aircraft%20Milestone].
* expose the atmospheric model to the property tree (or Nasal) [http://wwwforum.flightgear.org/forums/viewtopic.php?f=30&t=8743#p86387] [http://wwwforum.flightgear.org/forums/viewtopic.php?f=5&t=7358&st=0&sk=t&sd=a&start=15#p70714] [http://www.av8n.com/fly/fgfs/README.altimetry.html] [http://www.av8n.com/physics/altimetry.htm]
* Once I cross the mountaintops, some system switches on turbulence (I suspect ridge lift, since I could not find any other property which would create turbulence). That's bad, because wave lift isn't turbulent at all. To disable the ridge lift system, set '''/environment/ridge-lift/enabled''' to 0

Navigation menu