richboy2307

Hi @Skycowboy You could reach out to support (or reply to the email) with other means of proving proof of purchase/identity. As for making changes manually, I'm not sure if the marketplace version will encrypt these files (usually not), but you could manually disable the statics .bgl file. You will find it in the 'Official' packages folder under ``inibuilds-airport-omdb-dubai`` folder. Rename the ``omdb-scene-statics.bgl`` to something like ``omdb-scene-statics.disabled``, then update your layout.json file (please keep a backup of the original before making changes). Thanks!

Hi @mido2040 The team is already aware of the reports of performance issues by some users and looking into it. Thanks!

Hi @Timm Turner The flightplan you set/import in the World Map will not be loaded automatically into the plane. You need to either: Enter it manually in the MCDU, OR Import your Simbrief flightplan into the EFB (Dashboard Page > Simbrief Icon) and MCDU (INIT Page > select INIT Request) To import from Simbrief, you need to set your Simbrief ID on the EFB & MCDU first as follows: EFB - Go to Options page > enter Simbrief Pilot ID (Numbers Only). You can enable the ON SCREEN KEYBOARD option too from below to help you fill it in. MCDU - Press the MCDU Menu button > select ATSU > Enter your Simbrief Pilot ID (Numbers Only) Thanks!

Thanks for sharing @skydiver6547 Ok I found the issue. If you're using a single `Throttle Axis``,, then the issue you described occurs. However if you are using ``Throttle 1 Axis`` and ``Throttle 2 Axis`` (which is what I was doing as I have 2 separate levers on the BravoTQ, one for each engine), then it is working properly. The bug is logged and we'll look into it. But in the meanwhile, you can get around this by assigning the same axis (Joystick L-Axis Z as you mentioned above) to both ``Throttle 1 Axis`` and ``Throttle 2 Axis``. Do not use `Throttle Axis`. As below: Thanks!

Thanks for your detailed report. Has been logged for further testing. Yes the result sounds like a WASM crash, hence why certain systems are now INOP/unresponsive. Unfortunately though we haven't been able to reach the same result internally yet, having tried multiple times, across variants (PW F/PAX, GE F/PAX). Here's a video of one such attempt in N744FD (Fedex PW F) at EDDM: 2024-06-07 02-07-01(1).mp4 If there were any WASM crashes, it would have showed up in the Dev Mode Console Window on top left immediately with a warning in red. However as you can see after doing this process, none happened and all systems can be interacted with without issues. Do let me know if something was missed in this process however. Thanks!

Your suggestion is noted, thanks!

Hi @Bazz So it shouldn't ignore your constraints in a managed descent (DES). It would however ignore them in an Open Descent (OP DES). Normally you would see on the bottom right of your PFD, the target ALT, same as set on your FCU in blue colour. If it is limited by any constraint, it would show up in Purple with the ALT of that constraint. So when you are noticing this issue, could you please provide a screenshot of your PFD,ND, FCU and also the MCDU (FPLN Page)? Could you share the full route that you tried? Also a screenshot of your INIT A/B pages or list the values used. I have just tried with a couple of randomly generated dispatches via simbrief and not exactly seeing your calcs. Here's an example: From this, I can see for YBCG RNAV-W RWY 14, the following computed path: Do note that VAPMU is programmed in this procedure as 2500ft or above alt constraint by the navdatabase itself, and we cannot control that. So given this restriction, it has computed the path (within margin of error) whilst still abiding by the constraints. I am not able to reproduce the erroneous path currently, but would love to try with the data you are using to see if we can reproduce the problem, and thereby improve on it. Thanks!

For our aircraft (e.g. A300/A350) we probably could theoretically, but obviously no for Microsoft products like the A310/320neo. Thanks!

Hi @Kevin B There is an update currently under testing that includes performance and stability fixes. Please try with that once available and let us know about your performance then. Thanks!

Hi @DanDan87 / @Airbuskid87 Can you check if you have Aircraft Light assists set to OFF? (Options > Assistance Options > Aircraft Systems) Do note, after setting it to OFF, you will need to restart the flight for changes to take effect.

Hi @Shanks16 Thanks for the data. We do have performance metrics internally as well, which we gather from tests across different tiers of systems as part of the optimization process but never hurts to have have more data for analysis. Shared with the team. Also would appreciate if you could run the same test on the upcoming A300 update once it is available. There are some performance and stability improvements coming in that, so would be curious to see the difference on your system compared to the current data. Thanks!

What axis have you mapped your throttles to? Can you please share a screenshot of your EFB Throttle calibration page, alsoyour ThrottleData.ini file? Thanks!

Hi @LeeH No, we do not have any more liveries planned for the moment. Thanks!

Hi @Thompson Thanks for the suggestions. 1) Navigraph Charts - As this is a Microsoft Product, that decision ultimately rests with them. As much as you or we would love to, in the end such integrations with 3rd-party, non-default services have to be wanted and approved by them in their product. 2) In-Game ATC integration - your suggestion is noted and shared with the team. Thanks!

Hi @Bazz The red disconnect pb on the sidestick is mapped to 'AUTOPILOT OFF' command only, so you need to assign it to that instead. This is because IRL that button can only be used to disengage, and not engage the AP. If you disconnect the AP using this button, the alarm should only sound once and silence itself. If not, press that red button again to silence it for good. Thanks!

Hi @radbird Are you on Xbox or PC? This sounds like some kind of add-on conflict of some sorts. If you're on pc, try to run the SkyVan with an empty community folder. To do so without having to reinstall any addons, simply rename your existing Community folder (e.g. rename it '_Community'). Launch the sim, load into the SkyVan and see if you are still noticing such issues. If yes, that means you have something in your community folder that is causing a conflict. If you're using an addon like Horizon Simulations 787, please make sure it is updated to the latest version. If no, please report back. To restore your community folder, simply delete the new empty 'Community' folder, and rename your old one from '_Community' back to 'Community'. Thanks!

Hi @MitchellAA300 We just checked on our end and are not able to reproduce such issues with lighting. The lights will generally disappear at certain zoom levels (as this is part of LOD optimization for performance reasons), but they remain on in external views at the right zoom level. Also stairs are only available on cargo variants. Are you not able to see them via the EFB on the cargo aircraft?

I'm afraid you're on your own with that as that is copyrighted and protected material that we cannot share whole. However, google is your friend 😉

Thanks, reported.

Hi @kekki Please English only on these forums. And no you shouldn't need to restart the plane after every flight. What is the issue you are facing?

Hi @BrownCow069, Good catch. The 'Actual N1%' needle (green arrow) is correct, and at max reverse ~45% N1 is expected. However what appears to be wrong here is the 'Thrust Lever Angle (TLA) Position / N1% Command' needle (red arrow), so will log that as a bug. Thanks!

Thanks for confirming my statement. It "updates" with some "ILS data" every time you select a procedure. The 'phase of flight' determines whether that "ILS data" should be read from Departure Airport or Arrival Airport files. But if you continue further to read the third paragraph, you'd notice: In other words, when you select a procedure, the MCDU is calling on a default MSFS function that pulls the "ILS data" from an airport. The "ILS data" it pulls, is as defined by: the scenery itself (default or add-on) OR some other scenery files (as added by Navigraph or other navdata addons).* *The priority of the load order between both of the above is also not something the a320neo can control. There is no independent nav-database that the airplane is calling upon (e.g. in addons such as Fenix or PMDG which you can update via Navigraph Hub). So the "fix" to this issue is to ensure the scenery data and additional navdata is not in conflict, and appropriately taking precedence. Hope that helps you to better understand the issue. Thanks!

Ah, sorry I misunderstood your request. But that should be an easy fix. Bug logged, thanks!

Hi @Hungrypilot We currently have it tuned per IRL data for the A306. The BRAKE FANs exist for this reason, and are important equipment on this plane (unless you got time to wait for your brakes to cool). Generally, the slower you are, the less energy there is to lose using brakes, and the less heat will be generated as a result. In short, more flap, more reverser, less brake. Turn on brake fans as soon as you vacate. Do note that even with them ON, the brakes will continue to heat up as they try to dissipate the energy stored in them, and eventually they will reach equilibrium and the fans will start taking effect. Thanks!

Hi @Luciano Firstly, please ensure you have calibrated your throttles from the EFB Options. The function of the A/THR in A320neo is linked to your throttle levers being in the CLB, FLX MCT or TOGA detents. If your throttle is outside those detends, on your PFD the FMA will show MAN THR and you may not be able to engage A/THR. In general, I recommend you checkout some tutorial videos on youtube on how to fly airbus aircraft. There are many great options on youtube, but you could start here about Autothrust: