First, X-Plane 10.35 beta 2 is live. If you had beta 1, X-Plane will ask to update. A few bugs that made beta 1 unmanageable are now fixed:
- No more crashes when using multiplayer.
- Joystick axis assignment UI works.
- EFIS App support is back in.
See the full release notes for more.
EFIS App networking support will remain in X-Plane for the life of v10. We thought that no one was using this option, and interestingly, none of the bug reports were from actual EFIS-App users. (If you are using EFIS app with v10, maybe drop us a line? EFIS app has been discontinued for a very long time.)
It turns out that a third party app is using EFIS App’s network output. This is sort of weird; the output is labeled for EFIS App and isn’t a published “thing. On the other hand, it’s really easy to figure out how the option works and jump on it, and that’s apparently what the developer did.* So we won’t pull it until a major version break.**
I think we’ll get a WorldEditor 1.4 public beta early next week; I’m just going through the last beta-stopping bugs now.
Linux Nerds: I need help with this bug. Basically we don’t have a way for me to compile a cross-distribution WED release on Ubuntu (Debian) without CURL going somewhat haywire.
If we don’t come up with anything better, my default action is going to be to compile on Ubuntu and if it doesn’t work on your distribution, you can rebuild from the open source. That’s not awesome, so if anyone has a better idea, I’m interested. (But: doing several builds on several VMs for several distros is not on the table. I can’t spend that kind of time on Linux build process.)
I have a build of MeshTool that can build X-Plane 10-style DSFs (with the new terrains). If you’d like to try it, please let me know.
Edit: if you want to try an early private beta of MeshTool, please email me. My goal is to have 2 or 3 users try a private build first to make sure it more or less works; then we’ll do a public beta.
* It turns out that the EFIS App output is just the regular data output on another port. More modern options like Xavion and Foreflight really have their own proprietary protocols.
It begs the question of whether we should intentionally have a ‘handshake’ with our own app to guarantee that we don’t have to do third party compatibility on what we consider our own internal interfaces.
** There’s an easy work-around for the authors if they want their product to keep working with the next major version: go back to using X-Plane’s regular UDP data output, which is actually a published thing.