Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Possible reason for my confusion

Featured Replies

Hello once again, I think I now know what led to the utter state of confusion for me. It seems to be centered on one main idea: If on the documentation it was stated that once you get the message RCv22 IS READY then simply hit CSI. Now you will see the following: Chatter On/Off Hold On/Off Traffic On/Off Your Coms Now if you hit CSI again you'll be presented with Pilot Request again. Then hit CSN and one of the following three items, usually the second, will be displayed: Com Nav (the first waypoint info is shown by default) RWY You can toggle between these two categories by repeatably hitting CSI again. CSI acts as a simple toggle between the two categories. Now you can go up or down in the paticular category by hitting CSU or CSN to go up or down. This is very simple and certainly makes sense. From this point forward the process is very simple and essentially intuitive The major point I am making is that, for a newuser, getting to this understanding is, in my case, very frustrating. Without belaboring this point I wonder why the above statements could not have been placed on the same page of the same document. I have yet to find that documentation. All this information is in the documentation package but it is certainly spread out and difficult to integrate into a newuser's mind. As I said the method is simple and makes good sense. I guess, and actually know from personal experience, that it is very difficult for a person who develops a program to actually write clearly such that someone who is just being introduced to the program can understand it. If you don't believe this is true then simply try to do both.Should be straight forward from now on.Blais

  • Commercial Member

not to belabor the point :-) it's covered in the tutorials, which seems like an appropriate place for it :-)

Hi, Yes I did mentioned that but the point I was trying to make is that the information was not readily digestable due to it being broken up and spread out over several documents. In other words John, document management.Good eveningBlais

While my frustration never reached the levels that you seem to have experienced, I must agree with you that the documentation of RC2.2 is poorly organized for such a fine product. Radar Contact may be a complex piece of software, but it really isn't a very complex program to use. Nevertheless, for days I couldn't help thinking that I had made a mistake by buying RC2.2, simply because the documentation left me utterly confused again and again.I think the problem with the documentation is that you constantly run into hyperlinks pointing to pages that you need to visit now to understand the rest of the page that you're already on. But when you get there, you run into other hyperlinks, dragging you even further away from what you were trying to figure out. Eventually, you will often find yourself back were you started, only now you're even more confused :-)Unless RC3 comes with a nicely formatted PDF document explaining everything in the proper sequence, I won't buy it. I'm serious now! ;-)

  • Commercial Member

careful, i can put you in charge of documentation!maybe you can tell me how it should be organized....i'm all ears!

Hi, I look at it this way. I hung in there, with a lot of good help, and ended up really enjoying the use of it.I suspect John and the JD group will do their best but, no doubt, we will buy it anyway.Peace

>careful, i can put you in charge of documentation! (Gasp!) :-outta>maybe you can tell me how it should be organized.... Actually, I do write techdocs and end user documentation for a living, among other things.If you provide the basic documentation, and of course a copy of RC3, I'll happily spend a few weekends trying to make a good manual out of it. And it would only cost you a lifetime license to all future versions of Radar Contact. :-)My knowledge of the ATC world is limited, but that could actually prove an advantage. English is not my native language, but you could always do the final polishing yourselves.Contact me via email if you're interested.

Henrik, I've seen all the docs from the first Version of RC to the present and can agree they are hard to write. I've struggled with simple docs for a scenery upload. :-) I've proof read all of RC's docs and add my 2 cents when possible but like many of us, don't have the skills to organize it all, especially for the new comer. Version 3 is much friendlier to use and more intuitive than Ver 2.2 Looking forward to your thoughts on it.Best, Rob[table border=2 bgcolor=#eeeeee][tr][td]http://avsim.com/flightdeck/images/Radar_small.gif[/td][td]Beta tester for http://www.jdtllc.com' target="_blank">Radar Contact] the premier ATC adventure add-on for FS

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.