Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

AS2012, no overcast?

Featured Replies

its out now as a beta on the main site, http://dreamcatcher....pdate_B4448.zipActive Sky 2012Revision LogSP1B4448- Fixed problem related to Cirrus handling that could result in excessive cloud clearing/shifting as well as temperature and pressure depiction issues- Fixed problem where an Airport (vs. weather station) would fail to bring up proper interpolation station information in the Wx Report screen- Fixed problem with certain Sky Night textures that would cause an unwanted bright area of sky in some cases- XGauge: Made MET and DST textual weather information background color darker and more opaque for easier readability with brighter background colors (XGauge must be updated by running XGauge Installation Wizard’s file copy and access check)- Changed Airplane Icon in Map/XGauge view for better visibility- Fixed problem in Wx Edit screen where entering fractional visibility in the METAR string, parsing and then applying would result in an unhandled exception- Added support for fractional visibility entry (i.e. 0.25 or ¼) in the Visibility text field of the Wx Edit screen- Fixed problem where right-clicking the MAP screen with no flight plan loaded would result in an unhandled exception (now an informational message is shown asking the user to first load a plan with departure and destination specified before adding waypoints)- Corrected Latitude/Longitude/Elevation of FALE station in the default-supplied database- Fixed problem with Cirrus_Overcast03 texture being improperly handled when creating or installing Snapshots in some cases- Fixed problem with Cirrus_Overcast03 texture failing to properly build in some cases which may result in black/gray rectangles being depicted instead of proper cirrus cloud sprites- Fixed problem with cirrus texture handling when used with Turkish language settings which would result in black/gray sky or rectangles- Fixed problem where certain water textures may fail to copy/install in some cases- Fixed problem where machine code generation could fail in some isolated cases causing unnecessary reactivations on a single system- Various documentation edits to further explain or better clarify certain elements- Fixed problem in Wx Edit screen where deleting the only cloud layer or last cloud layer could result in an unhandled exception- Improved DWC very high-altitude aloft temperature handling (between 50K and 90k ft) to avoid unrealistically-low temperatures- Fixed UI Screen Size problem that affected some users, causing the UI to be “cut off” and partially inaccessible- Changed handling of upgrade verification check to properly allow product name of ASE or ASA during ASE/ASA upgrades (previously ASE must have been chosen regardless of ASE/ASA product being upgraded from)- Fixed problem with interpolation of pressure in some areas (mainly near north or south pole) which could result in lower than expected pressure and resulting in higher than expected indicated altitudes (thus resulting in lower altitudes flown using standard 29.92/1013 Kollsman setting for high altitude flight)- Changed handling of DWC depiction processes in order to eliminate problematic condition where the area around the aircraft might depict a clear-cloud scenario when surrounding (and reported) conditions include clouds- Fixed interpolation issue with surface winds which could result in far-away stations having too much influence with wind direction/speed in some cases- Fixed location of DAUO station in distribution data (must be updated from server or manually added via edit stations to affect existing installation)- Added Airport/Data station ESNZ in local data for new distributions (must be updated from server or manually added via edit stations to affect existing installation)- Added automatic warning and de-selection of confliction option when ATC Wind Lock and Suppress on Ground options are both enabled (which would prevent proper wind updates and ATC lock operation)- Fixed problem with rain/precipitation not properly depicting below 0ft MSL- Enhanced behavior of voice ATIS/flightwatch so that duplicate Inches/MB reports in some METARS default to Inches instead of QNH during voice readbacksChanged handling of manual refresh or wx edit “Apply” or Drag and Drop so that the depiction process is reset and will immediately depict the requested/reported cloud conditions regardless of settings such as “Prevent Cloud Redraws”, which previously prevented visual cloud updates in DWC mode

  • Replies 30
  • Views 6.1k
  • Created
  • Last Reply

Top Posters In This Topic

  • Commercial Member
its out now as a beta on the main site, http://dreamcatcher....pdate_B4448.zipActive Sky 2012Revision LogSP1B4448- Fixed problem related to Cirrus handling that could result in excessive cloud clearing/shifting as well as temperature and pressure depiction issues- Fixed problem where an Airport (vs. weather station) would fail to bring up proper interpolation station information in the Wx Report screen- Fixed problem with certain Sky Night textures that would cause an unwanted bright area of sky in some cases- XGauge: Made MET and DST textual weather information background color darker and more opaque for easier readability with brighter background colors (XGauge must be updated by running XGauge Installation Wizard’s file copy and access check)- Changed Airplane Icon in Map/XGauge view for better visibility- Fixed problem in Wx Edit screen where entering fractional visibility in the METAR string, parsing and then applying would result in an unhandled exception- Added support for fractional visibility entry (i.e. 0.25 or ¼) in the Visibility text field of the Wx Edit screen- Fixed problem where right-clicking the MAP screen with no flight plan loaded would result in an unhandled exception (now an informational message is shown asking the user to first load a plan with departure and destination specified before adding waypoints)- Corrected Latitude/Longitude/Elevation of FALE station in the default-supplied database- Fixed problem with Cirrus_Overcast03 texture being improperly handled when creating or installing Snapshots in some cases- Fixed problem with Cirrus_Overcast03 texture failing to properly build in some cases which may result in black/gray rectangles being depicted instead of proper cirrus cloud sprites- Fixed problem with cirrus texture handling when used with Turkish language settings which would result in black/gray sky or rectangles- Fixed problem where certain water textures may fail to copy/install in some cases- Fixed problem where machine code generation could fail in some isolated cases causing unnecessary reactivations on a single system- Various documentation edits to further explain or better clarify certain elements- Fixed problem in Wx Edit screen where deleting the only cloud layer or last cloud layer could result in an unhandled exception- Improved DWC very high-altitude aloft temperature handling (between 50K and 90k ft) to avoid unrealistically-low temperatures- Fixed UI Screen Size problem that affected some users, causing the UI to be “cut off” and partially inaccessible- Changed handling of upgrade verification check to properly allow product name of ASE or ASA during ASE/ASA upgrades (previously ASE must have been chosen regardless of ASE/ASA product being upgraded from)- Fixed problem with interpolation of pressure in some areas (mainly near north or south pole) which could result in lower than expected pressure and resulting in higher than expected indicated altitudes (thus resulting in lower altitudes flown using standard 29.92/1013 Kollsman setting for high altitude flight)- Changed handling of DWC depiction processes in order to eliminate problematic condition where the area around the aircraft might depict a clear-cloud scenario when surrounding (and reported) conditions include clouds- Fixed interpolation issue with surface winds which could result in far-away stations having too much influence with wind direction/speed in some cases- Fixed location of DAUO station in distribution data (must be updated from server or manually added via edit stations to affect existing installation)- Added Airport/Data station ESNZ in local data for new distributions (must be updated from server or manually added via edit stations to affect existing installation)- Added automatic warning and de-selection of confliction option when ATC Wind Lock and Suppress on Ground options are both enabled (which would prevent proper wind updates and ATC lock operation)- Fixed problem with rain/precipitation not properly depicting below 0ft MSL- Enhanced behavior of voice ATIS/flightwatch so that duplicate Inches/MB reports in some METARS default to Inches instead of QNH during voice readbacksChanged handling of manual refresh or wx edit “Apply” or Drag and Drop so that the depiction process is reset and will immediately depict the requested/reported cloud conditions regardless of settings such as “Prevent Cloud Redraws”, which previously prevented visual cloud updates in DWC mode
where is the original post for this update? Its not in a sticky?

Alex Ridge

Join Fswakevortex here! YOUTUBE and FACEBOOK

Hi, the SP1 information you see is a public beta. It is not an official SP update at this time. That information was emailed to our users and if you didn't get one please let me know and I will have the link sent to you. I do stop in to check the forums on a regular bases. This is a community that helps support one another. Officially, our support is done through our ticketing system now. Obviously, this helps us to keep track of bugs and other issues so we can help improve the program for everyone. So, making a statement that there is virtually no support, is a fallacy.

Yes I stated it was a beta and I also said there was no support on this forum, there has been little if any word from HIFI here regarding 2012 problems and impending updates, all I have seen is my previous post moderated where I said I wished I had not upgraded from ASE when somebody asked if it was worth upgrading, I didnt receive any email either advising of this beta although admittedly it may have been spammed by my filter.If you officially represent HIFI sim should you not have commercial member status to help identify your position? Anyway thanks as it was your post that got me looking for the SP for 2012!

Yes I stated it was a beta and I also said there was no support on this forum, there has been little if any word from HIFI here regarding 2012 problems and impending updates, all I have seen is my previous post moderated where I said I wished I had not upgraded from ASE when somebody asked if it was worth upgrading, I didnt receive any email either advising of this beta although admittedly it may have been spammed by my filter.If you officially represent HIFI sim should you not have commercial member status to help identify your position?Anyway thanks as it was your post that got me looking for the SP for 2012!
Damian and his team have been working tirelessly to fix the issues that have been reported with AS2012. So, the support from Damian directly has been little as he has been working on fixing the issues reported to him.In regards to me being part of the support team: please read this http://forum.avsim.net/topic/359022-new-hifi-additions-and-development-news/In regards to support: please read this http://forum.avsim.net/topic/350985-official-support-supporthifitechinccom/While I do my best to check in the forums on a daily bases, I can not always respond as the support tickets are the official support now.Hopefully SP1 will address most of the issues that have been reported here and in the support tickets. There are bound to be a few bugs, and reporting them is always appreciated here or by the ticket system. We only ask people report issues to the support system as the organization is far better and priority can be given.

OK understood and thanks, will give the beta a whirl and see if things have improved

installed SP1 beta, lovely overcast conditions at EGKK this morning, looked awesome, I cant figure out how to post a screenshot but I am very pleased with the update, met stations were holding the wx conditions accurately which has been a big problem for me so farThank you.

ASE and AS2012 both have been able to produce overcast "looking" skies from below and strong broken cumulus clouds (almost overcast) when flying above. Let's clarify the issue and that's NOT it. It is what happens when you try to climb or descent through that "overcast" and find that it has melted away below and around you into scattered or broken at best! So far I have not seen even broken cloud cover ceilings below 2000 agl. In RW we consider that VFR ( if at least 2 sm vis). Now that is fine for the many FSX users who just want "pretty" but realistic scenery displays. The discussion among the more sophisticated users, however, is the need (which has not been fulfilled to date by ASE, its predecessors, or AS2012) of a true genuine IMC condition of LOW ceiling stratus (or cumulus) overcast. And by low is meant at least solid down to 200 ft agl (which would just be a Cat 1 ILS approach) where NOTHING can be seen (in-cloud, zero visibility) until below that altitude. FSX is capable of displaying this if manually entered and a second layer of visibility (set to 1/16) is setup for the altitudes from base to top of the overcast layer. Not only will it produce the desired appearance from above and below but, most importantly, will produce the RW sensation of flying blind down to minimums -- a true IMC simulation. That is what we are hoping that Hifi will pursue until they can accomplish it.

In response to HiFly. While it is possible to produce the overcast results manually, try to fly the entire flight on manual. You'll see 0 visibility your entire route. So, again, when you hear the phrase "it is a FSX coding issue to produce true overcast" that's what it is. I understand what you are saying in terms of wanting true overcast and I too want that same thing. So your critiques are appreciated. If it were possible to have true overcast I believe Damian and his team would have accomplished it.

In response to HiFly.While it is possible to produce the overcast results manually, try to fly the entire flight on manual. You'll see 0 visibility your entire route. So, again, when you hear the phrase "it is a FSX coding issue to produce true overcast" that's what it is. I understand what you are saying in terms of wanting true overcast and I too want that same thing. So your critiques are appreciated. If it were possible to have true overcast I believe Damian and his team would have accomplished it.
So since it can't be done due to fsx limitations (I believe you by the way) then there is no real point in buying another weather engine again.

 

 

Thats a personal opinion you have and I respect it like I do all opinions. I personally think AS2012 has some of the best overcast I've visually seen in FSX. While I said it was a limitation , I never said it was impossible. I'm not a programmer (and never have claimed to be) I just know it is a well documented limitation of the game.

While it is possible to produce the overcast results manually, try to fly the entire flight on manual. You'll see 0 visibility your entire route.
You have slightly misunderstood my post, Joshua. Visiblity layers in FSX can be stacked one on top of another just like clouds, winds, temps, etc. For example to have a stratus overcast manually input would consist of correct cloud layer as well as a corresponding visibility layer at same level as the cloud deck.Say you want a deck from 200-4000 msl total overcast with an airport visibility of say, 1/2 sm. In this example, assume a sea level airport for simplicity. If you want it to be a stratus overcast you would have to first set a lower layer of overcast stratus such as 200-1200 agl and then immediately above it, an overcast layer of cumulus from 1201-4000. Now you would set visibilty to 1/2 from 0-200 msl and then activate a SECOND layer of visiblity from 200-4000 set at 1/16. Now when flying above it will be normal visibilty (usually I set mine for 50 miles in AS2012)with a SOLID deck (no holes) below. On the surface it will appear as a dark solid overcast (no holes). When flying through it you will have zero visibility from 200 msl all the way up to 4000. You will break out below the overcast at 200 msl or when climbing you will break out at 4000 ft msl. That is real world overcast deck and it can be programmed exactly that way in FSX. Try it. The assumption that FSX only will allow a SINGLE visibility layer is FALSE. You can have as many as you like. AS2012 just needs to have code designed to address this procedure. If it can be produced "manually" it can be encoded. The example I used was for a low stratus overcast layer. If a cumulus overcast were desired the first level of stratus would be unnecessary. And BTW FSX needs a better stratus texture (sprite) so that stratus layers don't have the appearance of multitudes of "chicklets" stuck together!Now back to your point, Joshua. It would naturally not be practical to program enroute weather this way, but when a DESTINATION metar specifies OVERCAST then that's what we need to encounter from the top of the deck all the way to the low ceiling and not scattered or broken.
  • Commercial Member

High Craig,You have some valid remarks there and I'd like to try and explain why it is difficult from a programmer's point of view to generalize the pattern of intermediate visibility layers for the whole weather depiction. It's as simple as that: We don't control directly when and if we are inside a depicted cloud. Even FSX itself doesn't know it, or at least it doesn't report it accurately. This way, trying to generalize the concept of intermediate visibility layers carries the risk of awkard 1/16 visibility at some point least expected (outside a cloud). This would only be of certain success if all the weather stations had the same overcast weather (not so realistic IMO and you have to remember that many stations are very close to each other).However, the whole IMC enhancing experience is one we've been working heavily on with Damian and we'll keep your remarks noted. I'd like to thank you for your valuable feedback (on this and other things like the temps etc). We may not speak too much in here, rest assured though we are reading all the posts here and in particular well documented posts such as yours will always provide us a clear picture of what our users think is most important and this way drive the development process of new things, fixes etc.Kostas TerzidesActive Sky developer

Kostas Terzides

 

devteam_bannerA.png

Thanks for you timely response, Kostas. I have never lost faith in you guys. Your comments helped to explain another anomaly I have noticed with both ASE and AS2012: since the metars only give the cloud bottoms--no tops, and no types, I assumed that you were using some type of algorithm to randomly generate the cloud type and vertical height but I thought that once generated, that information was permanently stored with the station for that metar. I have been disturbed, however, by the fact that I notice if I return again to the weather edit page for a station it is not uncommon to have the cloud types and vertical height be entirely different. Also it seems your program sometimes will not retain changes I make to the metar after I leave that edit page. It seems never to keep Cumulonimbus clouds nor any settings of severe turbulence or severe icing that I input. On a very positive note: because of my previously mentioned concern over inaccuracies of temp/wind changes with altitude using DWC I returned to Standard mode and was pleasantly surprised to find very little cloud popping (seldom if ever) and VERY FAST updates now with this new version. The big frame rate drags occuring for a minute or more seem to have been remedied. That is a phenomenal improvement and makes Standard mode a very pleasant workable alternative to the DWC. Thank you all.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.