richboy2307

Thanks I have shared this thread with the team already as of 31/7 and they are aware. If there is anything to be incorporated/improved upon, it will be done as everything seen in all previews till date is all still a WIP. Beyond that I wouldn't expect any reply from team members specifically on each issue. 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!

@D-RustonThanks for sharing. I'll forward to the team. I've also merged all the posts into one. Going forward if you have information to share, you can just add them all within the same post as replies. Thanks!

Hi @Maviatious Interesting. Glad its solved though. 🙂

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.

Its possible, but the installer is just an .exe file that you run and it installs. It shouldn't need any extracting. I have just tried with the latest version downloaded online and am not facing any such installation issues. But the fact its failing seems to indicate some kind of permissions issue. Either blocked by anti-virus, or your user account not having the appropriate access. I know you tried running as admin already, but those are the usual causes. If you have another drive, perhaps try it on that instead? You could also try to delete the iniManager folder at this location. Windows+R key to open run, and then paste the following path: Normally this is where the installer extracts to. Thanks!

Hi @Scotty Temporary server hiccup. Should be working now. Apologies for any inconvenience caused!

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!

Thanks for your suggestion. I'll share with the team.

Thanks I see the oscillations. What was your FPS at the time? Low FPS can mess with the autopilot functions. I believe a minimum of 23 is required, below which there can be latency in calculation that leads to excessive inputs/overcorrection. Also can you ensure you have all the assists disabled (Options > Assistance Options > Piloting)? These can cause issues with AP inputs. Also recommend a turbulence setting of MEDIUM or LOW, especially in mountainous areas such as where you're flying as the mechanical turbulence effect on large aircraft is unfortunately bit too exaggerated in the sim at REALSTIC setting. Owing to probably one of the above reasons, your yoke input appears far more excessive than experience by me personally in testing and flying this aircraft. The yoke blocking the instruments however, is an issue even in the real aircraft so you can either adjust your view point, or simply hide the yoke as recommended above if it is an issue, With regards to the AutoPilot, you can bind a key command to your keyboard, mouse or controllers to commands such as TOGGLE DISENGAGE AUTOPILOT or AUTOPILOT OFF such that you won't have to bring up the yoke again. Click the command twice to silence the AP Disconnect wailer. Thanks!

Hi @Maviatious Please do not extract the files manually. I would suggest checking Windows Defender or any antivirus programs to see if they're blocking it. Also try to rename the installer to "iniManager-2.3.8_Setup.exe" (without +) to see if that helps. Thanks!

Its telling you to capture the LOC early, before you capture the Glideslope. So select LOC on the FCU, and once established on the LOC, then arm APPR to intercept the glideslope. JayDee's guide you have linked is already pretty concise in my opinion. However if you want to see it done, just take any video from this query, as the process is the same in all A320s (NEO or CEO) for flying an ILS. https://www.youtube.com/results?search_query=a320neo+landing+tutorial Thanks!