UA124567

I don't know if this has been reported or not but with the new update 1.0.6, the "100 Above" and "Minimums" callouts do not work even if the appropriate values has been inserted on MFD/FMS (Baro or Radio).

I was on v1.0.4 earlier and had flown numerous flight since installation and never encountered a single wasm crash before. I have updated the A350 to v1.0.5 earlier today and have flown both A359 and A35K for same approach I tried last night and this time every thing worked like it should be. I'll continue to monitor this and make another report if I do encounter wasm crash again.

I encountered a very strange behaviour this evening where the A350 displays got frozen some 200ft above the ground. Every in the airplane frozen but the airplane kept flying and I was able to land it visually. Once on the ground nothing worked including throttles which were stuck in climb detent position. Have a look at screenshot below - I'm parked up on gate yet everything is still frozen. I was flying the RNP approach to runway 09R into London Heathrow with Navi graph charts loaded onto OIS Aircraft: A350-1000 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: Crash on approach to RNP approach 09R at London Heathrow, NUGRA1H arrival loaded with BNN transition. OFP - https://www.simbrief.com/ofp/flightplans/EGPHEGLL_PDF_1742770712.pdf WASM Error: Sorry don't have it

It will definitely be more then 50 dollars - Although the actual pricing has not been revealed, someone did ask this question the other day on stream and I believe response from developers was under 80 Euros excl VAT, so with VAT (depending on region) it could be above 80 Euros.

A350 is going to be inibuild's flagship product, with over many months and possibly years of development work. There is no way it will be free. Price wise I'm thinking something like 70 or 80 dollars.

Okay update - I did a same flight again, Same aircraft, same route, Same airport scenary - No crash this time and was able to do 5 Touch and goes without any problems. I don't know what happened earlier, This ntdll.dll crash sometimes happens not only in A300 but with other aircraft too.

So I updated my A300 via inimanager and initially the airplane loaded fine and I was able to make a departure, however on approach - my sim crashed for no apparent reason. Looking into windows event viewer I can see faulting module is "ntdll.dll". I'm on windows 10 with MSFS, 32GB RAM and GTX 1080 graphics card with medium settings. Flight I was undertaking was KMEM-KMEM (training flight, I'll try this flight again later tonight)

Thanks - I did notice that my controls are over sensitive with particular airplane compared to others, I will have a look at controls again. At same time will try to record this anomaly next time it happens.

Yeah forgot to mention - every time on approach I am on VAPP speed with A/T disconnected at 500ft AGL and on glideslope.

On the latest version I noticed that every time I land A300, after touchdown it either bounces back into air or looses complete control. Take today for example - I was landing on KMEM runway 27 with literally no wind whatsoever and after touchdown, the airplane immediately swinged almost 180 degrees to right and comes to complete stop. It looked like it hit an obstruction or something but there was none on runway (Orbx KMEM scenery). In fact similar behaviour was noted at other airfields during landing. After a almost after every perfect landing - the airplane loses control - something is wrong somewhere. Any suggestions?

Okay I just did another flight from KMEM to KJAX and this time VNAV worked fine in showing the vertical profile - one thing to note however on T/D the target speed went back to 210 kts way below green dot speed at this stage, The 210 kts restriction doesn't come into effect until STAR termination point at CEDOT. I flew the OHDEA1 arrival for RNAV Z RWY 08.

Hi there! Thanks for your response, I was flying HYTHR3 arrival into KMEM with ILS 36L selected as my landing runway. Even today I was flying this arrival and VNAV got me down quite early - in fact I changed to V/S to better match the profile. - Route used "-N0466F340 DCT BACEN DCT BLOKR DCT BEKKI DCT ENL DCT NMANN HYTHR3" KORD/KMEM. No SID on dep, STAR/APP as per above - CI - I use 35 for all flights, (ZFW was around 120.0 Tonnes, Block fuel around 13.6 Tonnes), Cruising altitude FL340 - Nav data - I use Navigraph as my primary navigation database. Unfortunately no screenshots available for this flight however I got 1 more flight planned for this evening, If I encounter any anomalies then I shall take screenshot and post it here.

Anyone else noticed that VNAV no longer provides accurate profile for descents after the recent update. I did couple of flights after the update and every time VNAV prediction seems to be odd, I had to manually take over to stay on profile yet VNAV tells me I'm too high.

Anyone? Do people even use NDBs?

Correction NDB beacons not ADFs, my mistake