381
edits
Advanced weather: Difference between revisions
m
→Feature requests on the C++ side: work in progress
No edit summary |
|||
| Line 115: | Line 115: | ||
* 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. | ||
'''Note''': This is currently work in progress. --[[User:T3r|T3r]] 11:17, 3 August 2010 (UTC) | |||
* interactions with the terrain - chiefly samling terrain elevation for large vectors of coordinates | * interactions with the terrain - chiefly samling terrain elevation for large vectors of coordinates | ||
'''Note''': This is currently work in progress. --[[User:T3r|T3r]] 11:17, 3 August 2010 (UTC) | |||
* calls to place cloud models into the scenery, to remove them and to change their position. Compared with the standard Flightgear 3d clouds, placing and moving models from Nasal seems exceedingly slow. However, local weather uses some features for which it is not obvious if they are supported by the way the standard 3d clouds are implemented. These are: | * calls to place cloud models into the scenery, to remove them and to change their position. Compared with the standard Flightgear 3d clouds, placing and moving models from Nasal seems exceedingly slow. However, local weather uses some features for which it is not obvious if they are supported by the way the standard 3d clouds are implemented. These are: | ||