20,741
edits
Advanced weather: Difference between revisions
Jump to navigation
Jump to search
→Feature requests on the C++ side
| Line 125: | Line 125: | ||
Based on an idea by Hooray, version 0.81 of the local weather package has low-level function calls gathered in a separate Nasal file <b>compat_layer.nas</b>. The idea is that C++ counterparts for these are supplied, along with Nasal structures which check if the Flightgear core has the functionality and call the C++ function if the functionality is there while they use current Nasal implementations if no C++ structures are available, thus ensuring backward compatibility to Flightgear 2.0.0. Anyone interested in porting a structure to C++ could then start to implement one of the functions found there. These functions are: | Based on an idea by Hooray, version 0.81 of the local weather package has low-level function calls gathered in a separate Nasal file <b>compat_layer.nas</b>. The idea is that C++ counterparts for these are supplied, along with Nasal structures which check if the Flightgear core has the functionality and call the C++ function if the functionality is there while they use current Nasal implementations if no C++ structures are available, thus ensuring backward compatibility to Flightgear 2.0.0. Anyone interested in porting a structure to C++ could then start to implement one of the functions found there. These functions are: | ||
=== Terrain related === | |||
* To check for wave conditions far from the original obstacle doesn't work well in Flightgear, because you can't rely on terrain far from your present location being loaded already. So by necessity one has to make it a more local phenomenon. | |||
=== Environment related === | === Environment related === | ||
* 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. | |||
* calls to set the environment (temperature, visibility, turbulence, pressure, dewpoint, thermal lift). It would seem a good idea if the environment subsystem could be structured in such a way as to accept direct input from Nasal via the property tree (and switches its own interpolation routines off) if a particular property is set. | * calls to set the environment (temperature, visibility, turbulence, pressure, dewpoint, thermal lift). It would seem a good idea if the environment subsystem could be structured in such a way as to accept direct input from Nasal via the property tree (and switches its own interpolation routines off) if a particular property is set. | ||
| Line 135: | Line 140: | ||
'''Another note''': There is already a proposal for a related patch [http://flightgear.org/forums/viewtopic.php?f=5&t=7358&st=0&sk=t&sd=a&start=90#p82805] which needs to be reviewed/reworked and hopefully committed at some point. Also, we have talked about other ways for speeding up the whole thing even more: [http://www.flightgear.org/forums/viewtopic.php?f=5&t=7358&st=0&sk=t&sd=a&start=30#p71125]--[[User:Hooray|Hooray]] 12:09, 3 August 2010 (UTC) | '''Another note''': There is already a proposal for a related patch [http://flightgear.org/forums/viewtopic.php?f=5&t=7358&st=0&sk=t&sd=a&start=90#p82805] which needs to be reviewed/reworked and hopefully committed at some point. Also, we have talked about other ways for speeding up the whole thing even more: [http://www.flightgear.org/forums/viewtopic.php?f=5&t=7358&st=0&sk=t&sd=a&start=30#p71125]--[[User:Hooray|Hooray]] 12:09, 3 August 2010 (UTC) | ||
=== Cloud placement === | === Cloud placement === | ||