The last couple of flights that I've done have gone a little bit like this:  "Expect vectors to runway 9L" I go through the trouble of setting up the  ILS to land at 9L. Just as I get finished, it says "Expect vectors to runway 22R." Every time I've flown the last couple of times it's like Radar Contact can't make up its mind where it wants me to land. I've also run into the issue of being cleared to land and within feet of the runway told to "Go around." It can be quite frustrating. Is there anything I can do to make Radar Contact less... confused?

I had the same thing happen to me today. Without more info it's difficult to nail what is going on but my guess is that light and variable winds at the destination are probably involved.

 

RC may initially look at the arrival weather and based purely on that decide a particular runway is best. It does tend to favour longer runways and those with an ILS.

 

But as you get closer then the runway used by Ai will probably take precedence. Hence it changing its mind.

 

As for the go-around was there an aircraft on the landing runway? That would explain that. Or maybe an aircraft crossing the active was 'frozen' by RC. Unusual but it can happen. If neither of those two scenarios was the case it would require a log to resolve it but you have to choose that when starting RC.

Well, that's not what I'm talking about what happened in both situations was expect vectors to runway a, expect vectors to runway b (I had paused the flight sim both times to enter in all the stuff) So literally it was within seconds of flight sim time. As for the second I'm unsure, I didn't see anything but it's not like I was paying as close attention as I should have.

What you described happens once you're inside 40 miles from destination and have been instructed to contact Approach. That is the only place where RC decides which runway you will be allocated.

 

The two instructions will probably come very close. That's just how RC works in some situations.

 

If you can reproduce the situation and want a definitive answer then please follow the instructions pinned to the forum on how to make a log and send it to JD. You may want to keep the flight short because the log can get very large.

If initially when you contacted approach no ai were present RC picked the best runway based on runway properties and whether. RC looks a second time further in and if ai show up or change pattern or weather changes RC may reassign your runway for best fit.

 

If you are using one of the Active Sky FSX products see the pinned topic. To get around the Global Weather limitations ignore RC's ATIS (it comes from Active Sky's METAR) and choose the Destination Weather Lock option in Active Sky. This will hold weather steady as you go through approach and thereby ai patterns should be stable.

 

For more ai protection for you try feware ai smooth version 1.2 from the FSX Utilities section here on AVSIM. It also works in FS9. Enable Respond to User Aircraft and disable ATC Messages and ATC voice options in the AI Smooth setup. You can also increase separation time of close arriving aircraft to allow interleaving of departing traffic with arrivals to reduce take-off queues and reduce runway congestion.

Hi guys;

 

I'm having this "problem" too, but it does not bother me that much. But taking advantage of this topic is open, let me relate what I've been watching. 

 

First of all, I must say I use Opus Weather. And these changes of runways are quite frequent for me, both on takeoff and on approach. 

 

Let's take the example of a flight I made a few months ago, from VIDP. The control guided me for takeoff on runway 29, as seen in this passage:

 

 

Once reaching on runway 29, the takeoff was cleared. Note that when turning on the TCAS, there is another aircraft approaching in the opposite direction:

 

 

Shortly after takeoff, note that the TCAS alarm sounding:

 

 

So I'm trying to find a solution for this. I do not believe the problem is in RC, quite the contrary. To my understanding, the weather addon is leaving the RC "clueless". 

 

I may have to disable updates earlier in the approach. But there is still the change in takeoff.

 

And just for the record, it takes me around half an hour between starting the simulator/weather/RC,  do all the procedures for loading baggage / passenger; only then to ask for permission to takeoff.

 

But anyway, I say again: I'm not complaining about it, I'm just trying to bring to you what I've been experiencing, to see if we come to a common denominator. 

 

Forgive me for my English, Google Translate does not always do the job.

I took a brief look at the FAQ heading subjects in the weather section:

http://www.opussoftware.co.uk/opusfsi/faq.htm

 

Check out weather erratic behavior and other pertinent issues.

 

I recommend you have a default FSX flight setup with a default flight using the clear weather theme as well as any flights you have saved and are going to load. FSX dynamic weather should be off letting Opus handle everything. Let Opus setup FSUIPC as it needs and FSUIPC weather settings should be default.

Hi Ron;

 

thanks for your reply. I will have to check my FSUIPC settings. My default flight is "the default" (trike at Friday Harbor). About the FSX weather options, I always set the last option "user..." (I'm not in front of the PC right now, I can't remember correctly) but it's the last one, and then I run Opus. And dynamic weather is always off. Maybe I have to choose "Clear Skies" as you sad. 

 

Well, my wife will kill me tonight, but I will need to do some tests....

 

Thank you once again.

Guys;

 

just to add, I found this here (http://www.opussoftware.co.uk/opusfsi/opusfsx_getting_started2.htm)

 

 

 

"Set your FSX Current Weather to any weather theme, just don't enable the real world weather options unless you are using AI aircraft.

 

If you are using AI aircraft then select RW Weather in the FSX Weather settings, update the FSX weather and ensure at least the correct wind has been injected. This requires that your point of departure is a met station and has a valid METAR in the Jeppesen database. This procedure will set the wind BEFORE the flight is even loaded. Now you can take your time, process your flight plan, specify your intended destination and cruise altitude and finally instruct Opus to generate and load the weather. The Opus LWE will automatically put the sim back into custom weather mode. Using this simple procedure will always ensure your AI traffic start out using the correct runway."

 

 

 

I will visit the Opus Forum. Any news, I report back.

The last couple of flights that I've done have gone a little bit like this:  "Expect vectors to runway 9L" I go through the trouble of setting up the  ILS to land at 9L. Just as I get finished, it says "Expect vectors to runway 22R." Every time I've flown the last couple of times it's like Radar Contact can't make up its mind where it wants me to land. I've also run into the issue of being cleared to land and within feet of the runway told to "Go around." It can be quite frustrating. Is there anything I can do to make Radar Contact less... confused?

Regarding the go-around, you'll be told to do this if your gear is not down but as you are executing the go around the controller will tell you this.

 

Iain Smith

Regarding the go-around, you'll be told to do this if your gear is not down but as you are executing the go around the controller will tell you this.

 

Iain Smith

That certainly makes sense. I haven't flown in ages and if memory serves on that flight I forgot to lower the gear.

In FSX you can force a weather and ai refresh by advancing the FS time one minute after OPUS finishes its update. This also applies to FS9 but if you have a user paid registration you can set a hot-key to toggle ai off (0%) and on (your percent choice). This advances the departure ATIS update faster, at least for Active Sky, which has an AI Refresh button.

For variable pitch prop planes the word "GUMPF" is used as a reminder:

 

(G)as  -  fuel selector set appropriately to fullest tank or other per aircraft SOP.

(U)ndercarriage - Gear down

(M)ixture - Set rich for landing and possible go-around

(P)rop - for variable speed/pitch props. Set pushed in for maximum power high RPM for possible go-around and better throtle control and add landing drag.

(F)laps - Set appropriately

 

Obviously mixture does not apply to turbine aircraft and prop not to jets or fixed pitch props.

 

This short check is for mostly GA aircraft as a memory item. Airliners have a more complex checklist.