sagitta424

I think that this is a very unrealistic request. Checklists, flows, procedures, that's what it's all about in real life. Trying to avoid problems by standardization and repetition. In all my (both IRL and Sim) flights I've always used checklists and I never got/get bored of flying. I do sometimes wonder why I don't use a checklist when I drive my car :-). Just my 2 cents ...

Two mice/mouses will work (just tested it), but they will operate on the same cursor (arrow). I wouldn't know how to get a second cursor on one PC. And what about framerates? I also don't think that you can run two instances of Flight Simulator on one PC, let alone assigning two different yokes since there is only 1 fsx.cfg ...

Thank you Julio, great stuff!

This happened to me in one of my first flights (before any of the SP's). I had no clue about what was happening, since I was flying with all failures disabled! And sure enough, when I landed, the right landing gear failed and my right wing touched the ground. Never had any failure since though (still everything disabled).Best regards,

+1

Great story, thanks for sharing!Only experience I have so far is a touch and go in a real A320 simulator in a Tokyo science museum, where I could only handle the primary flight controls myself (great fun though).

Thanks Mandy! That did the trick, everything back to normal now. There was a weird tailnumber, nothing to do with JAL at all. I believe that it was a tailnumber that I used a long time ago on the default 737, long before the NGX was released. No clue where FSX dug up this number all of a sudden :-) ...Best regards,

Hi all,Before installing SP1c, I uninstalled my liveries. Then after the install of SP1c I reinstalled them. I didn't save any old files, as I'm not advanced enough to fly with failures yet, so the actual number of hours flown is also not important to me.Just now I loaded the Japan Airlines 800WL and there are quite a few differences from the plane that I flew before SP1c:- no HUD- different secondary altimeter and horizon- Honeywell in stead of Collins MCPAlso the plane started C&D in stead of ready to fly. I didn't change anything in the JAL livery, not before and not after the installation of SP1c.When I check JA320J.ini I find for instance HGSInstalled=1 where I suppose "1" means "yes". So I wonder, why does the plane show up in a different way than before (and not even in accordance with the ini file)?Best regards,

Thank you guys a lot! I can't help noticing that you all are working into the early hours of Sunday morning ...

I think you meant 109.10?I just flew the approach in the Duke B60. It captured both localizer and G/S. I won't have time to fly a second attempt in the NGX today, but I will try tomorrow. Anyway, thanks for helping me :-)!

I flew STAR: STM1M and Transition: FSK. So inbound from BALAK, with R-092 as IAF. I made my final turn towards the runway at FSK, no holding, no procedure turn. This was how it was demonstrated during the course and how the FMC wanted to fly it, after entering the Approach, the Star and the Transition.

Well, that is exactly what I would have expected, but I don't know all ins and outs about Navigraph's AIRAC data. I could imagine that there is information about both the centerline orientation and that of the localizer beam. But just guessing, I have no clue.So, I could imagine that the AP won't do the job based on that discrepancy, leaving the PF with indications on the PFD but still making this approach something you have to hand fly anyhow.I will try this again tomorrow, but download the Navigraph charts in stead of using the charts provided by my FS club.Best regards,

This was my first approach on an airport with a localizer offset. On "normal" airports I never saw this happening. I guess it won't be easy to find another runway like that. This airport was chosen for a training flight by someone in our local MS FS club. Maybe the best thing to do is give it another try. I could also make some screenshots then. This time it took me by surprise.

Yes, I did.

Hi Captains,Today I made the ILS 25 approach on ENBO (STAR: STM1M Transition: FSK).The localizer has a slight offset to the left of the runway due to some hills in front of the runway. The ILS course was 264 degrees and I imagine that this is the value including the offset. But although both localizer and glide slope were indicated on the PFD, I couldn't establish on the localizer nor catch the glide slope. They were both annunciated as next mode (so in white), but that's were it stopped.On the ILS chart the course was 268, but I thought that the FSX info was just outdated and therefor I should use 264.Is there a reason why the AP won't engage in this situation? Is it because the course deviation between centerline and localizer? Was I wrong and should it have been 268 after all?Best regards,