User Tools

Site Tools


pc:software:xplane11:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
pc:software:xplane11:start [2019/01/25 20:45]
dwheele [Making custom gauges]
pc:software:xplane11:start [2020/12/05 18:22] (current)
dwheele [Using Orbx Scenery]
Line 6: Line 6:
  
 ^Manual|https://www.x-plane.com/manuals/desktop/#advancedsimulationinx-plane| ^Manual|https://www.x-plane.com/manuals/desktop/#advancedsimulationinx-plane|
 +^FMS File Format|X-Plane Native FMS format\\ https://developer.x-plane.com/?article=flightplan-files-v11-fms-file-format|
 ^OBJ File Format|This is the format that aircraft, panels, buildings, etc., are in\\ https://developer.x-plane.com/article/obj8-file-format-specification/| ^OBJ File Format|This is the format that aircraft, panels, buildings, etc., are in\\ https://developer.x-plane.com/article/obj8-file-format-specification/|
 +
 +  * [[.garming5:|Garmin G5 Emulation]]
  
 ===== NAV DATA ===== ===== NAV DATA =====
Line 36: Line 39:
  
 Sim reported **CORRUPTED NAVDATA**. Found solution here: https://forums.x-plane.org/index.php?/forums/topic/167034-latest-navigraph-airac-causes-error-in-zibo-mod/  (modified file at ''X-Plane 11/Aircraft/Extra Aircraft/B737-800X/plugins/xlua/scripts/B738.fms/B738.fms.lua'', adding additional rows to the NavData date ranges, and changing to ''cycle_n = 31'' Sim reported **CORRUPTED NAVDATA**. Found solution here: https://forums.x-plane.org/index.php?/forums/topic/167034-latest-navigraph-airac-causes-error-in-zibo-mod/  (modified file at ''X-Plane 11/Aircraft/Extra Aircraft/B737-800X/plugins/xlua/scripts/B738.fms/B738.fms.lua'', adding additional rows to the NavData date ranges, and changing to ''cycle_n = 31''
 +
 +===== Flying J Sim 727 =====
 +
 +Purchased 727 for X-Plane 7/2020. Autopilot is unusual. Found helpful PDF:
 +
 +{{ :pc:software:xplane11:727autopilotcontrolsmore.png |}}
 +
 +{{ :pc:software:xplane11:xp11_flyjsim_727-100_guide.pdf |}}
 +
  
 ===== 3D Cockpit ===== ===== 3D Cockpit =====
Line 71: Line 83:
  
 Comment that is true: Comment that is true:
 +
 +https://forums.x-plane.org/index.php?/forums/topic/114562-3d-cockpit-question-separate-instrument-objects/
  
 <code wrap> <code wrap>
Line 221: Line 235:
  
 1/21/2019 1/21/2019
 +
 +===== Using Orbx Scenery =====
 +
 +http://www.orbxdirect.com
 +
 +Orbx uses a "Orbx Central" app to download scenery and place it where it thinks it should be. Since I want to have one copy of the scenery, but use from multiple X-Plane instances, need to implement "Libraries." But this is just a directory where the scenery is installed, and a Shortcut is placed in the X-Plane Custom Scenery directory to point at it. Note that the Library folder directory structure is a little different than X-Plane's, so point to the right places.
 +
 +As of this writing, Orbx doesn't support very well the notion of changing where Orbx thinks the X-Plane directory is located. Helpful link: https://orbxsystems.com/forum/topic/177698-multiple-x-plane-installations/
 +
 +Using Orbx with xOrganizer: xOrganizer controls which scenery is loaded by manipulating the ini file. Since the Orbx scenery looks like all of the rest (if installed directly here, or via symbolic link (shortcut), this works.
 +
 +
 +===== Added NDB =====
 +
 +Added this to the end of user_nav.dat, located at ''X-Plane/Custom Data/user_nav.dat''
 +<code text>
 +2  33.813       -117.9              100      589    50      0.0  KDIS ENRT K1 KDIS NDB
 +</code>
 +
 +The K1 makes it think it is located in the Northwest, but this could be fixed.
 +
 +This marks Disneyland. Directions: https://forums.x-plane.org/index.php?/forums/topic/143561-add-custom-ndb/
 +
 +===== Adding Garmin 430/530 to Custom Panel =====
 +
 +Found out about how to add Garmin to custom panel from this:
 +
 +https://developer.x-plane.com/article/obj8-file-format-specification/#ATTR_cockpit
 +
 +Looks like I'll need to add a custom property from within Blender to turn on the Garmin.
 +
 +''ATTR_cockpit_device <name> <bus> <lighting channel> <auto_adjust>''
 +
 +<code text>
 +[New in 1100:] The ATTR_cockpit_device command changes the lit texture of the object to the screen of a given GPS device for an aircraft; it is legal only in aircraft-attached objects.  Use ATTR_no_cockpit when done.  Parameters:
 +
 +    Name is the device name, one of GNS430_1, GNS430_2, GNS530_1, GNS530_2, CDU739_1, CDU739_2, G1000_PFD1, G1000_MFD, G1000_PFD2.
 +    The bus is a bitfield, indicating all the electrical system bus indices (zero-based) that this device gets power from.
 +    The lighting channel is the zero-based index for the instrument lighting rheostats that control the screen’s brightness.  (Cockpit device lighting is not subject to ATTR_lit_level.)
 +    Auto-adjust is 1 if the screen brightness increases to be readable during the day, and 0 if screen brightness is “washed out” by the sun.
 +
 +The rest of the state commands affect the above published state.
 +</code>
 +
 +This goes inside of an OBJ file.
 +
 +2/12/2019
  
  
  
pc/software/xplane11/start.1548449123.txt.gz · Last modified: 2019/01/25 20:45 by dwheele