Cam,RC only works through Comm 1. The thing you can try is to add the default Comm 1 radio. Using the manual to install the Comm 2 and Audio Panel, instead of putting in 737-400!Comm 2, use 737-400!Comm 1, as in the following.//--------------------------------------------[Window01]Background_color=120,120,120 size_mm=178,112position=8visible=0ident=RADIO_STACK_PANELgauge00=737-400!Comm 1, 0,0,178,74gauge01=737-400!Audio, 0,75,178,36//--------------------------------------------and add the window to the [Window Titles] list at the top of panel.cfg:[Window Titles]Window00=Main PanelWindow01=Comm 1 and Audio panel <----add this lineThen press Shift-2 to open and close the new window.See if clicking the audio panel "BTH" off, and making Comm2 active (for FSATC) works. Then Comm1 is free for RC, and with the default radio you should be able to have Otto work the radio for you and hear it. It won't nevessarily change the PIC's comm1, but as long as you have a radio that's working, it doesn't matter.

well Scott ive come to the conclusion that radar control thru atc does not work properly , it has to be the modeling of the plane in that area, i have done all you said to do, tried other planes and they work fine , its just with this plane that i have the problem , until wilco comes out with a fix , i will have to just go back to pss 747.thanks....Camtech

The other problem that RC has is with "managed" climbs and descents. Quite often, as I am descending, the aircraft will pitch up and down to hold airspeed. Down is not a problem in this case, however, when the nose pitches up and the V/S momentarily rises to -300 or so, RC misinterprets this action as failure to descend and prematurely flames you for not descending to the assigned altitude. VS mode seems to be the only reliable means of addressing this problem.

Yo Scott,there is this modern technic that AntiCyclone uses a interactive VC where all the PIC-A320 gauges are and they work interactive but with each his own programming, not FS2k2 default. Of course not default - FS2k2 doesnt handle normal gauges in the VC. The PIC-A320 gauges communicates bypassing by some *.dll and (pic-a320).ini, which compute the input and give this to fs2k2 where it gets handled like info from 'normal' gauge output. This communication way of the PIC-A320 works this way as well with the yoke/joystick data. So, I guess not even adding default gauges into a non existing normal panel in the panel.cfg would work. It'll gets bypassed. I already tried that befor the update.AntiCyclone already told us that they did take a look into the programming code and couldnt find any error or cause why RC cannot work with PIC-A320. Well, they dont know how RC works and interacts with FS2k2. I know deep in my heart that there is/will be a solution! Just you two parties should work together and check out both programming codings. The VC-Radio gauge may be programmed with default code but FS2k2 doesnt know about that. FS2k2 gets the gauge data not from a default known gauge out of the panel but outside bypassed. FS2k2 gets the data, but RC probably tries to get the data through default or alike gauge data and cannot see any interactive gauges in VC or data flow bypassing the normal data flow. It has to be related to how they got the VC working interactive...CheersTorben

no magic, nothing special on my endi read the com1 frequency via fsuipc, at offset 34Ei write the com1 frequency via fsuipc, at offset 34Eworks on every other plane, that i know of....

...and now the magic question: How does the PIC-A320 do it??? If not the same way by fsuipc, there is the way to go, isnt it?Cheers

Torben,The PIC A320 radio may write to the comm 1/comm 2 variables, but may not read from them - and that would be a problem. There is nothing RC can do about that. I would imagine if this is true, any add-on radio system or external control won't work. And that's an AntiCyclone problem easily solved by them.I'm learning towards this direction because of the linked comm 1 and comm 2 and not being able to control from the default audio panel or set from default radios (if what the others have reported is true).

Hi Scott,>Torben,>>The PIC A320 radio may write to the comm 1/comm 2 variables,>but may not read from them - and that would be a problem. I just have a heavy guess that there is the problem.>There is nothing RC can do about that. I would imagine if>this is true, any add-on radio system or external control>won't work. And that's an AntiCyclone problem easily solved>by them.So I wonder why they havent yet found this problem spot in the code, maybe they never had a closer look?>I'm learning towards this direction because of the linked comm>1 and comm 2 and not being able to control from the default>audio panel or set from default radios (if what the others>have reported is true).I realy beleave that all that is true. So many customer of both cannot be wrong what they experience, right?So, I shell set a link to this forum discussion in the Wilco Forum... I dont fly the PIC-A320 just because I cannot fly as it should be and is with all other airplanes with ATC by RC301. I am about to go for a refund from WilcoPub...CheersTorben

Hi Scott,I'm co-developer of this add-on that seems to cause issue with your excellent program. We do not use the FS default radio management since we have clickable events. That's the reason why we programmed our own module.Any chance to get a time limited RC3 in order to try to fix the issue ? [email protected] edit : I have never flown online x(Best regards,

maybe we can trade. a plane for radar contact? :-)send me your snail mail address to [email protected] here is the rock bottom line. i use fsuipc to read/set the com frequencyif you have access to the fsuipc documentation, you can look up the offset 34Ewhen the rc co-pilot is handling the comms, i write to the 34e offset, per the fsuipc specs for that offset.if you could monitor that offset, and set your comms to the frequency in that offset, we're done.jd

Hi,Well it works fine for me. I use fs2002 atc on comm2 for progressive taxi then I cut it for the rest of the flight. When I press shift+1 etc to switch freq. in rc3 the comm1 tunes itself without a problem. I just have to do it manually for the approach freq. or the arrival ATIS, but usually I use activesky voice ATIS on comm2. Sometimes I cannot get fs2002 atc back after landing but well..I choose the nicest gate to park and taxi there :-) Also make sure your rc3 keys don't conflict with a320PIC.I didn't have the problem with the tower not responding or the departure ATIS not playing.Ok time to go try to fly a decent approach in my new a320 hehehePS: I didn't try Otto yet, usually I don't use it though...

thats the problem , otto not handling the comm, and myself i hardly never use 2002 atc, i use radar contact thru the entire flight and flying airbus320 i need help with the comm. and there are times even manually it will not responed, all other planes work fine other than wilcos airbus.Camtech

Howde JD,how are you doing buddy?I'd love to read something new about what you and AntiCyClone are communicate and do about the radio problem that Otto cannot handle the PIC-A320 radio and even manualy it doesnt work right to contact tower, departure etc.I guess by now AntiCyClone should recieved tje RC3 CD and had some time to play around with it...Cheers and have a good day.

he knows what he needs to do