I'm not sure if this is specifically related to online flight, but this is when I noticed it. I flew from KMSP-KPHX on VATSIM using SquawkBox 4, and FSX. Everything was working perfectly during the startup/taxi/takeoff stage. There were no controllers online at that time and I had no problems. About 100 miles from my TOD, I got a call from Albuquerque Center to contact him as he was now online. I dialed him in and was told to "descend at pilots discretion" via the published STAR. As I was currently flying along at FL360, I had previously told the FO to set the dial to FL310 before being told to descend (per charts and FMC readouts), but after I was told to contact him. The FO did set the FL, but I did not receive an audio confirmation that he had. I saw the digits moving and the green bar came up with a textual confirmation but nothing vocal. I switched off the Voice system (I remember this working in the LDS767 version if there was a "catch") but this didn't work, either. He still did what I asked but no confirmation. Also, when I asked for the checklists, I would get no response. My only suspicion is that this is an issue with Squawkbox and not with the program itself, as it has always worked nearly flawlessly. I saw "nearly" flawlessly because there is one other issue which I don't want to make a separate post about. Online and off, when I press "Shift+/" to arm speedbrakes, they arm just for literally a half second before going back down to flight position. The green light comes on in the cockpit saying "Spoilers armed" but then immediately goes off. Setting them by hand, ie opening the panel window and using mouse to move the spoilers to "armed", does not work as the indicator light does not come on, and the FO does not acknowledge them in my checklist as being up ("Are you sure about that?"), but upon landing the spoilers do come up on their own like they should. I'm not sure if this is an iFly issue or FS2Crew related as I mostly fly with FS2Crew now, but I am nearly positive I flew without activating FS2Crew and the spoilers worked like they should. Again, this is with FSX, I have yet to use FS2Crew iFly with FS9. Thanks for a great product, Bryan, and I hope you'll release more. I always recommend FS2Crew to fellow simmers. The iFly version is 100 times better than the 767 edition which is still a great product but a dated payware plane. In fact, I plan on using the 767 with FS2Crew Voice for Cross The Pond this month. You have a lifelong customer in me.

Hi, Glad you like it! Squawkbox: Does it happen "every single time" when using Squawkbox? Or is it something that just happens every now and again? Spoilers: Not sure, you'd need to ask iFly.

Bryan,I did further testing and cannot definitively confirm whether or not FS2Crew FO quits being heard while flying online. As best as I can tell, it was a one-time issue that hasn't reoccurred since then. I will do more testing and if it is an issue more than one other time, I will report back here. I see no reason why it should quit working. My hardware is setup properly so it must be that my hearing is going. As for the spoiler issue, I'm not sure that it's an iFly issue, as when I was on the ground at the gate before start, I engaged the "Arm Spoiler" and it did just that. I repeated a couple more times to be sure and it worked. After starting FS2Crew, it went back to popping up momentarily before going back down. I got around this by programming my "Down Arrow" for that particular action so that during the approach checklist, I hold the Down Arrow in position long enough for the FO to confirm speedbrake is armed, then release it. After the checklist is complete, I'll manually move the spoiler lever to the Arm position for landing. It's crude, but it works. Again, I will do more testing with and without FS2Crew and report back.

I would really need reputability.If something only happens once out of a 100 times, it's meaningless unless I can reproduce it given the plethora of possibilities associated with the multitude of hardware, software, driver combinations out there.

Thanks for the continued interest in this, Bryan. I think I found the issue. It seems my control sensitivity on the iFly is too high, so if I hold the keys for just a millisecond too long it will counteract any attempt to keep the spoilers in the "armed" position. Will have to tinker with my settings and see if I can reduce the sensitivity so that it is flyable if I'm not paying attention to how long my keystrokes are. Again, thanks!