Quick question. I'm enroute right now, Fort Lauderdale to Las Vegas, running RC v3 on WideFS. I'm using the PSS A320, primary comm is VHF2, but I've tried it with VHF1 as well. I can't seem to get option 1 or 2 to work. For instance, I can push 9, get 'next' ask for higher or lower. Can push 3,4,5,6 to get higher or lower altitudes, but RC won't acknowledge pushing 1 or 2. What gives? At first I thought it was the second computer that was giving me problems, but 8,9, and 0 all work, then when I get to a menu that's got 3,4,5,or 6 they work as well. Does my problem stem from using the PSS A320? Does the PSS A320 have a second radio installed?Any ideas?Thanks,Lobaeux

Lobaeux,1 and 2 are for engine control (from the keyboard). I have reassigned 1-4 to CS-1 to CS-4, so there's no conflict, and I can use 1,2,3,4 to manually adjust any/all engines, and do pushback.

I didn't even think of that!! Let me change these around and see if that fixes something, thanks Scott.Lobaeux

Nope, didn't work. I changed each 'select item 1' to ctrl-1 that didn't work. I think it's a problem with the PSS radios. Doesn't matter if I select VHF1 or VHF2, I still seem to get the same MS ATC radio calls. I think RC 3 is not recognising the 1 or 2 buttons because MS ATC is blocking them somehow. Is there a gauge like the one from the previous edition of RC that you can use with the mouse, I can't remember the name of it or where I got it from?Thanks,Lobaeux

I have the same problem with keys 1 & 2 using PIC 767 with WideFS.Steve Canham, President/CEOWestWind Virtual Airlineswww.flywestwind.com

Lobaeux,I don't recall if the PSS panel has separate Com1 and Com2 radios, or if it's swapable. If I remember correctly, you might need to install the default audio panel (and maybe even the default Com2 radio), then make sure "Both" is not selected. Then set Com2 as active, and FSATC will play through there. Then RC will stay on Com1.However it's done on the PSS panel, if there's a way to unselect "Both", do so, and make Com2 the active and see if that helps.There have been a few posts regarding this, so you can search for PSS A320, or wait until someone comes along to respond here.

I added in the 737 audio panel to my PSS A320. It started working last night, then FS Maintenance caused my left engine to fail so I had to return to KPHX. I've got to say it's my first emergency with RC3 and it worked perfectly. Even Otto was a little excited, but the controller was calm and did well. I also installed MiniCP, it's kind of a pain, always being visible, but for right now I'll use it if I can't get the com 2 working.Thanks,Lobaeux

Hi LobaeuxNot sure if I understand you, but isn't crtl-1-4 "prop control"? I have been using the PSS A32x for a mount with RC3 with no problems -(Or I might have overlooked them!)What I do is - assign every short key in RC3 to use crtl/shift. So 1 is assigned to crtl/shift-1, 2 is crtl/shift-2, etc..- On the radio stack I select VHF2 - and "bobs my auntie" - well at least for me. ;-)Cheers-Lars H

I plan on trying MiniCP on my next flight later today. I have dual monitors set up on my primary computer (host) so I have plenty of room for extra gauges. Should be just the thing for me if it works. I have experience the same problem the last two fights. I start out with the comm and 1 & 2 work fine. After airborne, I switch the comm to Otto and she handles things from then on. Once we land, I switch back the comm to me, but 1 & 2 don't work. Can't even get my critique! :-(Thanks,Steve Canham

Yes, exact same thing for me, unfortuanetly MiniCP is a 'sticky' gauge, and haven't toyed with it yet. I'm going to set my other monitor up to run it. I tried to get it to run with WideFS on my networked computer, but it didn't like that either. Lobaeux

Folks,I have seen the same problem with 767PIC. I have discovered that if you click on the cockpit scenery window the keystrokes go through just fine, but some of the other panels seem to block them if they are focused. Try clicking on the outside view, then use 1 or 2 keys. Works for me.Kevin>Lobaeux, >>1 and 2 are for engine control (from the keyboard). I have >reassigned 1-4 to CS-1 to CS-4, so there's no conflict, and >I can use 1,2,3,4 to manually adjust any/all engines, and do >pushback.

I see what you mean about 'sticky'. I believe I have 1 & 2 working now after changing all my commands to use Ctrl Shift. The MiniCP would be much nicer if it were easier to move around. It appears to be kind of trial and error, although I haven't spent any time with it. I would like to get it on my second monitor, but I'm not sure that is possible, but since I let Otto take the comm when airborne, I may just create a tray icon and turn it on and off when I need it.Steve

Follow-upIt turns out that both CS1 (Ctrl-Shift 1) and CS2 (Ctrl-Shift-2) are used by PIC and after trial and error I believe found two that will work - CSA and CSC. I haven't had a chance to test since changes don't take effect until FS is restarted (I'm in the middle of a nice trek from Denver to Billings). If those don't work, I'm sure I will be able to find some that do. Thanks to the fine programming of Radar Contact V3 and having the forsight to give us the ability to make custom settings.Steve Canham