Not quite sure what to make of this. This is my first experience with the product and occurred immediately after starting a new RC4 flight plan. I apologize if this issue has already surfaced. I am still perusing the forums to see if anyone else has experienced this.EDIT: I will answer my own silly question (maybe save someone else embarassment and shame)...Page 122 of the User Guide Wrote:Before you click Start on RC

Jase,That isn't the AdvDisp. It's the default FS banner that should be closed by right-clicking on it and choosing Close Window.Go to the menu and see if you have a tick against ADV display. You probably don't so if there's an entry present just select it and a small window will appear. Move it to a suitable position on your panel, right-click it and select Dock. Then right-click again and select Hide When Empty.That should get you up and running but for more info read the help file that came with AdvDisp.Cheers,

Yeah, I got it sorted out. The AdvDisp window came up blank and the garbled output showed up behind it in the FS banner. I just had to close the FS banner and restart RC, and all was well again.I am curious, however. If RC gleans its frequency info from FS, then how does it resolve conflicts with FS ATIS? When I tune weather through RC, I get piggybacked transmission of ATIS information - one from FS, one from RC. I'm sure this is easily solvable by choosing a phony ATIS freq. in the RC setup. Should FS ATC be disabled altogether when using RC?

Hi,ACT window checked Off and ATC sound, set to zero.Hope this helps,Jimhttp://www.hifisim.comhttp://sales.hifisim.com/pub-download/asv6...development.jpg http://sales.hifisim.com/pub-download/asv6-banner-proud.jpg

---

http://www.jdtllc.com/images/rcv4bannersupporter.jpg

Is RC4 "terrain-aware"? I received some unusual - somewhat circuitous - vectors that took me around a mountain range on approach. I wasn't certain if that was triggered by not making my descent altitude in time (losing 20,000 in < 30 miles was pretty aggressive for 767) or if RC perceived a possible incursion with terrain. Anyway, here's a snap shot of the approach path. The filed path was the JAMMN4 arrival into KSLC.

<>Yes. It stores (and shows) the Minimum Safe Altitude (MSA) in the Controller window after you load a flight plan. If you're flying into a mountainous area (such as SLC) you should check the NOTAMS box for KSLC. That tells RC to gives you descents that you can follow if safe to do so. What RC doesn't know is what direction the high ground is relative to the airport.Without seeing your flight plan it's impossible to judge your situation but try it again with NOTAMS checked and see what happens.Cheers,

Ah. So it understands an MSA floor, but isn't aware of specific elevation points - right?. So that leaves me a little puzzled. The attached picture shows the filed plan (in blue). The red line shows the vectors I received. I was coming down out of FL200 or so when I received instructions to turn left to 260, on a flight path that was orthogonal to my direction of flight. I assumed at the time that maybe I was being circled around while I bled off additional altitude, but surprised to find I was just being vectored around in a very wide pattern. I was surprised by how far west of the airport I was taken (even into restricted airspace). Eventually I got to where I needed to be, albeit in sort of a round-about way.I recall that RC 3 was sensitive to how near or far the last waypoint was to the landing field. Perhaps RC didn't like the location of those waypoints along that STAR for one reason or another.J

>>ACT window checked Off and ATC sound, set to zero.>This eliminated MS ATC chatter, but it didn't resolve the overlapping ATIS problem. RC chooses the same freq as the MS ATIS service, and both broadcast on the same freq. concurrently. The only way I've been able to circumvent this is to move the RC ATIS to a separate frequency or disable the Wx frequency and rely solely on MS ATIS (ick). A very minor inconvenience.

sounds like maybe you missed your crossing restrictionjd

are you sure atis isn't coming from your weather program? if you turn atc volume to 0, you shouldn't hear ms atisjd

Possibly. Like I said, I was given an expedited descent where I had to lose 20K in 30nm. I had the co-pilot auto-responding during that flight and lost the opportunity to declare "unable" (I distinctly recall wanting to smack the overly-accomodating guy in the right chair :). I know I wasn't down in 30nm. Part of me wonders if I was being vectored out of the pattern until I reached my target altitude. Is this possible?I flew the flight a second time (this time with auto-reply turned off) and this time a similar thing happened, only I was cleared down at P/D at which time I was vectored into a holding pattern (left to 260, then 170, then 080, and then 350 and proceed on course). J

This thought occurred to me as I am using FSMeteo 6.4. However, I don't recall seeing an option for ATIS - I thought this was an ASV thing (which I also have but was not using at the time). I can try dialing down the volume. A question about that though: is the MS ATC "chatter" at all meaningfull when RC is running? I got the impression that while RC could instruct AI aircraft, it wasn't in complete control of them either and that the MS ATC engine was still actively directing aircraft. If that is in fact true, wouldn't it make sense to still be able to hear the audio from the MS ATC engine (in addition to RC?) Or are MS ATC instructions meaningless in this context?Thanks,J

Options / Settings / Sound. Reduce Air Traffic Control to 0 but leave it checked. Reduces the chances of a ATC.DLL crash.If you can't hear the FS ATIS it shouldn't be a problem. That's worked for me for ages.Cheers,