AI Scenery objects: Difference between revisions
No edit summary |
No edit summary |
||
| Line 24: | Line 24: | ||
* Temporary runtime model files are created on demand for each airport. | * Temporary runtime model files are created on demand for each airport. | ||
This page is about a proof of concept for an alternative way for maintaining animated jetways by uploading animated jetways to the scenery object database similar to other scenery objects and have these controlled by the AI subsystem and a Nasal module <ref>{{cite web | After some discussion on the developer mailing list <ref>{{cite web | ||
|url = https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/CAMcJc7oP_AuXaNDQOF1pTYtSM4pskCDWg1gXpxkKtXaF4LVfLg%40mail.gmail.com/#msg36378569 | |||
|title = <nowiki> Mailing list discussion </nowiki> | |||
|author = <nowiki> ThomasS </nowiki> | |||
|date = July, 2018 | |||
|script_version = 0.40 | |||
}}</ref> the original idea scetched above broadened to a more generic solution, that not only disposes icao.jetways.xml, so the name "AI Scenery Object" arose. So an animated jetway is just one type of an AI Scenery Object. Cranes or bridges might be other types. | |||
This page is about a proof of concept for an alternative way for maintaining animated jetways by uploading animated jetways as AI scenery Object to the scenery object database similar to other scenery objects and have these controlled by the AI subsystem and a Nasal module <ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?f=5&t=34461&sid=4be4c415b0b814080102d632310b3297#p334260 | |url = https://forum.flightgear.org/viewtopic.php?f=5&t=34461&sid=4be4c415b0b814080102d632310b3297#p334260 | ||
|title = <nowiki> Animated Jetways: Type 1 or 2? </nowiki> | |title = <nowiki> Animated Jetways: Type 1 or 2? </nowiki> | ||
| Line 32: | Line 40: | ||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref>. | }}</ref>. | ||
== Requirements == | |||
== Outline == | |||
== References == | == References == | ||
{{Appendix}} | {{Appendix}} | ||
Revision as of 09:09, 8 October 2018
| This article describes content/features that may not yet be available in the latest stable version of FlightGear (2020.3). You may need to install some extra components, use the latest development (Git) version or even rebuild FlightGear from source, possibly from a custom topic branch using special build settings: This feature is scheduled for FlightGear (unknown).  If you'd like to learn more about getting your own ideas into FlightGear, check out Implementing new features for FlightGear. |
| Started in | 07/2018 |
|---|---|
| Description | Providing a way for controlling scenery objects from the scenery objects database by the AI subsystem |
| Contributor(s) | ThomasS (since 07/2018) |
| Status | Under active development as of 07/2018 |
Objective
The currently preferred way for defining animated jetways for an airport is putting the definitions into a ICAO.jetways.xml file and let someone with commit access upload the file to the scenery server for sharing it by TerraSync. But using a single file per airport has a few drawbacks:
- Its difficult to maintain and to evolve the jetways step by step without always modifying the complete file
- It bypasses parts of the well established process for adding objects to the scenery and always requires some manual intervention by a core developer for committing it.
- Temporary runtime model files are created on demand for each airport.
After some discussion on the developer mailing list [1] the original idea scetched above broadened to a more generic solution, that not only disposes icao.jetways.xml, so the name "AI Scenery Object" arose. So an animated jetway is just one type of an AI Scenery Object. Cranes or bridges might be other types.
This page is about a proof of concept for an alternative way for maintaining animated jetways by uploading animated jetways as AI scenery Object to the scenery object database similar to other scenery objects and have these controlled by the AI subsystem and a Nasal module [2].
Requirements
Outline
References
References
|