Difference between revisions of "User:Texnicer/devblog"

From FlightGear wiki
Jump to: navigation, search
m (Adding the model to the aircraft, positioning)
m
Line 60: Line 60:
 
* hence the menu route manager is not working yet  
 
* hence the menu route manager is not working yet  
 
* routes must be added manually into garmin196
 
* routes must be added manually into garmin196
 +
 +
 +
== Adding an internal view to an existing aircraft ==
 +
* I started copying a local draft of my aircraft. ''hint: adding some id to the name string helps to find your version in the aircraft list at startup''
 +
* The directory for that draft needs to be in a directory published to the starter/launcher and needs to be added if not already done.
 +
* I started FlightGear using my fork/draft. Using the mouse, LCTRL, RMB combination I navigated to the desired viewpoint (or is it point of view?).
 +
* F10 menu: DEBUG -> show property browser -> /sim/current-view
 +
* I found the view-definitions of my draft using the OS' console in the aircraft base folder:
 +
  $ grep -winr . -e 'view n=' 
 +
''note: for the DR400 the views are stored in /nasal/view.xml which is not default IMHO''

Revision as of 15:34, 26 March 2020

Adding a existing component to an existing aircraft

On march 25, 2020 I was asked via mumble, if I could add the garmin196 to the Seneca II, hence the AP is not charming. Here ist what I did, an how I did it.

Creating a working copy of the aircraft

At first I aquired the Aircraft. It's part of the sourceforge/svn-repository.

I got the plane searching throught FGADDON/AIRCRAFT (https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/) using the SVN system.

   $ svn checkout https://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/SenecaII

note: sourceforge does not support the correct svn-codeline, you need to correct the path starting after trunk'

Locating the system to add

I went into my system's Flightgear root directory $FG_ROOT - which is nice to know. On ubuntu and DeBIAN systems it is likely to be found in:
/usr/share/games/flightgear
  $ cd /usr/share/games/flightgear/

Hence I looked for garmin196 invoking a full recursive file-search

 me@machine:/usr/share/games/flightgear/$ ls -R | grep -A1 -i garmin196

and I figured that the device's files are located in /Aircraft/Instrument-3d/garmin196

Understanding the components of the system

Adding the model to the aircraft, positioning

note: understanding the euclidian space, the axis, the system's origin, helps alot placing the model roughly and visual in the cockpit. finetuning can be done while correcting the .xml file being in the simulator and using the "debug"-menu and "reload model" once and again.

in /Models/SenecaII.xml:

	<model> 
		<path>Aircraft/Instruments-3d/garmin196/garmin196.xml</path>
		<offsets> 
			<heading-deg>-40</heading-deg>
			<x-m>-1.945</x-m>
			<y-m>0.15</y-m>
			<z-m>1.65</z-m>
		</offsets>
	</model>
garmin196 added to SenecaII

Implementing the functionality

in /SenecaII-base.xml: (im Block "nasal")

        <garmin196>
		<file>Aircraft/Instruments-3d/garmin196/garmin196.nas</file>
	</garmin196>

Adapting, Adding, Extending

  • the autopilot menu is not working yet
  • hence the menu route manager is not working yet
  • routes must be added manually into garmin196


Adding an internal view to an existing aircraft

  • I started copying a local draft of my aircraft. hint: adding some id to the name string helps to find your version in the aircraft list at startup
  • The directory for that draft needs to be in a directory published to the starter/launcher and needs to be added if not already done.
  • I started FlightGear using my fork/draft. Using the mouse, LCTRL, RMB combination I navigated to the desired viewpoint (or is it point of view?).
  • F10 menu: DEBUG -> show property browser -> /sim/current-view
  • I found the view-definitions of my draft using the OS' console in the aircraft base folder:
  $ grep -winr . -e 'view n='   

note: for the DR400 the views are stored in /nasal/view.xml which is not default IMHO