20,741
edits
Startup Profiles: Difference between revisions
Jump to navigation
Jump to search
→Motivation
(→Status) |
|||
| Line 14: | Line 14: | ||
}} | }} | ||
</ref> | </ref> | ||
The position init code is a little complex, to allow for starting on a carrier and some other cases, and ideally we would do it from script, but unfortunately there's some technical limitations on doing that. (Not insurmountable, but not quick either). Adding more cases to the position-init code is certainly doable - one suggestion I made some time ago, is when MP is active, to default to starting at a free parking position instead of on a runway. (When no startup position is provided at all). This would avoid people accidentally starting on the runway in MP events, which would be a big usability win. When no parking positions are defined, AI traffic defaults to the 'airport centre' location. Selection a taxiway parallel to the active runway is possible, but for complex airport layouts I can imagine many ways this logic could fail. Personally I think it would be more robust to stick to picking parking positions, and otherwise using the airport centre, because it would encourage people to add the parking position data :) I anyone wants to work on this, it would be a self-contained function in position-init code, just ask here for any questions. All the pieces certainly exist - the taxiways, parking locations and runways for the airport are all accessible. | |||
<ref>{{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/31628611/ | |||
| title = <nowiki>Re: [Flightgear-devel] Aircraft positioning on the runway</nowiki> | |||
| author = <nowiki>James Turner</nowiki> | |||
| date = Nov 12th, 2013 | |||
| added = Nov 12th, 2013 | |||
| script_version = 0.25 | |||
}} | |||
</ref> | |||
<references/> | <references/> | ||
== Status == | == Status == | ||
{{FGCquote | {{FGCquote | ||