JimI must have been typing the reply when you made your post. What about the changes I made to FSUIPC.ini and FSX.cfg per instructions in the documentation? Change them back or leave them at the same setting?Michael Cubine

Forget this post. I remember I made the line changes in these files for ASE not DWC.Michael Cubine

JimI was doing a flight from KORD to KTPA and on descent into KTPA when the power went off. The UPS is not strong enough to work with the desktop I am using. I was flying the 744 to see if S-turns started and to tryout the Smooth Cloud Depiction. 1. There were no winds aloft ever though the coded route weather reported there were.2. There was no haze layer ever though it is not disabled in ASE.3. The BNA VOR was part of the route so that KBNA had a metar in the briefing. I turned in the ATIS and the wind direction and speed were not even close to the metar.The temperature seemed ok.4. Why do I get the crawl showing stations updated when the download is disabled and dynaminic rate of change is set a 0%?Michael Cubine

Hi,1. Show me a screen shot of the Shift/Z wind display in FSX and the corresponding Report screen in ASE.2. Then you have another texture that has disabled the haze. Did you have haze for the past flights?3. Are you refreshing the AI system one time before you begin your first flight, once ASE and FSX are running and you are in your plane? Also you use the FSX ATIS system to get conditions at your departure and destination airports. You don't use the FSX ATIS system to get conditions along your route.4. Because even in Offline Mode station weather still gets updated and the Dynamic Rate of Change does not prevent weather updates.B642 has been released now for 6 months. Have you been seeing these situations for the past 6 months?

Michael, I just posted this on the RADAR CONTAC forum:Well I am sure I am going to get "flak" with my response to your questions (LOL) I have worked so long with Pete Dowson (FSUIPC) and the ASE team on how to get the best results. NONE are satisfactory they all have problems. Instead of a long discussion on what is wrong with each of them, I am going to tell you what I do now and why. Today I use ASE build 446 in DWC mode. The reason for this I get the best enroute WX and it works with my LDS 767 the best. I don't use any of the enhance WX stations, and I have unchecked the Force Destination WX option also. I also have FSUIPC registered with WX options set to wind and pressure smoothing ON. I get perfect departure WX with the above setup and terrible destination WX via the RC ATIS call. Yesterday flying into KSFO, RC ATIS was wind 190/15, when I was on final, tower said winds calm, actual was 250/15. ASE is reporting winds via the RC ATIS call close to what is going on at my aircraft location. Its so bad I don't pay any attention to what the RC ATIS report says. I use the US National Weather Service site when planning my flights to get the METAR forecast for my expected landing time. In the example yesterday at KSFO, the METAR forecast was winds 250/15 gusting to 20. On final ASE had the winds 250/15 no gust. AI were landing on the same runway as me. I don't know if anyone knows how to fix this issue. If you read the tool tip for cloud smoothing in ASE it will tell you "may experience wind inconsistence at destination", now go figure. I never use ASE standard mode, since it causes terrible stutters on my rig. For the time being I rely on the METAR forecast at destination and thats it, not what I want but seems to work 90% of the time. Not a good answer Bob, but that just where I am today. Bob

When in DWC mode, as you know the weather is set globally. That means the winds at destination are constantly updated to the current surface winds of the station closest to the aicraft coordinates. That's why when we usually go get the ATIS (usually before ~50nm out) it's wrong. All ATC programs I know of read the fs destination weather to report the ATIS. And at the moment we get it (in DWC mode always) it is expected to be wrong (if it is correct then this might be by pure lack). ASE on the other hand gives a chance to ATC programs to get the "real" destination weather conditions indireclty (through windows messaging). AFAIK, only Pete has taken advantage of this (the infamous USEAseWeather option that is on by default when DWC is on). AFAIK only RC uses FSUIPC to get the destination weatherBut there is another problem there: AI aircraft. Even though, RC may report a correct ATIS, the true winds at destination are not set yet to match the ASE destination metar (they will be eventually as we get closer). RC may decide on the active runway soon enough by observing the AI and the runway we may get will possibly be wrong.Pete has explained all this much better than I do:http://forum.simflig...post__p__404290All the above are the reasons I always use force weather to destination when DWC is on. This way the weather at destination is set early enough to allow both AI and ATIS reporting programs to use "real" conditions. It is a good compromise given the advantages of DWC and I think it should always be checked when DWC is on and a flight plan is set. Some inconistencies may persist in cases of variable winds at destination, that's why now the team is investigating the LockWind option as you know. Some other problems may exist with ATC programs such as VoxATC, that calculate the active runway based on destination weather directly before the TOD. And this may be prior to the 80nm threshold ASE uses for forcing the destination weather, leading to incosistencies. Kostas

BobI switched to the Standard Depiction Mode with Local Range Suppression unchecked for the last two flights. The destination weather seems to be okay. ATIS and 122.025 agree all the way to shut down at the gate. I have no noticeable stutters; however, on the last flight the top fourth of the screen has intermitent flashes at higher altitudes. The flashes were the reason I went with DWC. I read someplace on this forum that DWC or Smooth Cloud Transition was a way to eliminate the flashes. I think I just need to keep on trying more flights with different options.Thank youMichael CubineKostasI think I will try DWC with force weather to destination on a flight tommorow. I am going to now bed now.Thank youMichael CubineJim I will reply to your post tommorow. I am going to bed now.Michael Cubine

JimI have only had ASE for 7 days. See http://forum.avsim.net/topic/334869-ase-sp1/. I am trying a flight from KTPA to KJFK in DWC mode with force weather to destination enabled.If this dose not work I will probably go back to the Standard Mode and suffer with the occasional and very short flashes. The flashes are not really that bothersome since it is only the top fourth of the screen at high altitudes and I am either looking at the instrument panel or doing what I am doing right now on a Dell XPS laptop. In answer to your questions:1. What mode and what part of the report did you need for the screenshots.2.The haze is back. And I have always had it unless it was disabled or I was in the Smooth Cloud mode like KORD-KTPA.3.I have no AI traffic except for FSX default and I am not familiar with what you are writing.4.Okay.I will let you know how the current flight turns out.Thank youMichael Cubine

JimI have completed three flights with ASE in the DWC Mode and Force to Destination enabled. I am doing a EDDF-KLAX right now. Due to Kostas's post I now understand ASE and ATIS a little better. The first several initial ATIS reports will be incorrect but ATIS will eventually come around to 122.025 before final approach. And on the ground all three will agree. Shift + Z, 122.025, and ATIS. And they will agree with what was reported in destination metar at departure within 5-10 degree difference. Close enough for government work, I am going to use the info on 122.025 to setup a STAR, approach, and landing and just ignore everything else. Might run into a couple of planes in the air or on the ground. I just set FSX to allow collisons with no bad effects. Not realistic but then neither is FSX weather. The whole FSX deal is just pretend anyway.Thank youMichael Cubine

JimI have completed three flights with ASE in the DWC Mode and Force to Destination enabled. I am doing a EDDF-KLAX right now. Due to Kostas's post I now understand ASE and ATIS a little better. The first several initial ATIS reports will be incorrect but ATIS will eventually come around to 122.025 before final approach. And on the ground all three will agree. Shift + Z, 122.025, and ATIS. And they will agree with what was reported in destination metar at departure within 5-10 degree difference. Close enough for government work, I am going to use the info on 122.025 to setup a STAR, approach, and landing and just ignore everything else. Might run into a couple of planes in the air or on the ground. I just set FSX to allow collisons with no bad effects. Not realistic but then neither is FSX weather. The whole FSX deal is just pretend anyway.Thank youMichael Cubine

Michael,Read the 3 pages of this thread. For a start your FSUIPC settings are all wrong, just about. First thing to do is clear everything in FSuipc, and read the following thread.http://forum.avsim.n...ended-settings/

Michael,Read the 3 pages of this thread. For a start your FSUIPC settings are all wrong, just about. First thing to do is clear everything in FSuipc, and read the following thread.http://forum.avsim.n...ended-settings/

nzch2010I just noticed this reply today. It is interesting that I read the above thread when I first switched from ASX to ASE about a month ago and I read it again this morning before I saw your reply. Sometimes I have a problem with ATIS, 122.025, and Shift + Z, and the METAR not agreeing. But what can you do? I have changed quite a few of the FSUIPC settings since that screenshot and FSUIPC.ini file and ASE settings. I am on to an external FPS limiter now - - the standard limiter seemed to screw with ASE and now I am trying an alternative limiter that ******* Bojote provided a link to. FSX is very smooth with this limiter but there are a lot of black screens and task manager use when trying to exit a flight.Michael Cubine

nzch2010I just noticed this reply today. It is interesting that I read the above thread when I first switched from ASX to ASE about a month ago and I read it again this morning before I saw your reply. Sometimes I have a problem with ATIS, 122.025, and Shift + Z, and the METAR not agreeing. But what can you do? I have changed quite a few of the FSUIPC settings since that screenshot and FSUIPC.ini file and ASE settings. I am on to an external FPS limiter now - - the standard limiter seemed to screw with ASE and now I am trying an alternative limiter that ******* Bojote provided a link to. FSX is very smooth with this limiter but there are a lot of black screens and task manager use when trying to exit a flight.Michael Cubine

Hi Michael,Try this (nothing to lose) , remove all tweaks in your FSX cfg EXCEPT highmemfix and see how your system runs. Some of those tweaks I belive are placebo and might help on a low end system, but yours is high end. I runn FSX with only the highmemfix, get no stutters and very fluid.let me know how it goes. Remove the limiter also. CheersJulian

Hi Michael,Try this (nothing to lose) , remove all tweaks in your FSX cfg EXCEPT highmemfix and see how your system runs. Some of those tweaks I belive are placebo and might help on a low end system, but yours is high end. I runn FSX with only the highmemfix, get no stutters and very fluid.let me know how it goes. Remove the limiter also. CheersJulian

JulianWhy would I want to change back to the old FSX.cfg file.The old cfg file has HIGHMEMFIX in it. The reason I submitted the file to ******* Bojote was to see if I liked it any better than my old one and I do. I have made changes to the new cfg file in some areas such as tool tips, shadows on aircraft and ground, level of airline and general aviation traffic. In the cfg file I have cloud draw distace set at 12. If the slider is all the way to the right in FSX Settings it is 8. At one time I had it at 15 and clould density to 13. Anyway it is 12 and 8 now. FSUIPC settings in the screenshot were for the MD-11. Since reading the settings thread I changed the pressure settings on the clouds page to whatever was in the link to Paul Smith's thread. And for flights with CS planes I remove the ckeckmark from suppress turbulence on the winds page. I am using the limter based upon several threads that said it was better to limit FPS thru an external limiter as oppossed to using FSX. The recommendation was to set the external limiter to 30fps and run FSX unlimited. When done with a flight I press Ctrl+C to exit FSX and the computer returns to the desktop with no black screens or task manager use. I had been using the Esc key and clicking on end flight. That when the black screen would appear.I did add UseAseWeather to the FSUIPC.ini file. That whole set of replies about that subject was confusing. It pretty much just looked like a flame war between everyone involved. So I thought I would try it and see what happens. Nothing soo far. Maybe I'll remove.I am doing a KORD-KSFO in a CS 752 on the other computer right now. The plane is really shaking from turbulence. Too bad that can't be done with the MD-11. Earlier today I was reading a post on the 737NGX and the poster said ASE was causing no problems with the NGX. Let's hope that's how it works out.Michael Cubine

JulianWhy would I want to change back to the old FSX.cfg file.The old cfg file has HIGHMEMFIX in it. The reason I submitted the file to ******* Bojote was to see if I liked it any better than my old one and I do. I have made changes to the new cfg file in some areas such as tool tips, shadows on aircraft and ground, level of airline and general aviation traffic. In the cfg file I have cloud draw distace set at 12. If the slider is all the way to the right in FSX Settings it is 8. At one time I had it at 15 and clould density to 13. Anyway it is 12 and 8 now. FSUIPC settings in the screenshot were for the MD-11. Since reading the settings thread I changed the pressure settings on the clouds page to whatever was in the link to Paul Smith's thread. And for flights with CS planes I remove the ckeckmark from suppress turbulence on the winds page. I am using the limter based upon several threads that said it was better to limit FPS thru an external limiter as oppossed to using FSX. The recommendation was to set the external limiter to 30fps and run FSX unlimited. When done with a flight I press Ctrl+C to exit FSX and the computer returns to the desktop with no black screens or task manager use. I had been using the Esc key and clicking on end flight. That when the black screen would appear.I did add UseAseWeather to the FSUIPC.ini file. That whole set of replies about that subject was confusing. It pretty much just looked like a flame war between everyone involved. So I thought I would try it and see what happens. Nothing soo far. Maybe I'll remove.I am doing a KORD-KSFO in a CS 752 on the other computer right now. The plane is really shaking from turbulence. Too bad that can't be done with the MD-11. Earlier today I was reading a post on the 737NGX and the poster said ASE was causing no problems with the NGX. Let's hope that's how it works out.Michael Cubine

Hi Michael,Suggesting the removal of tweaks was just to test really, just to eliminate any thing. You can use whatever tweaks you like, every user/system is different naturaly. Have you put UIAutomationCore.dll in your FSX root dir ? That fixes menu crashes.Also, the post about the NGX was not about the NGX, how can it when it is not realesed, unless it was from one of the tech team. You have me baffled on that one.I have posted the settings in a new thread to remove all the clutter, so should be easier to copy and paste. Also mad some very small changes. Paul Smiths initial tweaks were for the concorde, all I have done is made some changes to fix the DWC on large patware planes like PMDG.You say it does not wotk on the MD11 ? does on mine. Also many others have tried it with good results. Make sure you are using the latest version of FSUIPC 4.70+Edit: Remove UseAseWeather to the FSUIPC.ini file if using Radar ContactCheers

Hi Michael,Suggesting the removal of tweaks was just to test really, just to eliminate any thing. You can use whatever tweaks you like, every user/system is different naturaly. Have you put UIAutomationCore.dll in your FSX root dir ? That fixes menu crashes.Also, the post about the NGX was not about the NGX, how can it when it is not realesed, unless it was from one of the tech team. You have me baffled on that one.I have posted the settings in a new thread to remove all the clutter, so should be easier to copy and paste. Also mad some very small changes. Paul Smiths initial tweaks were for the concorde, all I have done is made some changes to fix the DWC on large patware planes like PMDG.You say it does not wotk on the MD11 ? does on mine. Also many others have tried it with good results. Make sure you are using the latest version of FSUIPC 4.70+Edit: Remove UseAseWeather to the FSUIPC.ini file if using Radar ContactCheers

JulianI have UIAutomation.dll in the FSX root folder. This is the NGX + ASE thread. It is the sixth reply.http://forum.avsim.net/topic/337154-ngx-ase/. That was yestersay morning that I read that thread but it looks like Tabs shot that down. Back to square one. The screenshot settings for FSUIPC in this thread are for the MD-11 and they work fine. I was commenting that it was too bad that turbulence had to be checked. Unchecking turbulence really brought the CS planes alive. I have the lastest version of FSUIPC which I downloaded and installed around May 15, 2011. I don't use Radar Contact but I did remove UseAseWeather from the ini file.On the fight that I mentioned above from KORD to KSFO the last metar I got on 122.025 had QNH rather than an altimeter setting. Once I landed I refreshed ASE and the briefing for KSFO showed a Q setting also. The real world METAR was still an altimeter setting. What going go wrong next?I have some questions about the FSUIPC.ini settings that you show. But I will save those for when I can get at the ini file. I fly in the full screen mode and I am doing a EDDF-KDFW flight right now.Take care.Michael Cubine

JulianI have UIAutomation.dll in the FSX root folder. This is the NGX + ASE thread. It is the sixth reply.http://forum.avsim.net/topic/337154-ngx-ase/. That was yestersay morning that I read that thread but it looks like Tabs shot that down. Back to square one. The screenshot settings for FSUIPC in this thread are for the MD-11 and they work fine. I was commenting that it was too bad that turbulence had to be checked. Unchecking turbulence really brought the CS planes alive. I have the lastest version of FSUIPC which I downloaded and installed around May 15, 2011. I don't use Radar Contact but I did remove UseAseWeather from the ini file.On the fight that I mentioned above from KORD to KSFO the last metar I got on 122.025 had QNH rather than an altimeter setting. Once I landed I refreshed ASE and the briefing for KSFO showed a Q setting also. The real world METAR was still an altimeter setting. What going go wrong next?I have some questions about the FSUIPC.ini settings that you show. But I will save those for when I can get at the ini file. I fly in the full screen mode and I am doing a EDDF-KDFW flight right now.Take care.Michael Cubine

Hi Michael,I know the post you mean, that post was very ambigous, could have meant anything. If you read further down, Ryan is going to test the NGX with those settings, he had not done so at time of writing his initial comment.Sometimes you cannot win with FSX, what might work for one aircraft, like CS, may not work for another PMDG. Jim's comment in the NGX thread is spot on when he basicly says everybody's needs are different. Let me know if I can be of further help. I am no einstein tho.CheersJulian