I'm new to RC and really like it. Compared to VATSIM the pace is so much more realistic, at least most of the time.

 

There is something I've noticed concerning ATIS and have a question. I've found that on both arrival as well as departure the actual runway I'm assigned is different than what ATIS is giving. Also, it seems the same thing is happening with Clearance Delivery. I listen to ATIS, then set up my DP for runway X, or inbound set up my nav / ILS for whatever ATIS gives and then the controller assigns something different? I'm using ASE and it has ample time to fully integrate with FS before I use RC. Is this normal, any thoughts or suggestions? Thank you.

 

Sent from my iPad using Tapatalk HD

Hi chuck

 

try it with the beta fsuipc 4.812d

 

http://forum.simflig...pic/71226-fsui/

 

peter

Thanks for the quick reply. I downloaded the file which is FSUIPC4.dll and asked Pete D. a question on his forum. He says that FSUIPC isn't involved as far as FS9 and ASE/RC is concerned. He did indicate that DWC in ActiveSky Evolution may not have to be enabled. I'll try it with DWC disabled and see if that helps.

Thanks for the quick reply. I downloaded the file which is FSUIPC4.dll and asked Pete D. a question on his forum. He says that FSUIPC isn't involved as far as FS9 and ASE/RC is concerned. He did indicate that DWC in ActiveSky Evolution may not have to be enabled. I'll try it with DWC disabled and see if that helps.

 

I frequently have had the same thing happen -- RC assigns a different RW than stated by ATIS, and I do not use ASE. So, its not ASE's fault.

 

Alan

RC's first priority in assigning a runway at approach time is to observe an active ai behavior. At ATIS time if you are far enough out ai may not be rendered yet so RC predicts a runway according to weather and runway properties. ai follow a different sort of best runway scoring as interpreted by long time ai behavior observers that depend on aircraft type, anticipated degree of tailwind and crosswind components allowance, navaid availability, and other devices.

 

I'm taking FS9 here. ASE was only released for FSX, correct? So which are we talking about. FSX weather smoothing and the required use of DWC in ASE in FSX does not apply for AS with FS9. (This issue is for FSX users.) This does not apply to Alan.

 

Also, for FSX users that use Ultimate Traffic II, be sure you have it set to render ai at the maximum distance.

As you know, ASE is used in FSX and also FS9. It's AS 2012 that's exclusively FSX. I now see its a RC situation. What I've ended up doing is NOT entering the departure runway and DP until AFTER getting taxi clearance. I do the same for arrivals. A little strange, but it saves a headache. :-)

Check then the ASE FS9 settings. If global weather mode is on automatic disable it. Same with DWC. Then independently set your wind smoothing options (change, etc.) in the weather options tab of FSUIPC. That method was also used to change the rapid wind shifts during AS real world weather updates or when crossing reporting stations in ASE.

 

RC4 assigns the runway for departure and arrival based on ai runway use as top priority to avoid conflicts with ai. ATIS is based only on predictive weather analysis. RC3 just used weather and was frequently in conflict so ai monitoring was added in RC4.

 

In the original ASE manual there was a section devoted early on where in FS9 you could set this up in ASE.

 

I use AS65 and do not have this problem to my recollection.

 

For departure before reading ATIS if ASE has the function Refresh AI, use this after the initial weather is processed (process the plan file first in ASE) and then when it says processing finished do the AI refresh in AES and wait one minute. That immediately updates ATIS and restarts ai take-offs and arrivals for the weather written by AS.AES. It supposed to be automatic but I found I got better results by issuing the ai refresh command command manually.

Thanks everyone, Ronzie. I'll give the settings a try and report back. :Straight Face:

Hi Chuck,

 

I have used AS products for many years and following some advice many years ago from Ronzie,I use a method which eliminates most problems.

 

I start the weather program,noting the departure and arrival weather, and then FS,putting the aircraft to the departure gate.I finish my aircraft checks and FMC workby which time the weather will have had one refresh.(Set to 15mins)

I then start RC,allowing things to settle I call up ATIS via the RC menu.It is always correct when I compare it to the weather noted earlier.

 

I fly on to the descent and wait until i am within 70 miles of my arrival airport when I refresh the weather and AI traffic.At 50nm to go I listen to arrival weather and find that except for some minor changes it is in accordance with the weather noted earlier.I complete my flight.

 

My usual flights last up to 3hrs but even flying the odd long haul I use similar methods.

Thanks guys. The suggestions work. But I've discovered a new situation as noted in another thread. :Phbbbt: