UA124567

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

I have noticed that my RMI needles does not work when ADF station has been appropriately tuned. For instance I was making an approach on the ILS runway 27 at East Midlands EGNX, As you descend on glideslope there is a altitude check at locator beacon EME 353.5. I have tuned the locater on my ADF selectors on the pedestal panel however RMI ADF indicator remains flagged, in other words - it does not work. I tried this with other ADF beacons and still that does not work. VORs and ILS work fine. Unless I am doing something wrong. I am on latest inibuilds version however same problem occurred on previous build. Any feedback ?

I tell you what I played a hunch and bought the A300 earlier today. I must say the performance is stable in terms FPS and overall stability. I did introductory flight from EGSS to EGLL (inbuilds scenery) and I was getting reasonable performance. Compared to A310, I definitely noticed difference as to how they fly. I find A310 quite jerky on controls, The A300 is just about right. The drawback I found is the sounds, I think Sounds update would be awesome. I am going to attempt a full flight later tonight and see how this bird performs.

Yeah I already own A310 and have flown several flights in the past, Performance in that has been spot on. As of now I understand it is broken because of nav update or something and it is unusable until MS release an update via marketplace to be fixed.