To all,

Looking for solution / ideas ..........

 

The Setup > Win7-64, FSX, AS2012, FSUIPC and WideFS payware, RCV4. AS2012 connecting from laptop via Simconnect and RCV4 connecting from

laptop via WideFS. Also running latest version of FS Flightkeeper via WideFS (from laptop), and Flight Sim Commander (on the PC).

 

The Issue > Winds reported by RCV4 ATIS prior to getting clearance are never in synch with winds reported by AS2012. At some point thereafter, near to

beginning of any flight the RCV4 / AS2012 weather always synchronizes nicely and stays that way throughout the remainder of the session. Wx is

always in synch at destination

 

The Resulting problems > After planning / selecting / requesting my departure runway based on winds reported by AS2012, I frequently find myself

facing aircraft taking off from the opposite end of runway. Of course I could always go with the ATIS, but that would frequently require last minute

runway / DP alterations to my flight plan (not a huge deal > just a [frequent] nuisance).

 

Also presenting this to the HiFi forum for any tips they may be able to offer.

Best to all,

Ken Boardman

Make sure you refresh the AS2012 AI after its weather writes are complete. When you load an FS flight the weather is what is in the default and the ai start moving based on this before AS 2012 has set the weather. After the last weather write update (frefresh the AI) to reset the ai flow and wait a couple of minutes. If AS2012 does not offer a refresh ai button then just advance the FS time by one minute and ai should reload. This refresh also updates the ATIS RC will read to you.

 

Arrival ATIS is read from the AS2012 METAR due to the mandatory use of Global Weather mode when using DWC for FSX. In that mode worldwide weather is the same as where your aircraft is at the moment which creates a problem with the destination weather forecast when RC looks at the ai at about 40 nm out. Our beta testers that have this environment recommend using the AS destination weather lock for FSX. This keeps the weather constant at what approach saw when you were 40 nm out.

 

As far as dynamically usingg a SID or STAR, just put the common waypoints for each runway in the .pln sent to RC. Pick them by departure or arrival direction. Then use for departure one of the altitude restriction options which lets you navigate on your own within 30 nm of departure. For arrival use an IAP which after accepting the first vector just request an IAP to the runway selected by RC.

 

These dynamics work best by using archived weather for the universal (Z) time and date of your flight and has the advantage of setting the weather environment for time of day based on your FS, not real world system time. If you depart at 1200Z then you'll be downloading the weather for that time and location so solar effects can be recognized instead of dealing with time zone differences.

Many thanks for the detailed explanations Ron. It all makes sense and I look forward to next flight. I'll follow up with you here after.....

Best regards,

Ken

Hi Ron,

Tested 3 times successfully, shutting down and rebooting between tests (overkill perhaps) by Refreshing AI with FSX unpaused. When I'm in the

flight preparation stage I like to do some of the stuff with FSX paused; however using AS2012 to Refresh the AI doesn't appear to work at all

with FSX paused so I've added "Unpause FSX" just before "Refresh AI" on my flight prep checklist ~ So this one is likely solved.

Thank you again for your instruction and helpful tips.

Best regards,

Ken

AS can not control FS if it is paused. Same with RC. Commands can go missed.