richboy2307

Reported already and noted, see :

Thanks everyone, logged. We'll look into it.

Hi @mustard7627 Noted on the bug list. What aircraft did you have this issue with? Thanks!

Thanks for sharing. I have forwarded to the team.

We're open to feedback and making improvements where necessary. However there are currently no plans to update the external fuselage model of the A300. If you have any more detailed, specific references please feel free to share. However in my personal opinion, I do not see the issue you are trying to point out from anything shown above as yet. Thanks!

Hi, in the EFB Settings app you can select IDC to HIDE and that will revert to the old radios. Thanks!

Hi @LukeFF Currently there is a bug where the INIT B page is pre-filled on spawn-in. You should over-write all values manually with the actual weights loaded into your aircraft. Alternatively, toggling the weight units (i.e. Imperial to Metric and back) from the EFB Options should clear all pre-filled weights. Thanks!

Hi @browns11 As mentioned earlier, it is on the list and will be looked at whenever the team is working on EGHI next. As you will note on the iniManager, the latest version of EGHI is 1.0.1, updated 6 Oct 2023. Thanks!

Noted. We're working on stability improvements for the next update, as we have recently with the A300 update (v1.1.2). In the meanwhile, please keep posting all instances of WASM crashes along with the following info: route you were flying (i.e. active F-PLN) route you had as secondary (i.e. entered in SEC F-PLN) Navdata Used (Navigraph or Default) Airport Sceneries used (The Departure, Arrival and ALTN airport if any was part of the secondary flight plan) Where you were when you activated the flight plan. (Go around, but at approx what altitude and near which waypoint) Thanks!

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!