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.

Finding RC a little buggy lately.

Featured Replies

The last couple of days, I've went through a couple of problems with RC.1) I was standing by at a runway, and I was instructed to taxi onto the runway and hold. So I did. A plane was landing at the other end of the strip and proceeded to go right towards me and hit me. So Why did RC give me the clear to go onto runway?2) Just a moment ago, I was filing my IFR flight from Saskatoon to Regina. I was told to climb and maintain 1000ft. Saskatoon is about 1600ft ASL. Just to experiment, I continued on to see what would happen later. After takeoff, I climbed to about 5000ft and and contacted departure. They were giving me hell for not flying my assigned altitude of 1000ft. What is the problem with RC?

Dear Buggy,I've never had that problem, but RC really doesn/t "know" where all of the Add-on planes are. (Sometimes the program is right on the money, sometimes not.)Second question: Your were most likely told to "climb and maintain Flight-level one zero". That's 10,000 ft!Last time I checked.

  • Commercial Member

1) this is fixed in v42) what is your transition altitude set for, on departure and arrival? exactly, what is in the boxes? 10 is going to be 1000ft, 100 is 10000ft, 10000 is going to be 1000000ftjd

Just for precision sake: flight level one-zero is 1000ft (probably never used, 'cause is surely lower than any transition altitude in any part of the world). 10000ft is flight level one-zero-zero (surely used very much in Europe, where TA is normally below 10000ft).

Regarding 1), it looks like you were also at the wrong end of the runway based on the AI pattern. Until version 4 is released, make sure you reload the AI if you are using any external weather program after it updates weather so the AI pattern and ATIS (FS9) reestablishes according to the new weather. Refresh AI is already a topic on this forum.

No. The ATC said "Fly and maintain one thousand"I am well aware of the Flight level terminology.

It was set at 180, (18000ft)There was a bug in the flight plan. I deleted the flight plan and started a new one. The problem never came back. So I don't know what had happened to the original plan. Oh well.

Thanks for trying to help.But I was at the right end of the runway. I never get those wrong.JD said that the problem will be fixed on V4.0.

Just to clarify, I did not mean that you misinterpreted ATC in going to the runway. There has been a problem where if using external weather apps such as AS2004.5, the FS ATIS and established AI do not update to the new current weather. RC seems to update correctly. The result is RC and FS would be out of synch for about fifteen minutes due to the AI delay in getting out of the established old pattern.When you stated you were on the runway with aircraft landing toward you, it looks like that was the case. FS and RC for the moment were disagreeing.The AI refresh is a work-around to insure that all programs are in synch for the new weather pattern.The feature that jd is referring to is that V4 will look at AI trends if active AI are present at departure and destination so it synchs with FS on a takeoff or approach merge. That is great where ambiguity exists. In addition, it should follow any AFCAD runway privileges imposed based on the AI flow.It will not fix the problem of AI using the wrong runways for new weather conditions established during all phases of flight origination. In other words, you do not want to have AI and yourself taking off downwind too much.I had recommended to the AS2004.5 folks that they issue a traffic refresh command at the end of their weather refresh process which should occur when a flight is loaded. This command is available within FSUIPC and if a user has the fully registered version a key assignment can be set to toggle AI off and then back on after the weather update is complete. The AI traffic will now follow the new weather influences and FS9 ATIS will now be correct.In summary, I was not implying that you had made any errors.

>>1) I was standing by at a runway, and I was instructed to taxi>onto the runway and hold. So I did. A plane was landing at>the other end of the strip and proceeded to go right towards>me and hit me. So Why did RC give me the clear to go onto>runway?> I see that often. For some reason MS ATC often don't seem to bother about the direction of the wind. E.g. having a situation with an easterly wind, you would expect to take of from e.g. rwy. 9, but MS ATC happily sends everyone to rwy 27. RC will send you to the correct rwy, but in these situations you'll face a problem. I always check where the AI planes takes off from before accepting the runway i get from RC.CheersLars

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.