Thomas L.

I didn't tried to click on the hatch. I've read some people report that there's no clickspot on it. I've also read a number of times that manual extension simply wasn't modeled (not only talking about the gear animation). Let met check that tonight when I get home Thomas

True, but after a given system has failed, you just have to go to the system's maintenance page and check the next maintenance schedule. Thomas

As you cannot lower the gear with no hydraulics, and because manual gear extension isn't modeled (yet), it's actually quite hard to land it properly. Tested yesterday... belly landing ended up not so good ;-) But it is really interesting to control the plane without hydraulics A&B (only STBY). It's really slow, and quite hard to control the pitch without extensive use of the stabilizer trim. For the interest of the simulation, i've setup random failures at a rate of 1 or 2 per 10 hours. Makes flying more interesting, and you better have a printed QRH handy. Thomas

I too use FSUIPC for all axis and buttons. Aileron, Elevator, and Rudder axis are "processed" to have a lower sensivity at small deviations. Throttles aren't processed and work fine with A/T. However, brakes are also processed and seem to prevend autobrake from working correctly. I think I've even read this in the NGX manual.

OK I tried with the VNAV Circling Approach procedure of RyanAir (published on SmartCockpit). Landing field is LFOT [IAC]. The ILS 20 was programmed, TUR being the IAF. LOC was intercepted in VOR/LOC mode, the vertical mode was VNAV PTH stable at 1900' until the FAP. MAP was set to the circling altitude (1230'), MCP Altitude was set to 1300', MCP heading was set to 151º. At the MDA, it leveled in VNAV ALT, I engaged HDG sel, started timing to join the downwind leg. As soon as I passed the RWY 20 threshold, the FMS sequenced the next waypoint to TURNB, as part of the published missed approach procedure. VNAV disconnected, and the Vref speed was deleted. Did I messed up somewhere? Thanks guys

I successfully activated my freshly-bought copy of AS2012 today (07 apr) at approx. 1100Z. If multiple customers report a similar problem, you should just wait for the issue to be resolved by the ActiveSky team ;-)

Maybe you should re-read my post ;-) I said I am *not* searching for a way to circle in LNAV. ;-) You can define multiple routes, but I never tried to activate the secondary route while in flight. Not sure it is possible. However, it is possible to re-select the appropriate runway from the ARR/DEP page of the MCDU while circling, but I was searching for a way to avoid dealing with the FMC while circling. Thanks everyone!

I could select RWY 31, but you cannot select RWY 31 while keeping the ILS 13 programmed. Thanks for the document, very nicely explained! Thomas

Nothing airport-specific here ;-) I am not searching for a way to keep the airplane under LNAV control, just make it aware I am not going to land on the runway associated with the instrument approach i'm doing. I wonder how it's done in real life, but my searches aren't successful ;-( Thanks,

Do some real-world airline actually use EFIS?!

Hello guys! Today I had to do a circling approach and had to face the fact that I had no idea how to correctly setup the FMC for this. What is the correct way to do? The FCTM doesn't say anything really interesting about this. I had programmed the ILS approach to RWY 13, flown it manually to circling minima, then started my circling maneuver to RWY 31 as usual. But of course, when I passed abeam the MA (Missed Approach) waypoint, the FMC started thinking I was going around. How do you do that correctly? Thanks!

Bought AS2012 today, the weather engine is really impressive and realistic! Didn't get any wind shift, textures are nice (but I am not a graphics aficionados), so it's perfect for me. The UI and the Xgauge are a little disappointing though. But not a single problem with the NGX. They are doing a 30% off-price, so it's the right time to buy!

Oh? Maybe I wanted it so much that I dreamed of it... ;-)Thanks,Thomas

It seems fixed in the new SP1c. I was also annoyed by the slowly-changing value, but now, the value is incremented by 10ft steps when you keep turning the mousewheel, as for the altimeter setting.Thomas

Installed it yesterday, on top of an existing SP1b NGX. Tested it today, I did a couple of approaches / go-around, and everything went perfectly OK for me. Great job guys!I've also read the new tutorial, and it is amazing. I wish I knew how much the FIX page of the MCDU could be valuable! Thanks Ryan!Fly safe ;-)Thomas

Hello,The NGX is perfectly flyable without this tutorial. Just take the time to read the FCTM and the FCOM you paid for. Tutorial #2 is only a "free bonus" - you didn't "pay" for it.Thomas

If the entry is not intended to be in the "Instruments Panels" menu, then it would be nice to be able to bring the window back by re-calling the guy using the MECH button on the overhead panel. The button works the first time, but if you ever close the Ground Comms window, re-clicking it doesn't do anything :(Anyway it is not a big deal once you know it. BTW another guy on a forum told me he encountered the same issue. ;)Thank you!Thomas

Hello!I just bought FS2Crew for the ATR, and I ran into a little problem: like (probably) every beginner, I messed up several times :( One of my mistake was closing the Ground Comms window after requesting Hotel-mode startup clearance.When the time came to start the engines, I wasn't able to find the Ground Comms entry in the Instruments Panel menu: only the Takeoff Data Card was available.After checking in the panel.cfg file, I found that the Window20 (Ground Comms) had the nomenu=1 option set. Is that wanted, given that the manual says we can bring back the window this way? Changing it to nomenu=0 fixed the problem.Strangely, the Landing Data Card window has the same option, whereas the Takeoff Data Card doesn't (i.e. is manually bringable).Apart from this little problem, everything went fine for me. Great job Bryan!Thanks!Thomas