As I posted in another thread, I have been working with the scholarly gentleman, Mr. Pete Dowson, to describe and test the well known issue we call the 'slows'. This is basically where RC menus and controller responses begin to take longer than usual to respond to our user input. This is mostly observed by many of us during approach and landing when using RC and HiFi's ASE, in DWC mode. Mr. Dowson has posted FSUIPC v4.649 Interim on his download forum as a probable fix for this long-standing issue. Testing with all major add-ons including FSXsp2, ASEsp2, RC4.3, Level-D 763, FS2Crew Voice, GEX, UTX, FSFK, RC, ASE, FS Passengers, etc; proved to be just as succesful - no slows. You can really tell it's fixed if near landing, the tower issues winds at about 4nm out and then immediately issues clearance to land by 2 or 3nm out - not during or after touchdown, which is what we call the 'slows'. It is also much cleaner when requesting an ILS approach shortly after the 40nm crossing restriction - no more waiting for menus to get to the ILS request keys.I can personally confirm that today has been the first time I could EVER use ASE in DWC mode with RC and it is now performing as well as it ever did with ASE in Standard mode. This includes running RC and ASE both directly on my FSX PC, and then again on my wide-client PC. Same reasonble response times with RC - no more slows. Please remove the "UseASEWeather=" statement from your FSUIPC.ini file - it's automatic and there is no nead to type it into the file - regardless of the Pinned topic. Also, ensure you have ASEsp2 Build 642 installed.If you have experienced the 'slows' while using RC and ASE in DWC mode in the past, please download Pete's latest FSUIPC beta from his download forum and see if it fixes the issue for you. Please post your finding back in this thread so Pete can monitor the findings directly. Again, this just about solving the 'slows' problem in this thread.On my ASE Options page, General Option tab, I have the following checked:

• Force Destination Wx Zone
• Force High Priority Process
• Automatic Downloads / 20 minutes
• Direct Weather Control
• Depict Hurricanes
• Create Additional Stations
• Enchance Route Coverage
• Dynamic Rate of Change = 10%

On my FSIUPC Settings, I think I was using (checked):

• Wind Smoothing - 2 sec kn/deg
• Smooth only airborne
• Turbulance, Gusts, Variance, all checked
• Pressure and Temp smoothing enabled - defaults (20/100)

Perhaps run a known simulation with a current version of FSUIPC with ASE in DWC mode and validate that you have the 'slows' in RC. Then install 4.649 and determine if the 'slows' are now gone - this would be a positive test scenario.Thanks for your help - I hope the new version works for you as well as it has for me today.

Thanks for working with Pete.There is a release note for this FSUIPC upgrade that applies to network users. This pertains to a wideclient version upgrade as noted:Note for FSUIPC:"29. FSUIPC4 now contains facilities to obtain weather from Active Sky (ASE build 638 or later) in response to weather requests from applications. This is automatically done if FSUIPC detects ASE running locally in DWC (Direct Weather Control) mode, but it can be made to do it even in normal weather modes by adding:UseASEweather=Yesto the [General] section of the FSUIPC4.INI file. Alternatively you can prevent FSUIPC4 using ASE at all by setting this parameter to 'No'.[Note: In version 4.648 the ASE interaction was moved to a separate thread to avoid any possible interference with normal FSUIPC and FSX activities, the, in 4.649, the way certain offsets were updated was changed to more suit what Radar Contact seems to expect when requesting weatrher].If you run ASE on a separate PC then you would need to have WideFS, and run WideClient.exe (version 6.833 or later) there as well for this facility to work. This is the case even if you otherwise have to use for WideFS on that PC."Note for WideClient 6.838:"12. WideClient automatically supports the FSUIPC4 facilities to obtain weather from Active Sky (ASE build 638 or later) in response to weather requests from applications. This applies when you run ASE on a separate PC from FSX. You will need to have WideFS, and run WideClient.exe on the same PC as ASE. This is the case even if you otherwise have to use for WideFS on that PC."--------------------The link to both module updates is here on this page;http://forum.simflight.com/topic/66139-updated-modules/

Just did a test flight with the new version - EDDM EDDF with an A319. All bells and whistles set in ASE.I can report that RC is now extremely responsive and as it should be. However, it seems that the airport weather is not reported correctly. For EDDF, tower told me that winds are calm when in fact they were 17mph - might be that it's a hickup with some of my settings in the FSUIPC.ini - so don't treat that as a bug yet. But apart from this matter, the combo now works flawlessly - and what a difference that makes :-)

To Al and Pete, that is great news, cannot thank you guys enough. And to the team at RC for jumping in with the great support.Will try tommorow (my time) and will report back.CheersJulian

Its very responsive but now the winds are back the way they used to be until your within 20 miles. When requesting ATIS I'm getting winds in excess of 50 knots at the destination. Guess I'll go back to the previous fsuipc version and live with the lag.I just finished reading some other messages from Pete Dowson and now I'm lost. He states he never said to put the parameter UseASEweather=YES in the INI file to use ASE with RC4. http://forum.avsim.net/topic/323219-fsuipc-update/Do we do this or not?I will try again without this parameter and the new beta of FSUIPC. The pinned topic at the top and my browsing of other messages contradicting the pinned topic are making my brain spin.Sean

Its very responsive but now the winds are back the way they used to be until your within 20 miles. When requesting ATIS I'm getting winds in excess of 50 knots at the destination. Guess I'll go back to the previous fsuipc version and live with the lag.

There's absolutely no difference in the weather reception or what is being set. The ONLY difference is the way FSUIPC signals to RC that the weather data ror its ATIS is ready to be read. Previously RC was repeatedly reading the same weather over and over again for anything from 30 seconds to 20 minutes, simply because it didn't recognise the "it's here" indication from FSUIPC, and this distracted it from its other duties causing the apparent slow responses.So, if you are getting different weather it cannot possibly be merely down to updating FSUIPC. FSUIPC has nothing whatsoever to do with setting ASE weather in FSX. You most certainly need to look elsewhere.

I just finished reading some other messages from Pete Dowson and now I'm lost. He states he never said to put the parameter UseASEweather=YES in the INI file to use ASE with RC4.

Correct. That's an option if you want to FORCE FSUIPC to always read ASE weather instead of FSX weather, even when it isn't necessary, as in ASE standard modes. It is documented like that in the release Notes for the updates. I have no idea why folks keep adding an optional and unnecessary parameter, but if you use ASE DWC mode it makes absolutely no difference whatsoever whether you add that line or leave it to default.Pete

Things seem a lot better! :) But i did run into a problem during a flight today. At CRZ FL310 FSX locked up and gave an ATC.DLL as the module causing the crash. Did I miss something?Rob Sciarrino

However, it seems that the airport weather is not reported correctly. For EDDF, tower told me that winds are calm when in fact they were 17mph - might be that it's a hickup with some of my settings in the FSUIPC.ini - so don't treat that as a bug yet.

Nothing in anything FSUIPC or ASE or RC does in relation to all the recent updates has any bearing whatsoever on Tower reports. By the time you are on Tower, the winds being reported should be the local ground ones at the aircraft position, and read from where they are actually stored in normal FSX offsets, not read from ASE at all. If the winds changed that much over the 5-15 miles you were on Tower then either they were gusting quite a bit in any case (a not uncommon phenomenon near the ground), or you had some pretty dramatic dynamics going on in the weather there.RegardsPete

But i did run into a problem during a flight today. At CRZ FL310 FSX locked up and gave an ATC.DLL as the module causing the crash. Did I miss something?

Nothing to do with FSUIPC or ASE or RC. You have a corrupt scenery file by the sound of it. ATC.DLL doesn't come into anything we are doing.Pete

As I posted in another thread, I have been working with the scholarly gentleman, Mr. Pete Dowson, to describe and test the well known issue we call the 'slows'. This is basically where RC menus and controller responses begin to take longer than usual to respond to our user input. This is mostly observed by many of us during approach and landing when using RC and HiFi's ASE, in DWC mode. Mr. Dowson has posted FSUIPC v4.649 Interim on his download forum as a probable fix for this long-standing issue. Testing with all major add-ons including FSXsp2, ASEsp2, RC4.3, Level-D 763, FS2Crew Voice, GEX, UTX, FSFK, RC, ASE, FS Passengers, etc; proved to be just as succesful - no slows. You can really tell it's fixed if near landing, the tower issues winds at about 4nm out and then immediately issues clearance to land by 2 or 3nm out - not during or after touchdown, which is what we call the 'slows'. It is also much cleaner when requesting an ILS approach shortly after the 40nm crossing restriction - no more waiting for menus to get to the ILS request keys.I can personally confirm that today has been the first time I could EVER use ASE in DWC mode with RC and it is now performing as well as it ever did with ASE in Standard mode. This includes running RC and ASE both directly on my FSX PC, and then again on my wide-client PC. Same reasonble response times with RC - no more slows. Please remove the "UseASEWeather=" statement from your FSUIPC.ini file - it's automatic and there is no nead to type it into the file - regardless of the Pinned topic. Also, ensure you have ASEsp2 Build 642 installed.If you have experienced the 'slows' while using RC and ASE in DWC mode in the past, please download Pete's latest FSUIPC beta from his download forum and see if it fixes the issue for you. Please post your finding back in this thread so Pete can monitor the findings directly. Again, this just about solving the 'slows' problem in this thread.On my ASE Options page, General Option tab, I have the following checked:

• Force Destination Wx Zone
• Force High Priority Process
• Automatic Downloads / 20 minutes
• Direct Weather Control
• Depict Hurricanes
• Create Additional Stations
• Enchance Route Coverage
• Dynamic Rate of Change = 10%

On my FSIUPC Settings, I think I was using (checked):

• Wind Smoothing - 2 sec kn/deg
• Smooth only airborne
• Turbulance, Gusts, Variance, all checked
• Pressure and Temp smoothing enabled - defaults (20/100)

Perhaps run a known simulation with a current version of FSUIPC with ASE in DWC mode and validate that you have the 'slows' in RC. Then install 4.649 and determine if the 'slows' are now gone - this would be a positive test scenario.Thanks for your help - I hope the new version works for you as well as it has for me today.

Downloaded FSUIPC 4649. Use ASE in DWC mode. The RC4 "slows" are gone, completely gone! This is the first time I have ever been able to run ASE in DWC mode without the RC4 "slows". I have tried many adjustments and nothing until today has worked. The new FSUIPC download is as good as gold! Thanks for your work. zach

This latest update fixes the "slows" for me as well.

Nothing to do with FSUIPC or ASE or RC. You have a corrupt scenery file by the sound of it. ATC.DLL doesn't come into anything we are doing.Pete

I just copied the FSUIPC. dll over to the modules folder. Should I have done something else? That is the only thing that has changed. Thanks,Rob

I just copied the FSUIPC. dll over to the modules folder. Should I have done something else? That is the only thing that has changed.

Sorry, I've no idea why your system crashed in ATC.DLL. All I am pointing out is that nothing in FSUIPC, RC or ASE has anything whatsoever to do with ATC.DLL. You will need to look elsewhere.RegardsPete

Although I couldn't reproduce it on my system, I found a flaw in the way FSUIPC version 4.649 "fiddles" the weather reading protocol to suit Radar Contact's way of requesting then reading the weather. Basically, there could be some occasions, very timing dependent, where it would read the wrong weather -- possibly the weather from a previous read or that at the aircraft. This is basically occurring because RC seems not to be waiting for the timestamp to be updated.To get around this I've made some further changes. I think I've done these in a way which will be normally just as responsive, but hopefully will also never supply the wrong weather.FSUIPC version 4.651 is now available in place of 4.649, from my Support Forum's Download Links subforum.Note that, to clarify some comments I made earlier in this thread, I don't think this will fix any cases of Tower relaying incorrect wind or QNH data, because by the time you are on Tower I would think that RC would be reading the current at-or-under aircraft weather (from always populated and supplied offset data), not asking for the full METAR as in the ATIS cases. However, I have not actually checked whether RC does what I think it should do, or not.RegardsPete

Pete I want to give you a BIG THANK YOU!!! That fixed the issue of giving the wrong winds at ATIS. This flight went smooth as butter other than one other issue which I believe is a HIFI Sim issue. Soon I'll actually be able to fly with FSX some real flights!!!Once again thanks for your wonderful support.Sean Green

I looked at some ASE logs sent to me by Bob Johnson in regard to some other issues:First, glad that Pete adjusted FSUIPC to 4.651 to correct the ATIS returned to RC. Thanks again to Pete and Al Jordan.I recommend that when operating in DWC (with Global Mode on) that you elect the option to Force Destination Weather Zone On so on approach RC sees the AI operating correctly stabilized for runway assignment. The ASE log shows that METARs sent to FS are interpolated to the locked option. However, it also shows that for those ASE users choosing to download real weather (not archived) ASE periodically gets that weather. When this occurs it appears that the destination weather even in the "locked" zone will change as I interpret the log so be aware that AI might be changing patterns during this period. Depending on your flight duration and landing time this update transition might occur during your approach anytime with the lat 40 nm or fifteen minutes. The ASE log shows the download occurring every thirty minutes with METAR refreshes applied to FS with interpolation.The result is if this update occurs after RC approach assigns a runway you could experience an AI conflict depending on runway layout and properties.Please advise if any conflicts occur at landing time for either situation of using archived weather or continual (periodic) weather updates.Thanks.