Open the Controller Info panel in RC and check if there is a weather briefing frequency entered.

 

Also, regarding use of ASN please read the pinned topic on ASX. The restrictions are probably similar. FSUIPC4 will detect if Active Sky is being used. If you request ATIS from RC it will deliver (via FSUIPC) the information from ASX's predictive arrival METAR, not the weather in force via FSX. This is per the request of users. This all has to do with the limitations of FSX's SimConnect when using the DWI interface for weather control. The FSUIPC4 AS detection has been in its versions for the last couple of years.

 

One of our beta testers recommended using Active Sky's Destination Weather Lock so weather would not be consistently changing during the last few miles of your center and approach phase due to enforcement of using the global weather mode. I assume the problem still exists with ASN since it is an FSX (not FS9) limitation.

 

RC does not examine ai patterns (if present) at more than 60 miles out and by the time you get to the airport traffic area they could be entirely different. In fact, RC looks twice as you approach - first when contacting approach and then again further in. This might result in a runway change BTW after your first assignment.

 

Finally predictive runway use by weather alone is extremely difficult.

 

The following quote regarding KDCA illustrates some of the complexity of how FSX assigns ai to runways:

 

"Runway 01/19 will always be the prefered takeoff/landing runway because

1. It is the longest runway
2. It has a ILS and a LDA approach code in the database
3. The runway is longer then 6500 ft
4. Runway 01 is the prefered landing runway with the highest score since it has the ILS approach code for clear weather landings
5. Runway 04/22 at less then 5000 ft when xwinded will only accept turbo props and smaller type aircraft


Some of the scoring in the XML compiled to bgl processed by the .dll looks like this


Score = 0
If runway length > 70% of longest runway at airport -> Score += 50
Score += tailwind or headwind (tailwind < 0 and headwind > 0)
If (unknown 'runway group' flag) Score += 10
Score = crosswind <<<<<<<<------------------------------------ add 100 points if my CW technique is in use
If (runway landing==yes) -> Score += 100
If (runway takeoff==yes) -> Score += 100

once the score is totaled then FS multiplies by 10000

Now we have to factor in that Jet Aircraft as per the .air file has additional scoring code. FS also looks at the Empty Weight value in the aircraft.cfg file

If no empty weights specified in the .cfg: returns 5000ft

Else:

value = ((empty_weight pounds - 10000) * 2000 / 90000 ) + 5000

if ( value > 7000 ) return 7000
if ( value < 5000 ) return 5000
else return value

Jets are most complicated based on EW vs runway length

Runway 01/19 = 6875 ft (FS9 stock)
Runway 04/22 = 4914 ft (FS9 stock)

Since the longest runway at KDCA is 01/19 then ATC will vector all Jets to use that runway. Runway 04/22 will be used if you crosswind but ATC will vector Turbo Props and smaller type aircraft to use that runway.

FS coded taxiways and runways with weight restriction code in the XML compiled to a bgl. However like many other parts of FS coding this weight restriction was not made available. The runway weight restriction code can be activated if the runways are parallel or made to think they are parallel with the Crosswind Runway Technique."

 

There were later developments in the runway scoring system adding more properties of the aircraft and runway, plus the weather environment. This is why RC looks at existing ai patterns giving those top priorities. This is also why for Active sky users it is recommended to use the destination weather lock for FSX so weather at destination is held consistent to stabilize any arriving ai during your arrival and not via the Global Weather Mode forced by Sim Connect forcing the weather at your changing aircraft location upon destination as you approach.

 

Now, if you are using destination weather lock, use the leave frequency for weather option (in your ASN guide check the destination weather lock range) if ATIS is not listed which is short range. Leave frequency to get weather is not available during approach. If the co-pilot has the comms, he supposed to get that for you.

 

If you use the ASN flight watch services they might conflict with RC's delivery. At least disable the ASN option to use a text box as it will overwrite RC's window.

aaahh i see, so this would explain when i asked for a wx brief RC gave me runway 24 i was way out more that 60 nm. As i neared and got handed over to app the runway changed to 06 the one i was expecting.

 

does that explain it?

 

well RC and ASN weather slightly matches. 

QNH remains the same

 

but the wind direction is different usually off about +- 5 degress but the speed is the same