Either the new FSUPIC 2.972 is causing dysfunction in Radar Contact, which I doubt, OR....Am using WideFS 5.41 by the way too, Radar Contact does not seem compatible with PICA320??..... is that possible JD? What I am observing is that upon takeoff, RC wants me to contact the destination approach. Am using it on LAX to SLC run. 135.50 is SLC's Approach!! I've started and restarted several times AND used with a native FS2002 aircraft, which worked just fine. Anyone else having RC problems with PICA320??Randy Jura, KPDX

idea why, but I'll go on and report any further trouble!Randy Jura, KPDX

Definitely something going on between Radar Contact and either FSUIPC or PICA320. It works, then it doesn't. Somehow, keypresses are being denied RC OR it wants to contact Arrival at Destination airport right after take off, this time From KSLC to KSEA. IF anyone else notices, please speak up, I'll certainly keep trying things out, such as reverting back in FSUIPC Randy Jura, KPDX

I as well experience weard behavieor of RC3 and PIC-A320. Sometimes it works without any problems, but mostly it doesnt at all. When I wanna call pushback and ready to taxi I get just that the agnollagement that I may pushback and call ground. Well, no ground there but I have the right frequency for sure and PIC-A320 has it too. When I activate shift+ctrl+k otto sometimes works as he/she is supposed to, but too often he/she doesnt work at all! When he/she works, all the way goes well as planned. Just the PIC-Bug that often I cannot depart without a SID without knowing that a SID will be selected automaticly, so I cannot setup RC3 befor for flexible departure.So, is it a PIC Bug that RC3 acts weard or anything else?

I have not used Radar Contact in a while so its just an idea and you've probably tried it already but have you checked to see if Radar Contact needs the same keystrokes for some actions as PIC.If this is the case then just reassign the keystrokes using the PIC set-up menu.RegardsHoward

Radar Contact for the most part uses keys 1-9 and 0. PICA320 uses those keys + CTRL and SHIFT key in various combinations, so there is no such conflict. What I've done so far is go backwards from FSUIPC 2.97 series to 2.96 and so far, that has fixed the problem infering that something in the latest versions of FSUIPC may be at fault. TORBEN!!: What version of FSUIPC are you using?????

What version of FSUIPC are you using. I think the problem may be with versions 2.97 or higherRandy Jura, KPDX

Well, 2.97. I cannot find a link/WebSite with the older 2.96 version. Could you mail me the one you use without [email protected] a bunchTorben.

on the way! Randy Jura, KPDX

I am still using FSUIPC 2.96 ... and I can only get RC3 to say two or three words and then it stops. HMMMM .. so I cannot get ATIS, cannot get clearance. Of course, MSFS ATC does NOT function either.This is OBVIOUSLY NOT RC's fault .. RC works with NO issues with the Meridian . a high resource sim.perhaps the problem is that PICA320 takes so much horesepower to run, that it blocks out anyone else .. (I can run FS_Meteo though) I can use PICA320 with my aging PIII866/512m with gforce2mx400/64m board, and it flies well .. but without RC .. it's no fun .. and I am sure that FDC won't work either.O well ... maybe a patch for a patch for PICa320 will help. Meanwhile, off to the "waiting for repair hanger" hahahahaOnce you start using RC3 and FDC .. it is absolutely not an option to NOT use both. And the thought of hjving to fiddle with or change settings in one place or another just for a one-off aircraft to work is silly ... I am way too old to have to worry about these things, especially when other a/c work well for me (i.e. PSS A320)

Hi,what I now experienced is that THIS FSUIPC 2.96 doesnt do any good to me. I found out that I had exactly the same FSUIPC befor figured by the file size etc. So, I gonna try the latest one out with the PIC-A320.Regards,T-A-H MultiMedia Productionshttp://www.t-a-h.com[email protected] TB 2400; Epox 8k3a+; 768MB 2100 DDR; Aopen GF4 4200 550MHz; CH-YOKE + Peddals; 17" Dell Monitor; WinXP home; FS2k2 pro

I can confirmed strange behaviours of rc3 in conjunction with A320PIC - regardless of the used FSUIPC version.All seems to work well - unless you have switched off to departure (after T/O), which results in "quietful agony" of Otto or misleading frequency changings to arrival instead of departure.Anyway, also manual frequency change leads to same bad experience.I think, this depends on the settings of Wilco's RPM and the use of FS ATC and RC voices.These problems seem to occur first, when you try to change the knobs, buttons and switches on the radio console, although you have two different radios.Sorry guys, no solution yet, but maybe a way of thinking about my suppose.Nice weekend to all of you... :-wave

I finally disabled "Contact Next Controller" in RC Key Options. This seems to have fixed RC with PICA320 as long as it is used on my FS2002 machine and not a networked computer with WideFS. So far RC on a Networked computer with WideFS still dysfunctions. I'll keep hacking at it.Randy Jura, KPDX