ASE not updating

[Jet2 0]

Hi Jim/Damien, ASE is behaving strangely. I did a flight yesterday and most of the destination weather was the same as my departure (wind,temp,pressure) even though the 2 airports were 4000nm apart! I did a test today sat on the ground at MYNN and after the initial set (which was ok) the weather did not update. I checked the ASE interface and that was succesfully downloading and displaying the latest metar, but it was not updating it in FSX. I fired up ASA and did the same test and everything updated as normal, strange? I'm using the latest builds, FSX SP2, FSUIPC 4.25 (weather settings off), Vista basic 32bit. I'm not in 'global mode' in ASE. Not sure where the ASE ini is so I cant post it. I also have FSC running on wide client from my laptop and traffic board via simconnect though ASE is on the host machine. Am I setting something up wrong? Any help would be good but i'll stick to ASA for now.RegardsMark

[JSkorna 137]

Hi,Sorry for the problem. Please post your ASE_Log txt file and I'll take a look at that.Also, make sure that you start ASE before FSX and if you close FSX that you also close ASE.

[JRBarrett 3,104]

Hi,Also, make sure that you start ASE before FSX and if you close FSX that you also close ASE.

I've seen this advice given before, (start ASE before FSX), but I have had nothing but problems trying this.In order for FSX to initialize into a stable and predictable state, it is essential that NO external programs attempt to interact with it, either via FSUIPC or via simconnect, until said initialization is fully complete. IF ASE is already running when FSX is started, it immediately begins sending its weather depiction to FSX very early on - even before the intitial load of the aircraft, and terrain textures completes.The result is that FSX loads with a variety of problems - including corrupted graphics, panel features (radios, instruments etc.) either inop or working incorrectly, and general instability - manifested by poor frame rates, and lockups and CTDs that happen very early on on the attempted flight.I've tried this numerous times - with ASE running on the same PC as FSX, and with ASE running on an outboard PC, via WideFS, and the result is always the same... an FSX that is so unstable that it never fully loads at all, or which crashes within minutes - usually before even beginning taxi to the runway. It's bad enough when starting FSX with a default aircraft like the Trike or Cessna 172, but even more of a problem when starting with a complex aircraft situation file, like the PMDG 747 or MD-11, or the FSLabs Concorde - all of which have their own protracted initialization routines that go above and beyond the default init that FSX performs.It would be different if FSX had the ability to tell ASE to "wait" (on sending wx info via simconnect) until it (FSX) was "ready" to receive the data, but that is not what happens - the instant that ASE detects that FSX is "alive" (which seems to occur the moment the opening FSX splash screen appears), it starts "slamming" FSX with METAR strings, before the FSX internal WX processing engine has even fully loaded. When doing this, I have seen the ASE "beginning weather depiction" status message scroll across the top of the FSX window, before the "loading terrain" status bar has even gone past the 25% mark.That seems to me to be a certain recipe for disaster.I always wait until FSX is fully loaded and initialized (and, if using an add on like PMDG, I wait until the add-on aircraft has completed its own load and initialization) BEFORE starting ASE. In doing so, I have never had the slightest problem with the two programs communicating reliably.For the same reason, I never start FSUIPC-based programs (FS Commander, Squawkbox etc.) until after FSX is fully initialized.I don't understand why you would want ASE to be running before FSX. What would be the advantage in doing that?Jim Barrett

[JSkorna 137]

Hi,1. To load any textures into FS you need to do that before running FS. So Snapshots or your texture program needs to run first.2. What ever works for you is the best situation for your set up. If your FSX is unstable any other way, then it is possible that your FSX install is not solid.3. Starting ASE after FSX can lead to SimConnect not communicating with ASE.4. Many internal FSX programs begin running before FSX is fully loaded, FSUIPC being one of them.So the general rule has always been to start AS first, since FS 2002, and generally I will continue to make that suggestion!! But what works for one, may not work for everyone!

[Jet2 0]

Thanks Jim, i'll try loading ASE first, ill also do some other testing first before I pester you too much, seems strange ASA is fine and ASE wont work. What are the fundemental differences between the two in terms of features and how they communicate with FSX, I may stick with ASA if there's not too much difference. As for my log file (ASE_log) all it says is:-12:51:57:0285 - Flight Plan Retrieved - Dataset data about to be processed17:35:06:0688 - Flight Plan Retrieved - Dataset data about to be processed13:49:34:0972 - Flight Plan Retrieved - Dataset data about to be processedThanks for your helpKind regardsMark

[ACA857 5]

Hi Jim,In my experience, starting ASE before FSX caused problems for me...I have to agree with JRBarret's observations where ASE is fighting with FSX before FSX has even initialised...since I started opening FSX first, and then loading ASE, many of the problems I had went away...like DEST wxr being incorrect, frequent ASE disconnects, and CTD's in FSX. I have had about a dozen flights with this process and I have no problems at all...touch wood.I should also note, I installed the FULL ASE version - I *was* using the AS6.5 upgrade to ASA and the free upgrade ASA to ASE with several issues I reported at this forum...so maybe the problem was version related and not to do with the start up sequence of FSX and ASE, I have no way of telling.

[Jet2 0]

Done a little testing before I nip out to watch more of the world cup! Tried starting ASE first and it made no difference. I was lucky enough to get this excellent program for free as i'm a long time customer of HiFi, hence I do have the upgrade version, surely this won't make a difference to having the full version? Going to try a reinstall too. Would upgrading to the latest fsuic make any difference? I'll let you know how i get on. Off topic question. Does ASE reproduce those wonderful towering cumulus clouds or 30000ft cumulonimbus, like in Asv6.5? I know ASA is a bit week on this with poor cloud heights during thunderstorms.Kind regardsMark

[JSkorna 137]

Hi Mark,We did need to limit cloud heights in ASE so you will not see 30K towering clouds.Wouls like to see a ASE_Log file. I know you posted that little bit, but I think that is the wrrong file. It should have multiple line of messages in it.No, we don't communicate with FSUIPC4 at all.

[JRBarrett 3,104]

1. To load any textures into FS you need to do that before running FS. So Snapshots or your texture program needs to run first.Yep, I know about that limitation - can't change texture files once they are locked by FSX. I still use XGraphics as a "standalone" app to load my desired weather theme before starting either FSX or ASE. I prefer it to the "snapshot" technique - just my own preference.2. What ever works for you is the best situation for your set up. If your FSX is unstable any other way, then it is possible that your FSX install is not solid.I'm pretty sure that my FSX is very solid indeed. The main problem for me is that I use complex add-ons almost exclusively, and both PMDG and FSLabs aircraft definitely do not "play" well with any kind of simconnect data injest activity taking place while they are in the midst of their own initialization. In the case of PMDG aircraft, it's something I've learned through experience and experimentation. In the case of the Concorde, the developer specifically warns against running any ancillary programs until the aircraft and panel init is complete. The Concorde is not "done" initializing even after the panel appears - there is still about 30 to 45 seconds of activity taking place behind the scenes before it is truly "ready". 3. Starting ASE after FSX can lead to SimConnect not communicating with ASE.I've heard of that issue. Fortunately, it's never happened in my installation. ASE always is able to communicate with FSX, even when being started second.But, as you say, users should go with the technique that works best in their own particular situation.

[Jet2 0]

Morning Jim, after the initial weather set ASE is still not updating, i've reinstalled it and updated to latest fsuipc but still nothing. Sat on the ground at KMCO last night, weather injected fine so I went to bed, woke up this morning and even though the metar string in ASE had updated, the weather in FSX was exactly the same as the initial weather set, its as if ASE is ignoring FSX. There were no other programs running last night.Is there any chance I can try the full version rather than the ASA update version I have, I can send my order details, might be worth a try. I'My ASE_Log file is too large to attach here and I cant find an email address at hifi to send it to.Kind regardsMark

[norman s 15]

Hi Jim and all others,I cannot get ASE to display the weather in FSX .After so many attempts I have switched back to using FS9 and ASV6.5.Mine was an upgrade version.Anotheritem which may have a bearing on things is that when trying to insert licence(from Simmarket) for ASA I am always getting a licence not recognised message.I have mentioned this before but at HiFis end the servers show it correct.Problems do exist and need addressing.Norman Bowman

[JSkorna 137]

Hi Mark,Your Simconnect is not communicating with ASE. As you move around in FSX, does ASE recognize the movements?We don't use FSUIPC at all so you don't need to mess with that.If you want to try the Full version you can drop me an e-mail, but I think it is a Simconnect issue, based on that log you posted. The same is true for your log file.

[Jet2 0]

Thanks jim, am I right in saying simconnect is located in the same folder as the FSX config? Is that all I need to have or does something need to be somewhere else or some settings changed. I wont bother trying the full version just yet if you've identified my problem. What can I try to resolve the communication problem or what could be causing it?RegardsMark

[JSkorna 137]

Hi,Simconnect in the in the Windows/SxS folder.Your should start backwords uninstalling FSX versions untile you have just your base FSX. Then you reinstall SP1 and SP2/Acceleration for FSX.

[Jet2 0]

Ah damn it! I was worried I may have to do something like that. Is there any way of just re-installing simconnect that you know of or is reinstalling the SP's the only way to go? Does simconnect come with FSX SP2 patch? Thanks very much for all your help as usual Jim, never a dark day on the support front!!Kind regardsMark