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.

RC3, active takeoff runway, and traffic vectors questio

Featured Replies

Greetings.Having owned now the last 3 releases of RC I can only say things get better each time. I am, however, just curious if I'm doing something strange or if I'm mis-interpreting what's happening.First, taking off KBOS I'm getting assigned 22L for takeoff. Which is fine, but the AI traffic is taking off from 33L instead and taxis via C to get there.. right accross my takeoff roll! Thankfully I was lookin out and managed to lift off early. Winds at the time were 230/13 and the MS ATIS and RC ATIS agree with the weather from FS_Meteo...I'm at FL350. I'm heading 270deg, on course. I get a traffic call for a Gulfstream 10:00 crossing right to left FL370. Then I get an instruction to turn 250 for traffic... Now, if the target is crossing right to left, and it's a left turn to get to 250 deg from 270 deg, am I not being turned *into* the same direction as the traffic will be heading? Shouldn't I be vectored 290 to go behind it, if manuvering is needed at all? Isn't 2K/opposite headings enough clearance to not manuver? Thanks in advance!P

P2K2 is notorious for using bogus runways. I don't know what they were thinking. If you want to see this in extreme action, go to KDEN. They dont use one correct runway.As for vectors for traffic, the controller knows what the traffic and you are doing. So he/she gives you a vector based on that. He doesn't have time to explain it.

>Greetings. >>Having owned now the last 3 releases of RC I can only say >things get better each time. I am, however, just curious if >I'm doing something strange or if I'm mis-interpreting >what's happening. >>First, taking off KBOS I'm getting assigned 22L for takeoff. > Which is fine, but the AI traffic is taking off from 33L >instead and taxis via C to get there.. right accross my >takeoff roll! Thankfully I was lookin out and managed to >lift off early. Winds at the time were 230/13 and the MS >ATIS and RC ATIS agree with the weather from FS_Meteo... MS ATC uses a runway of it choice, RC uses the runway most aligned with the wind. You can always chose to use the one that MS is using by choosing that in the menu.>>I'm at FL350. I'm heading 270deg, on course. I get a >traffic call for a Gulfstream 10:00 crossing right to left >FL370. Then I get an instruction to turn 250 for traffic... > Now, if the target is crossing right to left, and it's a >left turn to get to 250 deg from 270 deg, am I not being >turned *into* the same direction as the traffic will be >heading? Not sure if if you mean that the traffic was at your 10:00 crossing from left to right or not. But if it was left to right then it is correct to turn you to the left to pass behind it. If you got the call that traffic was crossing right to left from your 10:00, you would not need to would not need to move as the traffic would pass on your left side and not be a factor.Hope this helps!

man you are quick!!!!! hehehehe

  • Author

Greetings,The call was "traffic, 10:00, passing left to right". The traffic was 2000' above me. I then immediately get a 20 degree turn to the right vector, which if the traffic was at my 10:00 and moving right, puts me right into the same way it is going, right?I don't mind vectors, and I know the controllers know what they're doing, I guess I'm just trying to figure out if *this* controller knows what it's doing ;)P

  • Commercial Member

since i don't vector for traffic, two things happened here, nearly simultaneouslyyou had ai traffic, which warranted a traffic call which you got. a random traffic occured for a fictitious plane you never saw, and rc gave you a vector.bet you never see it again LOL

Hi Peter,You raise a very good point and question. Let me give you my own perspective about these two problems.First lets talk about airport situations with AI traffic. Many of the traffic situations are at fault due to bad AFCAD plans being loaded. For example, Scott mentioned KDEN where we both live and fly our MSFS flights. At Denver, you don't make a takeoff from runway 16 unless there are MAJOR repairs to the other north/south runways. Runway 16 for takeoff is miles of taxing from the gates. Using the default AFCAD for KDEN one would get runway 16, however a scenery designer for KDEN made the AFACAD for Denver with all the right real world runways for both takeoff and landing. You cannot believe what a difference that has made.Second on the subject of enroute traffic vectors, RC was designed for all MSFS versions. Prior to FS2002 there was NO inter-active traffic. Using the RC traffic vectors was an importnat function. However with FS2002 with "real-time" AI traffic, you really don't need to have random vectors. For me I have the RC vectors set to "ZERO", don't need to have random vectors when there is real planes flying all around me. I use comm 2 which is FSATC to "monitor" who is around me in the FS world and then I fly with the appropriate seperations.Lots of fun with all this new stuff (grin))Bob Johnson

 

Runway 16 is a walk in the park compared to the 6 1/2 miles of taxiing to runway 35R. They'e kidding, right? ;-)

Hey Scott,I have a "beta" example of the new runway at KDEN. You are so correct wait till anyone attempts to take off from the new 15,000 foot runway from the north. One needs to pack a lunch just for the taxi time (ha ha)Bob J

 

Bob,I still remember that 22-minute taxi to 17L at Stapleton, and 35R at DIA (which is still slightly further than 16R will be) is even futher than that! ;-)

>First, taking off KBOS I'm getting assigned 22L for takeoff. > Which is fine, but the AI traffic is taking off from 33L >instead and taxis via C to get there.. right accross my >takeoff roll!Unfortunately RC and fsatc use different criteria for choosing the active runway. Usually what I'll do is listen to both the RC atis and the fsatc atis so I'll know if there's going to be a conflict. If two different runways are in use and they're both suitable, I'll request from RC whatever runway fsatc is using. If the fsatc runway is unsuitable, I'll use the runway I was assigned by RC. Since I'm listening to fsatc on com2, I can hear when an ai aircraft is cleared to takeoff...I'll just wait until there's no crossing traffic and take off.Sidney Schwartz [KPDX]Horizon Pilot--flight plans and scenery for FS2002http://sidneyschwartz.homestead.com/index.htmlhttp://jdtllc.com/images/RCsupporter.jpg

Have you checked the FSUIPC setting to correct the AI traffic by real weather? And have you set all variables of FSMeteo right? Then FSUIPC tells FS2k2 the right runway to take and it should use same as RC chooses. There is this AI Traffic Project which sets all airports with the right aircrafts and flightplans and routes. These AI files are the best I ever experienced and since I installed them I cant remember seeing wrong AI traffic takeoff pattern.Do I make any sense?

Regards, Torben Hadler

 

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.