Leaderboard

Have you updated airhauler Air Hauler 2 (XP11) Changelog Latest Update: 2023/08/01 The below log shows all updates for this product since release: v3.0.1.0 - Fixed issue with UTC time conversion when pushing job to VA - Added Pilot & NPC character portraits - Added NPC reputation to available mission description - Supply missions - removed the From ICAO as it was confusing people, it is now left blank - When asked to clear the Pilot log, answering No will now leave it as is - Pax config aircraft have a reduction of 30% cargo capacity (to reflect seats etc) - Resolved issue which would result in all commodity markets closure if airport missing - XP - the AH2 XP11 plugin now supports XP12 (minimum version 11.50+) - Export button added to AI Pilot flight log toolbar - Fixed issue preventing mission generation - Prevented AH2 updating the Aircraft import list after importing an aircraft before closing the window - Added pilot/fleet map filter options in Accepted Missions window You can also get rid of Skunkcraft updater as they now have a standalone version that is not a plugin, which helps with start up times and update delays. XPUIPC is still waiting a promised update, maybe in 100 years. And as mentioned above Sam is notorious for causing issues plenty of posts on that one.

The oscillation is being caused by a positive feedback with the ground spoilers deploying whenever the ATS commands idle thrust and pulls the thrust levers back to the idle stop. This causes the nose to either drop or rise, which then feeds back into the speed excursion, the ATS changes power settings again, the vertical guidance starts hunting for the VPATH and the whole cycle repeats. Ground spoiler deployment can only happen if: Ground spoiler arming switch is either in AUTO or ARM, and Thrust levers are idle, and Either weight-on-wheels is detected, or wheel spin-up is detected Neither of 3 should theoretically be possible, but seeing a recording of the aircraft from the outside to see if the wheels are spinning in the wheel bins would be helpful. We do tell X-Plane to STOP the wheels from spinning when retracted, but if there's some sort of physics bugs going on inside of X-Plane's wheel logic, then it might be spinning the wheels anyway. This would trigger the PSEU wheel spin-up signal and that might be causing the ground spoiler deployment in flight. I can tell you that for sure we set both the l_brake_add and r_brake_add datarefs to non-zero values to tell X-Plane to NOT DO THAT, but if it is ignoring our input, then it's out of our hands.

Vulkan device loss is always a sim-generated render pipeline error, and nothing an add-on does should be able to cause it if the sim is working as designed. I've found it can also be triggered by using graphics settings that are too high for the hardware. I definitely suggest following Litjan's advice, but also reporting the crash to Laminar Research.

I have now completed a few dozen flights with the Challenger. I notice that during descent, the ATS speed control is quite erratic in maintaining the FCP selected speed. For example, speed set to 240 under FL100, from current speed of 290: upon reaching 240 after the deceleration, the throttles get increased a few knots before reaching 240 and push the aircraft to ~248, then throttles get reduced by the ATS. Again, upon reaching between 243 and 240, the throttles engage again, pushing the aircraft to ~248, and back down again. I believe the ATS needs some fine tuning, as it is currently too aggressive, pushing the nose up and down, into a clear oscillation pattern. This is happening no matter what the weather is, and annoys me to a point where I often take manual control of the throttles. One thing I also notice, relating to all this, is the amber GND Spoilers alert on the MFD, as soon as you overspeed by as little as 3 or 4 knots; is this also happening in the real thing? I reckon there might be some settings related to those sensitivities somewhere in the settings, of which I am not aware; so I will be happy if someone can point me in the right direction. Thanks in advance for any help in resolving this.

Congrats on all the things! Welcome back. Buy the Challenger 650. ;-)

Yes, I just reviewed the checklist, and you are right indeed. Will test with the switch set at AUTO, and as I said, will also check the wheel spinning too. I will also make sure I press the brake pedals after gear retraction, in case.

Thanks everyone! Followed the advice and think I found the culprit - Honeycomb Configurator. I'll keep my plugin folder trimmed down from now on anyway. A lot of nonsense in there.

You have many plugins, some of them notoriously prone to cause problems. (Like SAM, for example). You need to remove (not only disable) all plugins except for Gizmo and the default X-Plane plugins, then try again. If that works, start adding your other plugins until you find the one that is causing the crash. Cheers, Jan

Ah... haven't being enabled yet in the code. Working on this right now. Stopped in the middle of this testing Austin's builds. Should be ready for this release, probably around the end of the week.

Here's a video of it. Note that the behaviour starts happening when getting close to the 240 knots /10,000' restriction. Sorry it is only 1 minute, but I just downloaded this screen recorder, and it is limited to 1 minute videos in it's free version; but the behavior will continue all the way down to landing. Thanks for looking into it, as I really find it annoying. I usually disconnect AT and try to control my speeds/spoilers manually, which takes a lot of concentration off the route and approach.

The "cabin ready" is something that the flight-attendants notify you verbally about. We have decided to NOT add any of the automatic callouts that co-pilots or flight-attendants do, as opposed to other dev teams, because the procedures and wordings vary too wildly and instead of people being happy, it would trigger an avalanche of people requesting to do it this way or that way, because when they flew as kids in the 60´s they alwas used to hear "fasten your harness", but now they say "seatbelts" and how on earth can they expected to enjoy the 737 with such a glaring discrepancy...

Hello All, This will serve as an official announcement that we have released the version 2.0.2 update for the LES Douglas DC-3 v2. All customers who have purchased the LES Douglas DC-3 v2 up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the LES Douglas DC-3 v2 from today forward, your purchased download will already be updated to version 2.0.2 for you. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php 2. Find your original LES Douglas DC-3 v2 download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: What's New / Changed: Both Variants: Fixed freezing, when DC-3 is loaded as the first aircraft. Fixed opening the windows and no sound change is audible. Fixed version number shown in X-Plane. Now is 2.0.2. Master Radio switch now controls avionics bus as well. Logging: Removed some unnecessary logging, and fixed typos. Classic Variant: Fixed some cases no autopilot is selected by default. Now simplified is preselected. Copilot's DME1 light is visible when GPSs are shown. Modern Variant: Adjusted inside sound space. Fixed rain on windows not visible from inside. Fixed COM2 radio volume knob not changing the volume. Fixed dark background in copilot's attitude indicator. Fixed copilot's attitude indicator and trim ball not animating when GTN650 is selected. Fixed FMOD logging error. Removed transponder light from ceiling radio stack. As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support!

We're thinking "time is money". My mortgage payments runs on a timeframe...my internet fees...my software subscriptions, my commissions.....special offers in the mail......all time frame limited to encourage folks to act to keep the economic cycle moving. Time and money is inextricably linked. Without this principle, no business would survive and we've have no products...no add-ons, no x-plane, etc. Who is John Galt anyhow. TK

Tom explained it in the recent video he did with Q8pilot - he had to make a decision whether to continue developing the 737 or going down another road in his life to make money. And he needs to eat now, he can´t go hungry for a few months with people on the fence waiting if they want to maybe update or not ("I want to wait until they put in the holds..."). That is why we nudge people to pay the money now.