Hi James!

Well you seem to be opposite of everyone else for some reason. According to the manual, DWC is same at all levels and STANDARD is RW at all levels and that is the results I consistently get. Bottom line, James, is to use whatever works for you! If you are able to get real world weather displayed in FSX at all levels with DWC then by all means why would you not want to always use it?

October 2012 - 11:35 AM

 

I have been monitoring this forum since it began. I have been using AS2012 and before that ASE

Craig

I have been using the DWC in AS2012 since it was released last December. I am trying the STANDARD mode on a flight right now. It appears that when the weather updates the upper part of the monitor screen flashes white. I found an old thread about ASE that pretty much says the flashing is like death and taxes. It's a sure thing in the STANDARD mode. What has your experience been with this issue?

 

Thank you

Michael Cubine

Craig, this is from the AS2012 manual:

 

Standard.

Standard weather depiction mode uses normal SimConnect station-based weather writes and supports Range Suppression to reduce visual cloud changes (shifts) within your local view range. Recommended for best accuracy and consistency of SURFACE weather depiction.

 

Direct Weather Control.

Uses unique method of directly controlling ambient weather parameters resulting in the best balance of accuracy and smoothness of all weather especially aloft winds. Recommended for longer-range and airliner-style flights where winds aloft accuracy is important. Includes full real-time Wind, Visibility and Barometric Pressure Smoothing.

 

I think my DWC correctly matches what it should do, based on this description. What do you think? Do you have any particular option checked in order to get correct winds aloft with standard mode? Thanks.

I thought this was a forum dedicated to Opus weather engine. Would it not be polite to take your AS2012 issues to the correct forum. In all fairness.

Seconded, come on gentlemen off to the AS topic please.

 

Stephen

@ Michael: The flashing that you see is the weather updating. Like OPUS, ASE and AS2012 only inject a certain area of coverage and since FSX will eventually try to smooth the weather back to calm and standard conditons, the weather info has to be periodically re-injected (every so many minutes) into FSX in order to maintain correct depiction. That is what you are seeing and it does stutter the frame rates while it is loading. I have my exclusion range set to 200 and my load range to only 225 so the only loading is that outer ring between 200-225 which only takes a few seconds every 5 minutes or so. A tradeoff for sure but it is the most accurate winds/temps aloft of any of the engines so far. Not that FSX doesn't occasionally even "screw" that up but by using FSUIPC registered with wind smoothing it has become a rarity.

 

@James: I originally began using DWC equivalent with ASE and was troubled by what it was doing to the surface depictions and when I questioned Damian, he told me that in order to make it work ALL WIND LEVELS from surface up had to be set the SAME and thus my AI traffic would be landing/taking off in unrealistic conditions. When AS2012 was introduced it would not allow correct interpolation of temperatures during climbout and to my knowledge even though claimed to be now fixed, others have reported it is still an issue. Sudden changes in temperature on climbs/descents cause spikes in engine performance that would not be experienced in RW. This is most noticeable on more realistic models such as NGX and ConcordeX where temperature aloft during climb/descent is critical. Again, despite the quote from the manual, the temp/winds aloft are AVERAGED which again is not RW. This was introduced as an alternative to FSUIPC to eliminate the sudden wind shift glitch inherent occasionally in FSX.

 

@Stephen: I agree and apologize. James, Michael: if further discussion or questions for me, please direct them through the Active Sky forum.

We will soon provide GRIB data forecasts within the LWE and our updates are instant, detailed, and accurate !

 

No more please, this IS the OpusFSX forum.

 

Stephen

Craig, one thing you need to remember is how the FSX ATC engine works and how it chooses which runways will be active. When you load the weather at the main create a flight page in FS it automatically sets the active runways in FS based on the winds AT THAT TIME, the AI will use the runway best suited to the wind direction. Now assuming you have your airports runways configured appropriately ( that being either you have all runways open or the ones you want used for landing and takeoff) when you load up FS should be using those runways.

 

Lets say they are landing to the south at Denver on the 16's and 17's when you first load up. If your flight started in SFO-JFK and you flew over Denver 2 hours later in the sim (unless you FS did a mid flight reload) Denver should still be using the south ops. But what if during those 2 hours the wind shifted? Even though the ATIS may say they should be using the 35's and 34's you will still hear them using the 16's and 17's because FSX (& FS2004) doesn't support runway change in sim.

 

Unless I misread your original question about having the correct runways in use when you tune in to the respective ATIS enroute, that's a shot in the dark. The only way to properly ensure having the correct runways active for any airport you tune to would involve reloading your sim periodically while enroute to reset the desingated runways given the winds.

 

I HOPE I am comprehending my own thoughts correctly. This was compiled from an AI enthusiast with an AI perspective in mind.

The only way to properly ensure having the correct runways active for any airport you tune to would involve reloading your sim periodically while enroute to reset the desingated runways given the winds.

 

An option that should be implemented in OPUS is the AI Traffic refresh, you press a button and the AI traffic is reloaded, compliant with the present wind and runways conditions. In order to do that, the best would be to have the OPUS interface on a second computer...

We recommend doing a manual weather update when you are about 35nm away from your destination, then you can listen to the ATIS and determine the correct winds for landing. Perhaps we can provide an option for you to enter your destination and we can then do the weather update automatically for you 50nm from your destination.

 

On approach, all weather updates are disabled for 15 minutes on the final descent as soon as you descend through 2800 feet AGL (this process is cancelled whenever you climb above 3000 feet AGL). This was done to minimise the wind shift problem but we are going to introduce an option to enable/disable this.

 

Regards

Cheryl

Again, I think what Craig was wanting was so that no matter which airport ATIS he tuned to his AI would be using those respective runways. If the winds shift towards using a different runway than what was being used when the sim first loaded the AI won't change runways unless the sim is reloaded to take advantage of those winds. Manually refreshing the AI itself might work, but i'm not 100% confident in thinking that resetting the AI will institute the new runway. I thought that the FS runways were determined when you first loaded up.