20,741
edits
Using OSM Vector Data in FlightGear: Difference between revisions
Jump to navigation
Jump to search
Using OSM Vector Data in FlightGear (view source)
Revision as of 20:40, 30 January 2014
, 30 January 2014→Random Buildings Scripting Interface (Hooray, Thorsten)
m (→Background: http://forum.flightgear.org/viewtopic.php?f=5&t=16083&hilit=&start=15#p155789) |
|||
| Line 57: | Line 57: | ||
And have better access to the placement heuristics, or rather the underlying criteria would be great. That's not just related to "materials" anymore, but also access to "ground networks", such as roads, rivers, railways. | And have better access to the placement heuristics, or rather the underlying criteria would be great. That's not just related to "materials" anymore, but also access to "ground networks", such as roads, rivers, railways. | ||
The good thing is, adding a Nasal interface to make existing C++ code accessible is fairly trivial and much simpler than writing the original backend code. And this is clearly not a task that needs to be done by the developer of the original C++ code, as can be seen by all the existing Nasal extension functions, most of which were added by people who didn't really write the corresponding backend code. | |||
A Nasal script that may query a scenery tile and get detailed information on these properties, could come up with the heuristics to place models realistically. | A Nasal script that may query a scenery tile and get detailed information on these properties, could come up with the heuristics to place models realistically. | ||