Rodeo

I can't help but feel disappointed that there's no gateway airport for LHSM; I expected to find one, and made by Litjan of course!

Quite intriguing (sorry, I have no idea what's causing the behavior, I just saw there was a video and tought "oh, shiny!")

I would definitely update everything right away, since that will also update X-Plane's navaids. If you don't update the X-Plane native data (earth_*.dat), then all radio beacons (VOR, NDB, ILS etc.) will be slightly outdated, and this affects the IXEG 737-300, too

DataRef Editor automatically sees all datarefs… when running it under Mac OS X. Otherwise you have to manually provide it with a list of DataRefs. DataRef Tool will specifically scan plugins and planes for datarefs, but it works a bit differently to DataRef Editor and sometimes causes the IXEG 737 to crash.

Thanks! I think I have the information I need.

I mean things like uploading to X-Plane wouldn't work, obviously, but I'm mostly interested in the calculations, like N passengers in different cabins gives us a plausible GW and CoG that I can use in IXEG's fuel & load panel

Question before I pull the trigger: does the fuel & balance manager work even without the app being connected to the plane via a plugin?

Remove the AirTrack (HSAIR-Win64.xpl) plugin from the plugins folder.

Thanks

Any news on a standalone or iPhone application?

Do you mean MCP buttons? ixeg/733/MCP/*_ann Regarding N1, do you mean the two "pull to set N1" actuators? ixeg/733/ecam/eng1_limit_act ixeg/733/ecam/eng2_limit_act

My guess is you must have updated to macOS Sierra or a newer Beta of it.

Oh well…

For some reason, I was under the impression that some of the IXEG's core components were actually found in Resources/plugins/Gizmo64.plugin But after a quick check today, it seems like I was incorrect and that all logic files are contained in the aircraft's folder instead. So, as long as they're both in Aircraft/X-Aviation/, it would be possible to have two versions installed concurrently, so I can switch between them (e.g. keeping an older version around in case I encounter a regression)? X-Plane 10/Aircraft/X-Aviation/IXEG 737 Classic 1.0.5/ X-Plane 10/Aircraft/X-Aviation/IXEG 737 Classic 1.0.7/ …should I expect any issues in doing so? I've been sticking with version 1.0.5 because 1.0.7 seemingly has several new soft crashes related to the FMS reset introduced in that version, but if I can keep both versions around I'll upgrade and only fall back to version 1.0.5 for actual regressions, if any (as opposed to potential ones)

+1

Check the version in-sim using the IXEG menu - the installer version is not related to the aircraft version.

No, the text hasn't changed since I last read it. I'm afraid that's pretty clear. Still, I think (hope?) this should be easy to implement as long as they use default X-Plane manipulators.

Thanks for the heads-up!

As for a user-to-user suggestion, are you sure it's a good idea to use the NVIDIA Web Driver with an unreleased OS version? Personally if I were Beta-testing video games simulators under Sierra, I'd stick with the built-in graphics driver ;)

I was thinking of Apple's built-in Simulator for Xcode. Though I didn't check whether you can install App Store apps on it, I suspect not but I guess it's worth a try.

Any chance this can be used in the iOS Simulator?

I have a vague suspicion that the micro-stutters (which is a separate issue from this one) and this may be caused by the plugin writing some temporary/non-persistent information to disk when it should ideally just be kept in RAM.

Nope, after (see Tom's video above).

The installer always grabs the latest version of the plane from the X-Aviation servers.