20,741
edits
Canvas tile element: Difference between revisions
Jump to navigation
Jump to search
→Problem
No edit summary |
|||
| Line 68: | Line 68: | ||
More and more Airports that have different airport data on the FG Map & Route Manager. Route Manager data seems to agree with other map sources like Sky Vector. Does FG Map get updated from independent sources like Sky Vector & others.<ref>https://forum.flightgear.org/viewtopic.php?f=25&t=37589&p=369707#p369705</ref> | More and more Airports that have different airport data on the FG Map & Route Manager. Route Manager data seems to agree with other map sources like Sky Vector. Does FG Map get updated from independent sources like Sky Vector & others.<ref>https://forum.flightgear.org/viewtopic.php?f=25&t=37589&p=369707#p369705</ref> | ||
== About setPixel() == | |||
Drawing an entire image via setPixel calls from Nasal (for terrain / wxr radar overlays by any chance?) will also be slow,i n which case, it might be better to make these '''special image layers''' which are computed by C++ code, so they can be updated efficiently.<ref>https://sourceforge.net/p/flightgear/mailman/message/36483136/</ref> | |||
Obviously, it's a valid use-case, i.e. creating a ‘scanned’ terrain radar, WXR or similar overlays on Canvas, no argument there, where defining a raster via paths is pretty heavyweight for frequent updating. | |||
<ref>https://sourceforge.net/p/flightgear/mailman/message/36483231/</ref> | |||
For features like: | |||
* Inverse synthetic-aperture radar | |||
* Synthetic-aperture radar | |||
* Ground radar | |||
* Ground radar for moving objects | |||
But once we got capability for modifying canvas images real-time or through some other method like fragment shader, it will be usable for many things, for example wxr radar etc etc.<ref>https://sourceforge.net/p/flightgear/mailman/message/36484679/</ref> | |||
Originally, radar altimeter was a big CPU hit, because it does a ‘scanned’ set of 3D ground intersections (over a range of angles in two axes) at the full FDM rate (120Hz), and this becomes significant number of triangle intersections.<ref>https://sourceforge.net/p/flightgear/mailman/message/36484933/</ref> | |||
This kind of feature would be the prerequisite to get a working TERRain mode on the 737 MAP display.<ref>https://sourceforge.net/p/flightgear/mailman/message/36579110/</ref> | |||
== Status == | == Status == | ||