richboy2307

Please note you make any such changes at your own risk. In our testing we found that changing contact points had unintentional side-effects - i.e. excessive "bouncing" on braking at certain braking strengths. Sorting that through modelling changes would, in fact, be a "complex fix" and as a result it was decided against making any changes in this regard to contact points. Thanks!

Yeah unfortunately it got coupled with the new LNAV update in the end, so was missed as being mentioned separately. But yes, it covers all instances of LNAV, including DME ARC procedures. Thanks!

Yes as mentioned. This is intentional. Only valid ILS freqs are those between 108.00 and 111.95 MHz that have a odd digit after the decimal point (i.e. .10, .15, .30, .35, .50, .55, .70, .75, .90, .95) Thanks!

For everyone on this thread. After updating, we highly recommend you clear all the contents of the folder listed below. All files will be re-generated next time you launch the A300 (compiles separately for each variant). This is to ensure that all files used are generated/compiled under the new WASM of v1.1.2 only. Steam Version: MS Store Version: Thanks!

Hi @berkkp Team is aware and looking into this. Making any amendments to an ALTN airport will cause a WASM crash in the current build. It was working fine during the beta tests, but somehow seems to be causing issues in the Public build currently. We'll push an update for this once sorted. Apologies for any inconvenience.

Thanks for your suggestion. Will share with the team.

Hi @Embalmz Thanks for your suggestion. I'll share with the team. Meanwhile if you could provide additional reference for this, from multiple angles and/or in better detail it would help.

Hi, we're aware of the changes and the suggestion is noted. Thanks!

It shouldn't be too long we hope. We have already submitted to MS/Asobo, however we have no control over their processes so can't provide any ETA. Thanks!

Yes this is a known issue, already fixed for whenever next update is available. Thanks!

Hi @xEspada I've been using the a320neo full screen, alt-tabbing multiple times without any issues. Is it possible that you are accidentally clicking some data-entry field in the EFB whilst you are alt-tabbed? As that causes the sim to be locked to in order to only take keyboard input for filling in the info into EFB. When this happens, try to use the Camera menu from the toolbar on top to navigate to the efb instrument view. You'll note the red bar on the EFB if you're in data-input mode. Thanks!

Yes this is a known issue, already fixed for whenever next update is available. Thanks!

You still need to calibrate initially. There is no default calibration. On the EFB, select REVERSE ON AXIS to YES, then NO. That will force-reset the calibration. After that re-calibrate again. Keep REVERSE ON AXIS as NO if you are using a controller. Thanks!

Please try to clear the contents of this work folder, to ensure there were no issues of older files not getting replaced fully. It will regenerate all these files next time you launch the A300. Steam: MS Store: Thanks!

Hi @selkin Please try to clear the contents of this folder, to ensure there were no issues of older files not getting replaced fully. It will regenerate all these files next time you launch the A300. Steam: MS Store: Thanks!

The team is aware of this issue, primarily in legacy interaction mode. It's an issue with Asobo's switch template that we're using for optimized performance. It affects most 3-way switches. We're looking into it. Thanks!

Hey thanks for the feedback.We'll look into this.

Hi @ApolloBlackCat Not as yet, it is on the list for next update. For now to restore NoolVDGS please do the following: Find your Community folder and inside look for iniBuilds-airport-egll-heathrow folder. Here you'll see things like the layout.json file that you need to edit. In it go to SimObjects > Landmarks and there you'll see the noolaero-vdgs-egll Rename noolaero-vdgs-egll to noolaero VDGS EGLL Then go back to iniBuilds-airport-egll-heathrow and update the layout.json (either manually in notepad or by dragging the .json file on top of MSFS Layout Generator.exe tool) Finally, run the Noolaero app to Rescan devices. This time you will see EGLL populate in the list. Thanks!

Please Calibrate your throttles in the EFB using the guide below:

Hi @Scott Wongsanguan Thanks for sharing the video! Hmm, we're not able to reproduce this issue on our end. Please try to clear the contents of the folder below, it will re-compile these files next time you launch the A320Neo v2. Also ensure you do not have any AI Assists enabled (Options > Assistance Options > Piloting) that may cause conflicts. Steam Edition: MS Store Version: Thanks!

Hi @Scott Wongsanguan I have tried your steps multiple times and unable to reproduce the issue on our end. Attached below the recording of one of the attempts: Please ensure there is no conflict with other addons. If you are on PC you can do this by closing the sim, and renaming your Community folder to "_Community" temporarily. Launch the sim, test and see if the chocks are working properly. After you are done testing, close the sim and delete the newly created empty Community folder, and rename the "_Community" folder back to Community. This will restore all your installed addons without having to reinstall them. If they chocks are working fine with an empty Community folder, then there is likely a conflict. To avoid this update your installed addons and do some further testing to find out which one may be causing an issue for you. Thanks! 2024-07-19 04-58-04(1).mp4

Hi @Bald kelp Sorry, there are no known bugs/issues with the brakes. It is common that the brakes will heat up after you use them. The less you use them, the less they will heat up. If you have enough runway available, you can tap your brakes to disengage them at about ~90 knots, and use manual braking as necessary to stop after. After landing (or when you get the HOT BRAKES alert) turn on the BRK FAN by clicking this button here: This will help to cool down your brakes after they have reached thermal equilibrium (or peak temperature). Thanks!

Thanks we'll look into it.

On the EFB you'll see an option for the On-Screen Keyboard. Enable that and enter your your Simbrief Pilot ID using that within the EFB. Do not use the Xbox Overlay keyboard as it doesn't actually register the input, even though its seen on screen. Thanks!

Hi @RosstheBoss Sometimes Xbox version of MSFS fails to initialize the proper connection required to download the necessary files from Simbrief servers. If you are facing this issue, please restart the sim as that will force it to re-initialize. You could also try to delete and add your Simbrief Pilot ID in the EFB and MCDU again. Thanks!