Teflon_490

Yes, I use FSpassengers, but I am sure to uncheck the box to forbid it to operate doors.One more thing I recall - in the previous versions of FS2C, I sometimes got the DOORS warning lit up on the master caution panel, but only on the second leg. I never knew why, but it didnt affect anything. It is only from version 1.5 that it actually does something more than just warning. And another thing, for me, the cargo doors are opened and closed together with main pax doors, via SHIFT+E. I am not sure if iFly even models separate cargo doors operation. Does FS2C operate somehow cargo doors independently?

Ok, but its basically the same what has been discussed previously in this thread. Users had to disable automatic door opening to be able to fly second leg. I guess they still have to disable the doors operation in the config panel to fly turnarounds properly. But no big deal, if it works, I dont mind operating the doors manually.

No Airstairs, iFly version 2.1 installed from the main installer, I also recently installed Win7 Ultimate 64bit, so FS is also installed from the scratch. The same thing was happening to me before the reinstall, and its definately not because packs would be off, this is clearly due to some doors that are opened by FS2C probably at the end of the flight and not closed before starting another leg. I have no problems whatsoever on the first flight, this happens only after the turnaround. This is easily reproducible, it happens on every second leg. I will give a try disabling doors operation in FS2C config panel and see if it helps, but I think it will.

Hello I just wanted to ask. I still get cabin alt warning on the second leg, also the FSPax detect this as forgotten opened door. Strange thing is, there are no doors open visible from the outside, nor there is any indication on the overhead panel. Is this fixed already in the current last version 1.6? Because if yes, then it must be something wrong in my setup. In the changelog there is mentioned something about the cargo doors, but I am not sure if it is related to this problem. Thanks

Here you go:http://ifly.flight1.net/forums/forum_posts.asp?TID=3105&title=get-the-ifly737-for-fsx-here

I see, I misunderstood the question. Actually, I though those are 2 questions, one for L/R ignition, and second for engine start sequence.

Actually, I think the most common practice is to change the ignition from day to day to achieve even wear. For example left on odd days, right on even days.

Hello DanielIt has been already discussed here http://forum.avsim.net/topic/325044-sound-channel/ and the outcome is, that on some systems it is just like this, we haven't found the reason for this so far. I think you gonna have to live with this.

The only thing I experience is that sound is of "normal" volume when FS2C panel is opened, while as when the panel is closed, the volume of all FS2C voices is suddenly lower, but it still can be heard well. No sound distortion of any kind.And dump XP for running FS9? Why? Everything has been working well for me ever since, I am sure I would bump into some installation problems at least on Win7, with all the additional programs I use with FS9. Plus, I doubt it is XP what is responsible for dongkiyu's problem.

Can you please confirm what do you mean by "won't come on"? Do you mean that taxi light switch is not automatically switched by the FO, or that the switch is on but you don't see any light on the ground?

Yes, I figured out myself that this order works, I just thought that the manual states correct sequence, so I wanted to ask. No problem, I will call it like this, it works flawlessly then. Thanks Bryan.

HelloAfter I updated to V1.2, I noticed a little glitch in the before start and pushback procedure. If I understand correctly from the manual, sequence is:- before start procedure- call ground for pushback/startup clearance- before start checklistWhen i do it this way, everytime i call for "before start checklist", the secondary action reverts back to pre-pushback action and I have to use the arrows to get back to the "brakes set" state. This did not happen to me in V1.1, so I am asking, is this happening only to me, or does this glitch happen to everyone? Or am I doing something wrong in the procedure?

HelloThis is well documented feature and has nothing to do with FS2Crew...you can find many threads about this over the iFly support forums. If you want to engage CMD A or B, you must do so only when the aircraft is fully trimmed and you must not apply any pressure to the yoke. Only then you can successfuly engage the AP - this behaviour is the same in the real aircraft. I can also see in the video, that you definately don't follow the standard procedure after takeoff, you are trying to engage all at once, retracting flaps even though the speed is well below the retraction speed, and so on...I recommend stabilize the aircraft first, reach the flaps up speed, retract the flaps, trim the aircraft so that when you release the yoke it flies itself without you having to interfere, and then it should be possible to engage the AP.If it still won't work, there is also possibility, that your controller might be "noisy" - causing little oscillations of the axis even when you don't touch it. You can try to disable your controller within FS - there is a special setting for this in the assignments menu.

Really? And I thought he does...then it must be the feature of the iFly itself, because everytime after landing the stab trim is set automatically to 4.0 units as per operation procedures, I can even hear the sound of the trimming wheel.

HelloI have to confirm I have a very similar problem. Sounds that are supposed to be heard from both channels, as captain for instance (but even the clicks when a button is pressed), are heard from the right channel. When I listen closely to the left speaker, the sound is there, but it is very faint, so when listening in the center of both speakers the overall impression is that all FS2Crew sounds come from the right speaker only. All other sounds in the Flight Simulator are perfectly centered.I have an Creative X-Fi soundcard, XP SP3 - I have never had any problems with the sound before, I use 5.1 channel setup and all the required channels are properly heard in other applications I use.Michal Pospichal