stepell

did the install of the update (your link) and the nav-cycle (Navigraph 1609) again, nothing changed. Still get the crash while FO is doing the Decent checklist into EHAM, no other issues with FS2Crew... is there a file i can manually change (without the installer), just to be sure? I assume changing the FS2audio.dll wont help either? thanks Stefan

Hi Bryan! I have the same issue with the Decent-Checklist going into EHAM (negative elevation) as mentioned above. FS crashes while FO is reading the Checklist. In event viewer I can see it’s because of the Fs2audio.dll I already installed the update you mentioned (http://www.fs2crew.com/cart/pages/FS2Crew%3A-iFly-737NG-Edition.html) but nothing changed The FS2Crew interface says its Version 2.2 and I can also see that some files are updated Also tried switching between Headset and other speakers as you suggested above I am using the ifly 737 Voice Version in FS9.1 on a Win 7 64 Prof System Running it for quite some time now, no other issues so far. Everything is switched of, no Antivirus on this Computer Also tried downloading it from another PC, just to be sure Is there any solution in the meantime?? Thanks Cheers Stefan

In the last days i tried everything i could think of, including reinstall. No changes. is there anything besides "nonsense numbers" that could make ALT and HDG values run away? is there a difference in the logic between the Level-D and ifly (because ifly workes fine)? despite reinstall, could there be a wrong entry in the panel.cfg?

I have my own PC for FS and havent been using it for 2,3 month, so nothing changed except the win updates and the recent update for IVAP.

Hi, I checked everything as you suggested, still the same. The bar confirms my numbers and syntax are understood correctly. The values for HDG and ALT are also reasonable. Any ideas?!

Hi Bryan I am using FS2crew voice for some years now and it worked fine, but in the last days something wired happened: When using the “SET HDG XXX”, “SET FL XXX” commands the numbers go on running. In general I know about this issue. it happened from time to time in the past and a solution is also mentioned in the manual (switch “voice” off and on again). But now it happens every time. Switching “Voice” off and on helps at first. The running stoppes, but with the next command it runs away again. Often I have to do it 3, 4 times till it works normally again and the numbers don’t run away anymore... Maybe not important but I recognized one thing: Normally the numbers change slower when reaching the commanded value e.g. hdg 300 current, “SET HDG 160” - first numbers are changing fast till maybe 170 then changing slower for the last few steps till reaching 160 now they still slow down before reaching the selected value, but pick up again and keep on running also only happened with HDG and ALT/FL not with SPD (so far) all other commands work perfectly I’ve tried countless times even with preselected flights and switching the FS2C panel to the right situation. I am also looking at the green bar in case the system understands something wrong or picks up things it shouldn’t. The commands are also correctly spoken. (as confirmed at the green bar). I also did a reinstall of the software incl. SP but nothing changed. (it works fine with the ifly737 voice btw.) Can you please tell me what is the general reason that these numbers sometimes (in my case always) run away. Since you mentioned it in the manual there must be something behind. My specs. Win 7 prof (all updates) FS9.1 LevelD (all updates) FS2Crew voice for LevelD767 incl. SP As mentioned, didn’t have this problems before, don’t have this problem with the ifly737 I have my own system just for FS so nothing changed except the regular Win updates and a recent IVAP update. Thanks for your answers cheers Stefan

there isn’t. well, there are some paints out there, works for me. To be honest, I don’t care if the Cargodoor really opens anyway, thanks for the reply, PMDG777 sounds good, but doesn’t help, still on FS9 ;-)

Hi Bryan! After a longer time away from FS I started again with some flights in the "good old" LDS767. For me FS2Crew Voice is a must have for any add-on btw. I wanted to do a cargo flight but it felt a little strange with all that "seat the cabin please" "cabin is ready to go" etc. Probably I could just skip some of the phrases but I think some are mandatory or will appear anyway. Did you ever consider doing a Cargo Version? I mean “just” changing the specific dialogues or leaving the passenger stuff. This of course is not Aircraft type related. Thanks Greetings from Vienna

Hi,maybe its the same i had, solution in the last post: http://forum.avsim.net/topic/293161-speed-speed/CheersStefan

Hi Bryan,will there be a solution for the flaps/speedbrake issue (when they are running over FSUIPC) in V1.1 or maybe later?thanksStefan

Hi Bryan, did you get some response from the iFly Team?

Hi Bryan,sorry, my last post was not fully correct: I have a "general" assignment for buttons/axis and an assignment for each addon aircraft i use regularly. Deleting the iFly assignments caused FSUIPC to use the general assignments (thats why nothing changed).So indeed, when Flaps are not assigned via FSUIPC at all, everything works fine.Not a solution, because now i only can use one or the other, but at least we know for sure whats causing it...thanks for your efforts, hopefully the iFly developers make a fix. I am sure I am not the only one using a Saitek (or other hardware) throttle/flap lever and FSUIPCCheersStefan

hi,I deleted the Flaps and Spedbrake assignments of the iFly in FSUIPC, Problem still exists - so no difference ;-(

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

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

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,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.

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 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,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 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,possible i hit the FA button, i will have a look on that the next flights....you can set the angel to more than 90° easily, till 90 it works both ways via the mouse-wheel and right/left klick, over 90 only the l/r mouse-buttons worki found out early because of the gate i am usually starting from when i fly from my home-airport LOWW, but i didnt put to much thoughts in it...just curious, why should >90° not be possible??Stefan

Hello Bryan,in the meantime i did some testing:When I command "Gear up" he recognizes "Gear up" (according to the green bar correctly and nothing else!)then, someone (i guess the flight attendant) says "hello" (nothing else) in the backgroundthen the FO finally moves the Gear lever by himself (maybe 10-20 sec. after my command)it seems the delay on the gear is because of that "hello" (i didnt say anything else in that time!)...everything else works fine from preflight till shutdown...I tried that with a saved panel state "ready for TO" and switched to Takeoff roll, and i tried a complete flight and started at the gate (with preflight option) both time the same result...the latest updates for LevelD and FS2Crew are installedany Ideas?Pushback: can someone confirm that the PBK only doesnt stop when the angel is more than 90°?!Greetings from ViennaStefan

Hello Bryan!I am using FS2Crew VC for LevelD almost from the first Day it was available and I am getting more and more familiar with it (especially the last 3 month's since I have my new PC).Still, some minor things happen on most (not all!) of my flights and I dont know why:1) When I command "Gear up", the FO is responding with "gear up" but he doesnt move the lever, so finally i have to do it(Is it somehow possible that this has something to do with my saved panel state which I use at startup at the Gate? Of course when saved Gear was DWN)2) Sometimes the Pushback doesnt stop, (I guess you are aware of that, because you mention it in the manual). Maybe its a coincidence but it only happened to me when the Angel is more than 90°. 3) From time to time the the FO stops working/responding at all during the flight (mostly at the end). Any Idea what could trigger such a behaviour?4) During cockpit prep. the FO sets the QNH. When flying online (IVAO) its not always the same QNH as i get from the METAR or what is told by ATCMy specs:Win7 Pro64 (with Vistalizator)Fs9.1LevelD, all Updates incl. Winglet updatefresh install since the PC is just 3 month oldMaybe you have some Ideas...thanksStefan

Hi Brian!I think the problem is solved, more or less at least...Just a short note if somebody else will experience similar troubles:Basically Brian was right with the mic settings, but even on the lowest setting i had the problem (winXP)I also had to set the output level on a lower setting (mix-output and FS2Crew panel) to make it work. Finally i found out the FO is "hearing" himself talk - thats why the "speed"-loop (funny thing though, the UK/US FO's "heard" other things they say than the EU FO)I guess its also a characteristic of my headset, it seems it is not that well isolated than i thought (a sennheiser btw.)Now i just have to play around to find the best mic/output level settings. At least i know were to look, FS2Crew itself works fine!thanks for your help