This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
pc:software:xplane11:start [2019/01/23 21:33] dwheele [Servo Demo] |
pc:software:xplane11:start [2020/12/05 18:22] (current) dwheele [Using Orbx Scenery] |
||
|---|---|---|---|
| Line 6: | Line 6: | ||
| ^Manual|https:// | ^Manual|https:// | ||
| + | ^FMS File Format|X-Plane Native FMS format\\ https:// | ||
| ^OBJ File Format|This is the format that aircraft, panels, buildings, etc., are in\\ https:// | ^OBJ File Format|This is the format that aircraft, panels, buildings, etc., are in\\ https:// | ||
| + | |||
| + | * [[.garming5: | ||
| ===== NAV DATA ===== | ===== NAV DATA ===== | ||
| Line 36: | Line 39: | ||
| Sim reported **CORRUPTED NAVDATA**. Found solution here: https:// | Sim reported **CORRUPTED NAVDATA**. Found solution here: https:// | ||
| + | |||
| + | ===== Flying J Sim 727 ===== | ||
| + | |||
| + | Purchased 727 for X-Plane 7/2020. Autopilot is unusual. Found helpful PDF: | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | {{ : | ||
| + | |||
| ===== 3D Cockpit ===== | ===== 3D Cockpit ===== | ||
| Line 70: | Line 82: | ||
| [[xplane2blender|Xplane2Blender Notes]] | [[xplane2blender|Xplane2Blender Notes]] | ||
| + | Comment that is true: | ||
| + | |||
| + | https:// | ||
| + | |||
| + | <code wrap> | ||
| + | |||
| + | I have spent some time already doing these things, just started doing it now and then, but I have some practical knowledge. | ||
| + | |||
| + | It is possible to make instruments in 3D. | ||
| + | |||
| + | For instrument objects that only have an animation(based on dataref) then they do not even have to be part of the object set as the _cockpit or _cockpit_INN. | ||
| + | |||
| + | Manipulators definitions must be in the cockpit object.(if you want it to work) | ||
| + | |||
| + | For example, an altimeter could have a 3d animated needle over a textured on numbers for hundreds. | ||
| + | |||
| + | So for objects and texturing a single x-plane object is not required for cockpit items and there are ways to get around manipulators like click/ | ||
| + | |||
| + | But with 4096x4096 textures, more gray could be squeezed in the texture uv space :P. for a single cockpit object. | ||
| + | |||
| + | </ | ||
| ==== Servo Demo ==== | ==== Servo Demo ==== | ||
| Line 185: | Line 218: | ||
| if __name__ == ' | if __name__ == ' | ||
| main() | main() | ||
| + | </ | ||
| + | |||
| + | **Troubleshooting** | ||
| + | |||
| + | Had some problems because the VVI came on index [2], not [1]. I kept seeing -999 show up. Was able to see the situation by using the code up above without responding to type=4, and it dumps all of the values out, and I saw where the VVI value was located. | ||
| + | |||
| + | Still not knowing the relationships between the type numbers and the DataRef numbers within Xplane 11. | ||
| + | |||
| + | 1/23/2019 | ||
| - | </ | ||
| ===== Changing Scenery ===== | ===== Changing Scenery ===== | ||
| Line 194: | Line 235: | ||
| 1/21/2019 | 1/21/2019 | ||
| + | |||
| + | ===== Using Orbx Scenery ===== | ||
| + | |||
| + | http:// | ||
| + | |||
| + | Orbx uses a "Orbx Central" | ||
| + | |||
| + | As of this writing, Orbx doesn' | ||
| + | |||
| + | 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, | ||
| + | <code text> | ||
| + | 2 33.813 | ||
| + | </ | ||
| + | |||
| + | The K1 makes it think it is located in the Northwest, but this could be fixed. | ||
| + | |||
| + | This marks Disneyland. Directions: https:// | ||
| + | |||
| + | ===== Adding Garmin 430/530 to Custom Panel ===== | ||
| + | |||
| + | Found out about how to add Garmin to custom panel from this: | ||
| + | |||
| + | https:// | ||
| + | |||
| + | Looks like I'll need to add a custom property from within Blender to turn on the Garmin. | ||
| + | |||
| + | '' | ||
| + | |||
| + | <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. | ||
| + | |||
| + | 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. | ||
| + | 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. | ||
| + | </ | ||
| + | |||
| + | This goes inside of an OBJ file. | ||
| + | |||
| + | 2/12/2019 | ||