Jump to content

Archived

This topic is now archived and is closed to further replies.

737guy1

Weather at arrival airport updated late

Recommended Posts

I cannot seem to get my OpusFSX to load the conditions at my destination airport before FS ATC gives me vectors to land. The FS ATC just assignes me a runway based on the weather that I had on the surface at my departing airport. I have set my destination in the weather download section and made my forced recovery altitude to 25,000ft. Is there anything else I can do or is this just an FSX limitation?

Share this post


Link to post
Share on other sites

What was your cruise altitude and recovery altitude set at. Surface wind recovery is enabled only after you climb above the RA + 500 feet. Recovery will be attempted after you then descend below RA with forced recovery occurring after you descend through the specified altitude.

 

Stephen

Share this post


Link to post
Share on other sites

My cruise was set in the weather download option as FL370 and I did cruise at that altitude. Once again my recovery and forced recovery altitude are set at 25000.

Share this post


Link to post
Share on other sites

I also noticed that my destination weather is fully set at about 4 miles to land, visibility could go from 10km to the metar's 1500m when i am about 5-4 miles in the ils. Is it possible to set a wider radius and ceiling for arrival like 30 miles and 10000ft so the conditions don't drastically change on final approach.

Share this post


Link to post
Share on other sites

If that's with the current beta then it should be ok, I will check the handling of the RA and forced RA when they are the same. If its an older version I assume you set 37000 for the cruise. If you had Automatic Settings enabled then the RA would have been overridden.

 

With your destination set the LWE would give priority to the destination METAR (if one exists) between 10 and 20 miles in each direction. Beyond that zone all METARs will be treated with equal weighting. Your destination weather should have been updated long before your arrival, similarly, unless the weather updates were disabled, the recovery of the surface conditions should have occurred long before your arrival. In your case it certainly looks like the destination vis did not extend much beyond the priority zone.

 

Stephen

Share this post


Link to post
Share on other sites

The METAR is correct when I arrive I just wish there was a way to have it communicate it with FS so that FSATC will assign runways and approaches based conditions there at that airport and not on the conditions at my aircraft. It seems with default FSX weather I did not have this problem (however the weather was nowhere near as accurate as OpusFSX). I am having UT2 aircraft landing or taking off coming towards me while I land on the correct runway despite FS ATC's instructions.

Share this post


Link to post
Share on other sites

Make sure you have recovered the winds before you contact ATC, otherwise it is possible static winds will be used. If static winds are in force this will be indicated in the weather report window.

 

Share this post


Link to post
Share on other sites

Oh ok thanks for that tip; that makes sense. But will that make the AI traffic land the correct way? Still seems like there will be some landing and takeing off the same way as me and some going off of static weather and landing and taking off opposite.

Share this post


Link to post
Share on other sites

I agree, I don't think it will guarantee all AI traffic landing the correct way due to flights being queued but you will have to see how it goes.

 

Regards

Cheryl

Share this post


Link to post
Share on other sites

The AI traffic I am using is Ultimate Traffic 2. I figure that unless there is a way to have the LWE communicate to FSX the conditions at an airport about 75NM out, there will be some AI flights landing the wrong way.

Share this post


Link to post
Share on other sites

Hello!

 

I had a similar case yesterday. I'm using VoxATC (or Radar Contact) with FSX AI traffic (Traffic 360 visual models).

 

VoxATC/Radar Contact works in a similar way to the one Mitchell mentioned:

 

ATC assigns me the same runway that the AI is using. The decision is made, when I'm 50-80nm away from the airport. The sequence of event goes something like this, when flying lower airways (below FL240):

 

1) Runway in use is selected based on destination weather when ~70nm from touchdown

 

2) When ~50nm from the airport, ATC requests me to start a descent

 

3) I pass Opus recovery altitude ~40nm from the airport (cruise FL190, Recovery automatically set to 17000)

 

4) Surface wind are recovered?

 

5) ATC vectors my to the runway selected in step #1

 

6) Landing is made with a tailwind component

 

It was a late night flight, but this is what I think happened.

Share this post


Link to post
Share on other sites

You could set your recovery at 29,000 and the forced recovery at 25,000. Don't use the automatic settings since it will adjust these figures.

Share this post


Link to post
Share on other sites

I can't remember if the automatic settings was checked last time I flew or not. I have now made sure it is unchecked and have set my recovery from 25,000 to 29,000 and my forced recovery to remain at 25,000. I will report on the results after my next flight.

Share this post


Link to post
Share on other sites

What happens if we do not set a destination? How many updates would we get in the descent/approach phase? Alternatively, what if we updated the weather let's say 100nm out and then disabled updates for the remainder of the flight? What if we did that with a destination and without? What would the destination weather be? Maybe it wouldn't be dead on to the METAR that was reported 5 minutes ago, but would it be weather that is expected at the destination(i.e. not the weather at my current location/altitude)?

 

I'm still trying to find the right settings that will give the fewest updates. Especially on departure and most definitely on approach/arrival. I think in some ways, with the earlier versions of Opus before we could set the destination and before winds/temps aloft, there were less updates and a lot better feeling of flying into the weather(less "popping"). Now, we're getting updates when climbing/descending, updates when a timer expires and/or a distance is flown, and then updates based on how close we are to some destination.

 

It's been sort a debate in my own mind on whether to switch back to the simpler earlier versions where I could really get that great feel of flying into weather in the distance where when I am on descent or approach and am flying towards a cloud, I knew it wasn't going to "jump" 100 feet to the right because the weather got updated. The weather generated by Opus is still just amazing and I love it. I've never had so many amazing IFR flights before. Just want to minimize the updates.

Share this post


Link to post
Share on other sites

Hi Kevin

 

We cannot prevent FSX redrawing clouds on a weather update. See if the forthcoming weather smoothing helps (we are still beta testing).

 

If you don't like updates then for now get into the habit of manually disabling weather updates (via the addon menu or shortcut controls) and re-enabling them when you want. You can also disable updates on approach, it's best to disable Adjust Options Automatically since they override manual settings.

 

We would usually recommend specifying your destination since if you don't the METAR for your destination may not be correct i.e. it may be older than it should be, but it depends if that bothers you, the choice is yours.

 

If you set the Live Weather Update Distance greater than 192km the LWE will inject the full size 992km x 992km (535nm x 535nm, or 616 x 616 statute miles) region into the simulator, centered on your aircraft. If you fly beyond this region then the weather would not be accurate so you can time your manual updates accordingly.

 

If you want accurate winds at your cruise altitude then you must specify your cruise altitude, but again the choice is yours, you could just update at the start of your flight then disable further updates until required or you pass the boundary of the weather region.

 

Regards

Cheryl

Share this post


Link to post
Share on other sites

Thanks Cheryl...That was more or less the answer I was expecting. I've kind of mentioned this a couple different times in this forum. :) I'm hoping the weather smoothing options help too.

 

With the latest addition of key assignments or 'hotkeys', would it be possible to add a key shortcut to enable/disable updates then so we don't have to open the menu and do that?

Share this post


Link to post
Share on other sites

Should be no problem. See how the cloud smoothing beta dev cycle pans out first, that or the currently considered 'Use Global Weather Above' option will most likely prevent those changes. But if you want accurate weather at your destination it will have to eventually change.

 

Stephen

Share this post


Link to post
Share on other sites

But if you want accurate weather at your destination it will have to eventually change.

 

That's the key statement for me...I totally appreciate the want by some or most for exactly accurate METAR upon arrival, even at the expense of "cloud popping". But, for me, I'd rather have a 45 minute old METAR at my destination but have a smooth approach within the final 100nm to my destination.

 

To elaborate on what I mean by "smooth approach" a little more...I'd like the destination METAR to be set for a final time about 100nm out and then just know that when I get to the airport, it's going to be what it should be as reported in the METAR from the time 100nm ago. Also, to have ATC(Radar Contact in my case) know of this destination weather so when it gives approach clearances/runways, it's giving correct ones and AI is using the same correct approaches/runways. From what I can tell, this would be accomplished then if I just disable weather updates at 100nm from my destination, right?

 

As always, thanks again for the quick responses and listening to maybe slightly different ideas on how someone would like things to work. Excellent support!!! Thank you!!

Share this post


Link to post
Share on other sites

You seem to be assuming FSX is capable of storing detailed weather accurately at virtually any distance, irrespective of how limited the memory it can access, or that it even smooths out and morphs METAR weather even 80 miles away. With our method of injection it will be fairly accurate but FSX has many limitations.

 

Stephen

Share this post


Link to post
Share on other sites

You seem to be assuming FSX is capable of storing detailed weather accurately at virtually any distance, irrespective of how limited the memory it can access, or that it even smooths out and morphs METAR weather even 80 miles away. With our method of injection it will be fairly accurate but FSX has many limitations.

 

True. Sorry, I sometimes forget what we're dealing with here when it comes to FS itself. So, what would happen then if I did one final update 100nm out and did not update again after that? What would the weather be at destination? What would it be like the remaining 100nm - cloud popping/shifting? Does Opus still "update" as you fly along your route and descend through various altitudes? Does forced recovery and the like still happen if updates are disabled? What would Radar Contact know about when it issues its approach clearance(around 40nm +/- out).

 

Sorry again if these have all been answered before. I am pretty confident I know the answer for some but some are based on previous versions of Opus too and just wonder if that understanding needs to change.

 

Thanks for taking the time again.

Share this post


Link to post
Share on other sites

If you perform an update at 100nm out then disable updates the current METAR would be loaded for your destination and no further updates would take place, not even the forced recovery if it hadn't already occured. No idea what Radar Contact would do, you will have to try it.

 

Regards

Cheryl

Share this post


Link to post
Share on other sites

I kind of run into this issue from time to time. Love Opus BTW!!!

 

Question to those in the know. I fly short haul commuter flights. CYYC to CYEG and back. Kelowna to Vancouver. and so on and so on.

 

Typical distance based on flightplans pulled from flightaware are 100 to 150 miles and typically 12000 to 18000 feet. I generally fly the JS41 from PMDG in place of a good Beach 1900 or Dash8 and I also fly the B200.

 

Is there an optimum setting for these flights to prevent the "late ATIS". I mean the ATIS and METAR match once I am getting close to intercepting the localizer where I am say... about 10 miles out. What I like to do is call up ATIS about 40 miles out so I can choose an arrival based on an expected RW but this is challenging.

 

I am putting in the destination airport and cruise altitude. Besides that, is there something I am missing?

 

Charles.

Share this post


Link to post
Share on other sites

Hi Charles

 

If you want to use automatic settings then use the destination weather report (which can be accessed from the shortcut controls) as your long distance ATIS to plan your approach. The LWE will sort everything out for you when you are within 30 miles (i.e. radio contact distance) of your destination. Using any other form of long range ATIS is not guaranteed since it does not take account of how FSX stores weather internally. The destination report can be relied upon for accuracy.

Share this post


Link to post
Share on other sites

fantastic!

 

Will you eventually put the Max cruise altitude and destination ICAO option into the "ingame" menu? So that we dont have to bother with the background app GUI?

 

Thanks!

 

Charles.

Share this post


Link to post
Share on other sites

×
×
  • Create New...