20,741
edits
Canvas development: Difference between revisions
→Adding new Projections
| Line 2,151: | Line 2,151: | ||
=== Adding new Projections === | === Adding new Projections === | ||
{{Note|Discuss base class that needs to be implemented}} | {{Note|Discuss base class that needs to be implemented}} | ||
that's a coordinate singularity of a (lat/lon) grid and things like your course cease to be well-defined in the vicinity - so you can't expect normal code to work. Usually you need special provisions to deal with such singularities (from my own experience, the Shuttle has four different coordinate systems to switch, and fallback rules what to display when close to a singularity and the AP for liftoff uses a different coordinate grid (based on vectors rather than angles) from the AP later during launch because the launch is done right into the singularity (there's no course defined for vertical ascent) and so one can't steer to any particular course until later). <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/36184377/ | |||
|title = <nowiki> Re: [Flightgear-devel] MP / Autorouter Bugs Observed </nowiki> | |||
|author = <nowiki> Thorsten Renk </nowiki> | |||
|date = Jan 10th, 2018 | |||
|added = Jan 10th, 2018 | |||
|script_version = 0.36 | |||
}}</ref> | |||
{{FGCquote | {{FGCquote | ||