Here is the place to share ideas and feature requests related to tutorial/mission system.
Current wish/to do list (will be periodically updated according to your feedback):
Johan G wrote:You beat me to it. I had the intention to post it here, so I settle for the YouTube version.
Hooray wrote:we may need to add some features, especially for piloting/flying, i.e. route manager/waypoint awareness, and ability to track course/bearing to certain positions (via geo.nas) - e.g. for navigating via VORs, NDBs or DMEs
Currently, the tutorial system doesn't have any built-in support for "fly to the SFO VOR" - but once we have that, we could even support flying holding patterns ( "fly to sfo maintain 8000, hold left on the 180 radial"). Such things would be useful also for virtual flight instruction - but also for an ATC adventure, i.e. where a virtual ATC controller guides pilots down a GCA path using radar vectors and AGL altitudes
ludomotico wrote in Wed Apr 16, 2014 5:44 pm:I agree most of the code is already there by extending the tutorial system and a bit of nasal.
The only thing I'm not sure is how to load "mission files". Should missions be defined in the -set.xml of each aircraft? Should they be defined as a scenario? A new entry in the menu? How could we load a mission from fgrun, for example?
<?xml version="1.0" encoding="UTF-8"?>
<!-- list.xml -->
<PropertyList>
<tutorial include="Helicopter_missions/Oil-Rig-Landing/Oil-Rig-Landing.xml"/>
<tutorial include="Helicopter_missions/helicopter1.xml"/>
<tutorial include="helicopter2.xml"/>
<!-- ... -->
</PropertyList>
<PropertyList>
<mission include="Helicopter_tutorials/hovering_tutorial.xml"/>
<mission include="Helicopter_missions/Oil-Rig-Landing/Oil-Rig-Landing.xml"/>
</PropertyList>
The tutorials are registered in fg-root/tutorials/list.xml
== Missions ==
* power line maintenance
* equipment transportation
* banner pickup/towing
* precision landing
Hooray wrote in Wed Apr 16, 2014 5:24 pm:The tutorial system itself already has support for placing 3D models in arbitrary locations, no matter if it's a vessel, climber or a vehicle: http://wiki.flightgear.org/Tutorials#Models
But those are all static currently, so we would need to use this in combination with an AI scenario, which is not overly flexible, and also not that easy to deploy.
<model>
<path>Aircraft/Generic/Human/Models/npc0.xml</path>
<longitude-deg-prop>/sim/model/npc/longitude-deg</longitude-deg-prop>
<latitude-deg-prop>/sim/model/npc/latitude-deg</latitude-deg-prop>
<elevation-ft-prop>/sim/model/npc/altitude-ft</elevation-ft-prop>
</model>
<!--NPC0 -->
<set>
<property>/sim/model/npc/character</property>
<value>2</value>
</set>
<set>
<property>/sim/model/npc/gender</property>
<value>0</value>
</set>
<set>
<property>/sim/model/npc/outfit</property>
<value>1</value>
</set>
<set>
<property>/sim/model/npc/hair</property>
<value>1</value>
</set>
<set>
<property>/sim/model/npc/headgear</property>
<value>3</value>
</set>
<set>
<property>/sim/model/npc/mask</property>
<value>1</value>
</set>
<set>
<property>/sim/model/npc/toolr</property>
<value>0</value>
</set>
<set>
<property>/sim/model/npc/longitude-deg</property>
<value>-0.5419</value>
</set>
<set>
<property>/sim/model/npc/latitude-deg</property>
<value>38.28027048</value>
</set>
<set>
<property>/sim/model/npc/altitude-ft</property>
<value>35</value>
</set>
<nasal>
<script>
io.read_properties("Aircraft/Generic/Human/Models/Poses/help.xml", "sim/model/npc[0]/pose");
</script>
</nasal>
Return to Tutorials and missions
Users browsing this forum: No registered users and 1 guest