A strange thing happened on my latest flight.I was enroute from DFW to EWR in the PIC767, using RCV3. Everything was working flawlessly insofar as my own flightplan and interactions with ATC were concerned.I was at FL 370, in Memphis Center airspace. In the RC "options" menu, I had selected the Chatter slider to number 4. I was hearing chatter about once every 60 seconds or so.Suddenly, the chatter playback function seemed to get stuck in an endless loop. It started playing the first 3 seconds of EVERY wave file one right after another... dozens of different aircraft. I let this go on for about 2 minutes, and it showed no sign of stopping.I run RCV3 on a second computer, so I opened up the options menu and set chatter to "off", which stopped the runaway playback. Later, I set the slider back to "4", and everything worked fine from that point on.The only thing I noted that might have contributed to this problem happened about a minute before... a chatter wave file had just started playing as I passed a waypoint. The "ding" sound effect stopped the chatter in mid sentence. The endless loop began when the next chatter wave started.One other minor glitch - during descent on the DYLIN2 STAR to EWR, the Washington Center controller gave me a PD clearance to descend and maintain 17000 feet (from FL 230). After the descent clearance, he started to give the upcoming crossing restriction, but only got out the word "expect" and then said nothing further... he just stopped speaking. The rest of the approach sequence later on went fine - it was just that one clearance that seemed to get cut short. This one was NOT interrupted by a waypoint chime.Jim BarrettUPS417

Wow! I thought it must have been something I did, because on a flight from KLGA to KBWI I had the exact same problem with the chatter. It played the first bit of every wave file in rapid succesion for about 2 minutes before everything went back to normal. I was using the DF734.Max

happend here to, twice in five flights. I assumed that somehow the chatter just got 'clogged' and finally flushed itself so to speak. At a freq change it cleared up and continued the flight.

Hi Guys,That same problem happen through test, but we just kind of let it go. Now that chatter and controller wav's have been a point of our concern, it may now be related to the issue on slow controller wav's. First what OS do each of you use, please post.I am on a Windows XP Pro system and since I use the post that JD has given everyone on making RC the top priority, I did not have this same occurance.I also fly with the PIC 767, so it is not related to that plane, but a RC wav going through rapid play. However since I did the priority change in XP that did not happen on my flight today from KSFO to KEWR.Lets hear what your results are.CheersBob Johnson

>Hi Guys, >>That same problem happen through test, but we just kind of >let it go. Now that chatter and controller wav's have been >a point of our concern, it may now be related to the issue >on slow controller wav's. >>First what OS do each of you use, please post. >>I run RCV3 (and FSMeteo 5.1) on a second computer, using WideFS. That machine is running Windows 2000 Pro.Haven't tried making RC high priority on the aux computer since it's dedicated just to RC.The main FS2K computer is running Win 98 SEJim Barrett

That's really strange. Out of the hundreds of flights I've made with V3, I've not had this until now. It was just as I contacted Cleveland Center, I had all the atc3 wavs play. I think the clock jumped to Eastern Time.(additional)I'm flying West to East, and I've set the RC priority to Real-Time for wav play testing.

Just out of curiosity, does anyone else experiencing this NOT have "Keep FS clock synced to Real Time" checked in FSUIPC?

>Just out of curiosity, does anyone else experiencing this >NOT have "Keep FS clock synced to Real Time" checked in >FSUIPC? I DO have the clock sync enabled. I'd have to look at a map to confirm, but I believe that I might very well have been crossing the boundary between Central and Eastern time when the glitch happened. I know that I was in the vicinity of Nashville at the time, headed eastbound.Jim Barrett

I am using WIN XP Pro and I cannot remember the exact point where this occured but I thought it was hilarious because I was also monitoring Fsatc NY center so you can imagine the commotion on the radio. :-eek