Bjoern

Heh. As we say in German: "Dogs who get hit start barking". Consistent indeed, because that's the same verdict I've been reading about them since, uh, FS2002 (or was that FS9)? At least Thranda made something usable out of their (admittedly still very easy to look at) 3D and textures, so let's be glad that, at least for some time, at least the XP10/11 crowd got their money's worth.

Sigh. You're neither entitled to "good" add-ons nor to continuous development of add-ons (features, bug fixes) nor to infinite compatibility with future sims. Developers control the pricing and product development route and if you don't agree with that, simply leave your credit card in the wallet and buy something else. Keeping the price non-discounted is actually a good move, as it keeps as many customers, who'd buy it exclusively for use in an unsupported sim, away as possible. Also, most aircraft from Carenado's collection have more modern equivalents from other developers anyway.

Well, Carenado's aircraft were made for X-Plane 11, so if you just run them in that version, they're guaranteed to work*. And I think they still offer support via e-mail, so all the boxes that warrant the price are technically still ticked. *Some inherent, unfixed bugs aside, but the wary customer of course does his/her research before clicking "Buy". :-)

Part responsibility for the huge delay is allegedly that Dassault was very insistent that this one is very close to the manuals.

Mind that the low price of the E-Jets comes with a very simple autopilot.

No, it's a combination of add-on scenery, plugins that read lots of data, SSD speed and Windows.

Default AI traffic should not ignore your presence. Then it's a bug in those plugins.

According to Skymatix, he's too busy in real life to care for XP. But he allegedly wants to get back in this autumn. Make of that what you will.

Or maybe the devs simply have something better to do than developing XP models, especially if it's just a pastime kind of affair.

The decision to focus on an app based updating procedure is because Zibomod out of the box exhibits some annoying, inherent bugs (VNAV descent tables, weight & balance) when used with the LevelUp 737NGs. For a multitude of reasons like license agreements with Zibo, Zibo's absence, and generally no real line of communication between LU and Zibo (not for lack of trying, mind you), this requires compatibillity patches for LevelUp's Zibomod installation. Since manually patching Lua files or executing Python scripts to do the patching is too tedious in the long run, the 737NG Maintenance Toolkit (MTK) was developed by a LU team member as a more easy to use app (which can also install fresh copies of both the LevelUp and Zibo 737). Since V2.S1.51 is essentially the first public outing of the MTK, some bugs and quirks may still be present. Theoretically, one could still download the latest base pack and manually update with the latest update archive (if one finds the Github repository...), but this will not install the latest patches. The only configuration supported by LevelUp is the latest release including the latest compatibility patches. Any support request for configurations deviating from this standard will be rejected by LevelUp. Therefore, it's best to get used to the app as quickly as possible, as it is completely uncertain if any of the patches will ever make it natively into Zibomod. Source: I'm on the team. And before anybody gets ideas from that: Official support for the aircraft and the Maintenance Toolkit happens on Discord (see the readme for the link), so do not expect me to work miracles with any issues here (especially with the Maintenance Toolkit). Private messages with support requests will be rejected. If some issue occurs on both LevelUp's and Zibo's 737, it must be reported to Zibo as it can not be fixed by LevelUp. P.S: Check the patch selection on the MTK's "Advanced" page. Especially the optional performance calculator patch is helpful for those not using SimBrief.

Since I could reproduce this, i've asked Laminar on Discord and they say that it's a rendering engine limitation. Something to do with the switch from 2D trees to 3D tree model and a subsequent alteration of ambient occlusion. So it's something that can not be readily changed or improved. You won't see that effect when you disable 3D vegetation.

I do not understand the problem, but if you think you found a bug, you need to file a report. X-PlaneX-Plane Bug ReporterReport bugs and technical issues directly to the X-Plane development team. Use the official X-Plane Bug Report Form to help improve the flight simulator with your feedback and error reports.

You can set datarefs all day, but without some cloud layers to block out the sun, fog from an inversion layer is all you will get. Do it the proper way and simply set the weather instead because it's a much more organic, flexible and non-hacky solution.

🤷

I doubt you'll find many, if any, Pimax users here, especially with X-Plane 11. Your best shot at support might be the #xplane-vr channel on the official X-Plane Discord server: https://discord.com/invite/x-plane-official-1072974189906108509 Or the XP11 VR forums at: https://forums.x-plane.org/forums/forum/380-vr-in-x-plane-11/ Note that X-Plane 11 is end of life, so any bugs with newer hardware are there to stay.