Hi Bryan,just purchased your iFly VC: When I open the CFG, it seems to be something wrong with the audio Setup. It says "No such device" under Headset device and the box for Crew region is empty. I can hear every sound except the FS2Crew related things Everything else seems to work as far as i can tell...I tryed "HS" on and off, no difference, "HM" is offI run W7-64Pro (plus Vistalizator)FS9.1IFly SP2.1I checked the FS2Crew Voice in the iFly Control panel (as admin)l loaded the ifly after the default Cessnathe panel CFG's are from 16.4. and containFS2Crew lines, so i guess they are updatedi use Soundblaster X-fi xtreme, onboard sound is disabledThe only thing is, i do not use a USB-headset but I also own your VC for the Level-D and have no problems with that Version at allany Ideasthanks and greetings from ViennaStefan

Hi Bryan,just purchased your iFly VC: When I open the CFG, it seems to be something wrong with the audio Setup. It says "No such device" under Headset device and the box for Crew region is empty. I can hear every sound except the FS2Crew related things Everything else seems to work as far as i can tell...I tryed "HS" on and off, no difference, "HM" is offI run W7-64Pro (plus Vistalizator)FS9.1IFly SP2.1I checked the FS2Crew Voice in the iFly Control panel (as admin)l loaded the ifly after the default Cessnathe panel CFG's are from 16.4. and containFS2Crew lines, so i guess they are updatedi use Soundblaster X-fi xtreme, onboard sound is disabledThe only thing is, i do not use a USB-headset but I also own your VC for the Level-D and have no problems with that Version at allany Ideasthanks and greetings from ViennaStefan

Hi Stefan,I was on the beta team and found that with the DirectX file update that FS2Crew does after I plugged on my headset I had to go in to Control Panel=>Hardware and Sound=>Sound=>Manage audio devices and select my headset as default under both Playback and Recording. Only had to do it once (but had to do it every time I re-installed) and since then no issues at all.I have Vista and a USB headset so YMMV. Give it a try and let us know how it goes.Thanks,

Hi Bryan,just purchased your iFly VC: When I open the CFG, it seems to be something wrong with the audio Setup. It says "No such device" under Headset device and the box for Crew region is empty. I can hear every sound except the FS2Crew related things Everything else seems to work as far as i can tell...I tryed "HS" on and off, no difference, "HM" is offI run W7-64Pro (plus Vistalizator)FS9.1IFly SP2.1I checked the FS2Crew Voice in the iFly Control panel (as admin)l loaded the ifly after the default Cessnathe panel CFG's are from 16.4. and containFS2Crew lines, so i guess they are updatedi use Soundblaster X-fi xtreme, onboard sound is disabledThe only thing is, i do not use a USB-headset but I also own your VC for the Level-D and have no problems with that Version at allany Ideasthanks and greetings from ViennaStefan

Hi Stefan,The internal system is unchanged from the Level-D 767 version, so if it worked in the 767 it should be the same in the iFly.Check your system settings.Cheers,

Hi,I checked my settings, then startet FS and opened the iFly CFG and the Level-D's. As you can see on the screenshots, the one is working the other not. I tryed different settings and rebooted the pc, no change. Any ideas?iFlyLevel-D

Hi again,I did a reinstall, seems to work now. Dont realy know what happened...Thanks for your quick replys anyway. Lets check it out now ;-)Stefan

Hi again,I did a reinstall, seems to work now. Dont realy know what happened...Thanks for your quick replys anyway. Lets check it out now ;-)Stefan

Glad you got it sorted!You had me scratching my head there!Was probably just a bad install. Cheers,

Sorry for bothering again, it seems this is not my day...Just did a short flight, everything good so far, besides one thing:When I ask to set a certain Flap setting (no matter if pre T/O or pre LDG) the FO reads back correct but always sets Flaps FULL!I tryed with a 700 and a 800, same thing...

Hi Bryan,I am using this thread, if you think it’s worth opening a new one, please move it.The flaps issue worried me; I did some testing and found numerous things which didn’t feel right.So I de-installed the iFly737 FS2C-VC, did a manual clean, rebooted the PC and installed it again according to the manual. All the things that didn’t work correctly (in my eyes) are still there and since there are no other complaints here in the forum I am even more confused. As you know the Level-D VC runs without any issue here on my PC!Main issue - the Flaps:- Commanding a certain Flap setting always results in Flaps FULL- Telling him to retract them (after T/O) let’s say Flaps 1, results in Flaps UP - As if he only knows Up or Full, no matter what you tell him. BUT the readback is always correct. - Gauge, Flap lever and Flap position (outside view) fits together- Before Taxi I told FO to set Flaps 5, he set it to FULL, so I retracted them manually to UP to see what happens when doing the Before T/O checklist. Even though I told him Flaps are 5 and 5 was set in FMC he didn’t complain while doing the checklist. - Same before the Landing: only Full, no matter what you tell him, retracting was also not possible anymore (only manually)- It’s possible to tell the FO to set the Flaps even if you are way over the Flap-Speed (I tried 320 knots) is this different to the 767?I am not that familiar with the 737 but here are some things I am also curious about:- Preflight: the FO starts LEFT AFT Fuel-Pump AFTER he started the APU (shouldn’t it be before?), he also turns on the LEFT CTR Fuel-Pump for the APU- After he switches ON the window heat, he switches it off and on again- I arm the Speed-brake on Approach (green light is on), FO confirms ARM during Landing checklist (no “check that…” or something) but on touchdown he says “Speedbrake doesn’t come up”?!I experienced some other things, but I need to double check them first, to be 100% sure it’s not me. For ex. I think the Status was switching without trigger, I did Approach brief/checks, Decent checks, and Status bar showed “Landing”, shortly after that it showed “Approach” again but I didn’t touch a button. Here you also can do a checklist several times, on the 767 you could only do it once safaik! Is that correct?After the 3rd reinstall and some hours of testing I hope you have an Idea Bryan ;-) I doesn’t seem to be a bug in your software, but I have no clue what went wrong….ThanksStefan specs. are in the first post btw.

Hi Stefan:Flaps: We never experienced that during testing. Are you using any hardware or other programs that attempt to control flaps? Is the Green Bar showing your correct flap command? Do you have the latest SP from iFly installed.Fuel Pumps: This is documented in the manual in the FO flows section. Those pumps are turned on for fuel balancing purposes.Window Heat Off then On: That's part of the test procedure. Remember everything you're seeing was created and checked by a real-world B737NG Captain.Speedbrakes: Please look at the wings to see if the spoilers physically came up.Trigger to go from Approach to Landing is "Set". Cheers,

Hi Bryan,Here an example for the Flaps before T/O when i command "Flaps 5". As you can see, "green"-bar shows Flap 5 correctlyFlap indicator passes 5 (green light illuminates) but moves forward to FULL (also the lever and the Flaps itself are at FULL) I am using the latest SP2.1 iFly version. For the Flaps I am using an assigned axis on the Saitek Trottle (latest FSUIPC) i can select any Flap-setting i want manually, F6 and F7 (=default FS9 key assign.) also works for setting the Flaps to any position.The Flap-Lever (on the Saitek) stays untouched the whole time in UP position. During one test i disconected my Throttle and Yoke, but no difference. Speedbrakes and the other stuff i will check later on a complete flight. As for those other things, I just wanted to find out if my instalation is totaly messed up or if there is "just" the Flap-thing...I also think its my system and not your software, but since my LevelD Version works, only you can tell me what the difference is...thanksStefan

Hi Bryan,Here an example for the Flaps before T/O when i command "Flaps 5". As you can see, "green"-bar shows Flap 5 correctlyFlap indicator passes 5 (green light illuminates) but moves forward to FULL (also the lever and the Flaps itself are at FULL) I am using the latest SP2.1 iFly version. For the Flaps I am using an assigned axis on the Saitek Trottle (latest FSUIPC) i can select any Flap-setting i want manually, F6 and F7 (=default FS9 key assign.) also works for setting the Flaps to any position.The Flap-Lever (on the Saitek) stays untouched the whole time in UP position. During one test i disconected my Throttle and Yoke, but no difference. Speedbrakes and the other stuff i will check later on a complete flight. As for those other things, I just wanted to find out if my instalation is totaly messed up or if there is "just" the Flap-thing...I also think its my system and not your software, but since my LevelD Version works, only you can tell me what the difference is...thanksStefan

Hi Stefan,To control the flaps in the iFly, I send a command via the SDK provided by iFly.In the Level-D 767, FS2Crew sets the flaps using an 'event command' from the Microsoft Panels and Gauges SDK. That's the difference.It's not the software itself or I'd be hearing about this a 100 times a day.I'll forward this to the iFly developers and see if anything can be done on their end.The problem is simply that your hardware is overriding the iFly SDK.Cheers,

Thanks for your quick reply Bryan,so if i understand you correct, there is nothing i can do about it at the moment?other saitek (or other hardware?)-users could have the same issue?it could also explain the thing with the Speedbrakes?Stefan

Thanks for your quick reply Bryan,so if i understand you correct, there is nothing i can do about it at the moment?other saitek (or other hardware?)-users could have the same issue?it could also explain the thing with the Speedbrakes?Stefan

All you could do is disable your external hardware to the extent that it attempts to controls flaps, etc.I have however contacted the developer of iFly. Since it's his SDK, any change would need to be made on his end.Best,

just to make sure we are talking about the same thing: the Flap issue is also there with Yoke/Throttle unplugged!

just to make sure we are talking about the same thing: the Flap issue is also there with Yoke/Throttle unplugged!

Hmmmm, another user said this (from the button control version):

Only been using FS2Crew for a few days now. Had a similar problem with flaps. The flaps lever [separate Saitek Throttle Quadrant] was assigned and calibrated with FSUIPC . Removed the assignment in FSUIPC and all good now - FO does the flap settings.

Try removing the assignments from FSUIPC.