richboy2307

Hi all, Apologies for the delayed response, however with KSAT we didn't have access to the source files so was difficult to implement fixes. We provided this update regarding KSAT for clafirication on discord, and will share here as well: Thanks!

Hi @Anonymous1999 How are you turning off the APU? You simply need to disable APU Bleed and then click the APU MASTER switch once for the APU to turn off. Also ensure you have your ignition switch on the pedestal returned to the center position. Thanks!

Hi @Maverick3007 It is noted, but no work on this as yet. As mentioned before, it is unlikely at the moment due to the VRAM limitations on the Xbox Console and how close we are hovering to this already. Should that situation change, we may reconsider. Thanks!

Hi @Maverick3007 Thanks both these are known issues and we'll release an update for these in the future. Thanks!

Hi @Alan Fernandes You need to ensure you have your simbrief ID (Numbers) in the EFB Options. Then it may import CLB/DES wind forecast from the OFP. However some users have reported issues with wind uplink and we're still looking into the causes for it. Thanks!

Hi @Adam Forsyth The A320neo does not come with any navdata. It is simply using the in-game navdata that is supplemented by data included in the sceneries. If you use navigraph, it uses the "scenery" method to implement its data, but the A320neo is in the end still only reading the data that is available to the sim. Can you please share a screenshot of the issue, what you're seeing on the MCDU for the approaches? Thanks!

Hi @Melow320 This is probably a result of the eye-adjustment by the sim. You can verify by putting down the shades and see if it improves. However, the shading is not severe, and intentional. Livery painters may be able to add their own custom textures, but generally no, there are no planned updated to this. Thanks!

Hi @Harp0nAv Av The A320neo v2 uses the in-game navigation data, so this can be affected by the airport sceneries you are using. If no data is being shown, its likely a fault with lack of data in the sceneries you are using. Try without those sceneries installed, and if you see data then, you need to contact the makers of those sceneries to incorporate fixes to lack of navdata. Thanks!

As mentioned by Luke, please cross check your control bindings, in particular relating to mixture/fuel controls. Also ensure you have disabled all assists from the Assistance Options (Piloting Section), especially items like "Automixture". Thanks!

Hi @Ming005150 How are you trying to operate the jetways? Also are you using GSX? PC or Xbox? Thanks!

Hi @Simon Stühlinger This is a WASM Crash, so all the systems that use WASM will stop responding as a result. To restore, you need to restart your flight. However, are you getting this crash constantly whenever you select EDDB, 25L SUKI2N SID or only happened this once? Thanks!

Not an issue on the A320neo V2. This issue is specific to the A300, due to the XML rewrite of all the switches in that plane as part of the performance optimization. For the A20N, please ensure you have configured the ACP properly: Thanks!

Hi, our EFB is capable of making calculations for up to 6,000ft Pressure Altitude as that's what normal A320Neos are capable of, and what we have data for. Anything higher would require a special high-altitude operations package from Airbus, which is not simulated in this version of the A320neo. That being said, the primary factor for things like speeds is the runway length and preference given for 2nd segment climb performance. Try to FORCE TOGA for higher altitude operations as the FLEX data may be unreliable. Thanks!

Hi @SimPilot7091 Please ensure you have calibrated your throttles from the EFB Options. Select Reverse on Axis = NO for Bravo Throttle quadrant. Also try the following: Thanks!

Thanks for the suggestion, I'll share with the team if we can make our own avatar. However if i'm not mistaken, there are some avatar available on sites like Flightsim.to Thanks!

Noted, thanks for the info! I believe this has been better implemented in our more recent smaller aircraft such as the Skyvan and the Do31, but will share with the team.

Hi @Simon Stühlinger Yes we understand the need for this feature, and plan to incorporate it into our upcoming A350 primarily. Once we've worked out a solution, we'll look into backporting it into aircraft such as A300. Thanks!

Thats probably owing to the scenery used for EIDW. If it is still using old runway designation (only 28) then thats what the sim (and thereby plane) will see. Other aircraft such as Fenix/PMDG won't be susceptible to this as they don't use the sim's navdata (default or updated via Navigraph) but instead use their own custom NavDB that doesn't look into whats actually installed in the sim. This is a sim limitation largely and best way to fix for now is to use EIDW scenery that has 28L/R in it.

Hi @Timo Dr. Roeschke Thanks for your report. We'll look into it.

Hi @jjcamb We have identified issues with VNAV when there are "MANUAL" or vector legs involved. For now if you're facing issues, we recommend to remove the discontinuits and MANUAL legs, and just be mindful of obeying them for ATC purposes. Thanks!

Hi @Harp0nAv Avwhat was your framerate at this time? The AP Logic can be affected by low framerates and lead to overcorrections as there is excessive latency in the calculations. We recommend an absolute minimum of 23FPS, below which there will likely be issues. Also ensure you have configured your aircraft properly (Flaps, Gear and appropriate speeds) prior to capture of the LOC and GS. Ensure you capture the GS from below to avoid excessive dives. Also please cross-check that you have disabled all the assists in your assistance options (Options > Assistance Options > Piloting). Thanks!

Did your autothrottle disconnect? I can assure you this is not typical behaviour and most likely a case of operator error. You'll need to provide screenshots of the situation when you notice it. Also ensure you have all assists disabled (Options > Assistance Options > Piloting) as they can cause conflicts with the AP and its logic. You can update the base sim navdata using Navigraph as well, however do note that EIDW has 2 operational runways now, namely 28L and 28R. What was previously runway 28 is now 28L. So that is why you probably could not see any associated procedures. You'll need to update your scenery if you want to use the latest AIRAC data (either default or navigraph) Thanks!

This is not a bug. Please see below: Thanks!

Hi @mjk62, I am also using the BravoTQ with this plane and do not face any unsurmountable issues in using this aircraft. We acknowledge that there could be improvements, particularly around larger or user-definable deadzones around each detent in the calibration tool which we will look to implement in a future update if possible. However as it stands, I calibrate roughly using the printed lines for guidance. I centre the base of the Throttle Lever between each marked position, and set that as the required detent position on the EFB. So for example in the shot below, I'm between the two marked lines, and have set this as CLB detent on the EFB Calibration tool when its placed here. In between the lines further ahead I would set it as FLX/MCT, and full forward as TOGA. Likewise full back as IDLE, and have set REVERSE ON AXIS = NO. This may be caused by a multitude of things. Part of which might be that you're not in the proper modes, owing to the the throttles not being moved in the proper detents. Alternatively it could be due to incomplete information on your MCDU. In order to use the managed modes, all information on the INIT A and INIT B pages must be filled correctly, as well as on the PERF page (takeoff). I can only make guesses as to whats wrong without proper screenshots/video clip of what you're noticing, however rest assured that this is not particularly an aspect of the plane that falls short and most the issues you are having can be resolved by improved proper operating techniques. It does require some patience, especially if you haven't used any Airbus aircraft before, but once you've used one, you've used them all as the philosophy and ideas remain largely the same. I will also recommend going through some tutorials on Youtube that can further detail how to operate this aircraft. Thanks!

Hi @Talha Shahzad This is an xbox limitation that will affect high quality airports such as ours. Due to the hardware limitations of Xbox, particularly Series S, it is a bit aggressive in its culling of objects in order to preserve memory. However what objects it chooses to remove is unfortunately not in our control. So its not an issue with the scenery per se. This affects not just OMAA, and if there is a fix possible on our end then we shall implement it. Thanks!