20,741
edits
Canvas MapStructure: Difference between revisions
Jump to navigation
Jump to search
m
→Performance
mNo edit summary |
m (→Performance) |
||
| Line 283: | Line 283: | ||
[[File:MapStructure-ND-Profiling.png|thumb|MapStructure/NavDisplay testbed with integrated profiling support for each layer]] | [[File:MapStructure-ND-Profiling.png|thumb|MapStructure/NavDisplay testbed with integrated profiling support for each layer]] | ||
{{FGCquote | |||
|We've already fixed that in the (old) map dialog, by using an azimuthal equidistant projection (see [[images/7/71/Map_north_pole_route.jpg|screenshot]]). Porting the projection to Canvas is on my todo list. Such a projection is much much better for navigational use. | |||
Curves in routes are not calculated by Canvas, nor by the ND though. It's the route manager that splits up a route in segments in order to get smooth transitions. | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=227838#p227838 | |||
|title=<nowiki>Re: Canvas ND performance issues with route-manager</nowiki> | |||
|author=<nowiki>Gijs</nowiki> | |||
|date=<nowiki>Tue Dec 23</nowiki> | |||
}} | |||
}} | |||
These are the most likely jobs ahead to improve MapStructure performance: | These are the most likely jobs ahead to improve MapStructure performance: | ||
* adopt our caching scheme (i.e. referencing precreated raster images rather than having hundreds of openVG paths) {{Progressbar|80}} | * adopt our caching scheme (i.e. referencing precreated raster images rather than having hundreds of openVG paths) {{Progressbar|80}} | ||