20,741
edits
Using OSM Vector Data in FlightGear: Difference between revisions
Jump to navigation
Jump to search
m
Using OSM Vector Data in FlightGear (view source)
Revision as of 20:31, 13 January 2015
, 13 January 2015→Status (01/2015)
| Line 47: | Line 47: | ||
|author=<nowiki>stuart</nowiki> | |author=<nowiki>stuart</nowiki> | ||
|date=<nowiki>Tue Jan 13</nowiki> | |date=<nowiki>Tue Jan 13</nowiki> | ||
}} | |||
}} | |||
{{FGCquote | |||
|I've written a little tool that<br/> | |||
does the following:<br/> | |||
1) Loads all the .ac files in the STG file passed in as an argument<br/> | |||
2) Runs the osgUtil::Optimizer to merge all the textures together, build a<br/> | |||
quad tree and optimize the meshes<br/> | |||
3) Outputs the result as a native osg format (.osgb)<br/> | |||
4) Writes a new STG file with the .ac model references removed, and the<br/> | |||
.osgb file added.<br/> | |||
<br/> | |||
The idea is that this could be used within our scenery generation toolchain<br/> | |||
to generate a more efficient set of static tile objects. | |||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33230184/ | |||
|title=<nowiki>[Flightgear-devel] STG model merge tool</nowiki> | |||
|author=<nowiki>Stuart Buchanan</nowiki> | |||
|date=<nowiki>2015-01-13</nowiki> | |||
}} | }} | ||
}} | }} | ||