Hello All -I recently uncovered what most of you discovered regarding the ASE & RC issue of slowness. So I upgraded FSUIPC to 4.60 and the latest of ASE (B642). I'm still experiencing "Slow Response" from RC4. I was confused about the pinned post on the forum regarding this. So I add the lineASEweather=Yes to the general section of the fsuipc4.ini fileWhat other settings does anyone suggest on the ASE portion of it? I didn't change much on ASE, so I'm sure its something I missed there.Thanks,Rob Sciarrino

I recently uncovered what most of you discovered regarding the ASE & RC issue of slowness.

As far as I am aware this has only been experienced with ASE in "DWC" (Direct Weather Control) modes. I think it must be due to ASE's constant control of the weather in DWC mode, rather than the otherwise periodic updates.

So I upgraded FSUIPC to 4.60 and the latest of ASE (B642).

I'm glad you upgraded to 4.60 because nothing earlier than that is currently supported on FSX. However, it contains no facilities related to the ASE update. For that you need the latest update for FSUIPC4 too, as in fact pointed out in the ASE release details. Currently that's 4.645 but version 4.647 will be released later today, and hopefully by the end of this month a complete new user release (4.65) will be published, superseding 4.60 as well.

So I add the lineASEweather=Yes to the general section of the fsuipc4.ini file

That line does nothing in 4.60 because 4.60 pre-dates the addition of the ASE facilities by at least 6 months. In any case you do not need to add any line. It is automatically assumed if you use DWC mode in ASE. In other words, the relevant versions of FSUIPC will automatically use ASE weather if ASE is running in DWC mode, but not otherwise (it is not needed if you don't use DWC mode). Either way I don't think it has much to do with any RC response times, only to do with RC reporting the correct weather.RegardsPete

That line does nothing in 4.60 because 4.60 pre-dates the addition of the ASE facilities by at least 6 months. In any case you do not need to add any line. It is automatically assumed if you use DWC mode in ASE. In other words, the relevant versions of FSUIPC will automatically use ASE weather if ASE is running in DWC mode, but not otherwise (it is not needed if you don't use DWC mode). Either way I don't think it has much to do with any RC response times, only to do with RC reporting the correct weather.RegardsPete

This is the point that I've been trying to get across to all those involved with this recent fix, but I must not be explaining my observations clearly enough. I understand that if we are using ASEsp2 with the latest FSUIPC, it will automatically call data from ASEsp2 (when detected in DWC mode) without the new UseASEweather switch in the INI file. I can see statements to this affect in the WideClient and FSUIPC logs. Regardless, before and now, if ASE is used in DWC (Global) mode, RC get the 'slows'. I suspect that you are correct in your assestment, it being a side-effect of constant updates from ASE weather.But what I am failing to get across to those involved, is the fact that with the new UseASEweather switch set to 'yes' (or removed entirely), and ASEsp2 in 'Standard' mode, the same bad affect is now duplicated, RC gets the 'slows' throughout the approach and landing. Again, the 'slows' in RC is now happening in non-DWC mode.I completely understand that this was implemented to make calls for more accurate destination weather to anticpate the landing winds and runway in use. I myself have had the missery of plenty of 12K crossings issued for a near-side approaches, only to come head-long into AI and frequent go-arounds. The only way I have been able to now get rid of the RC 'slows' is if I force ASEsp2 to 'Standard' mode and set the UseASEweather switch to 'No'. Removeing it from FSUIPC.ini now has the same affect and the 'slows' are still noted in RC - it must be set to 'No'.My point is, if the 'slows' issue has now been fully replicated using completely different mode (Standard) in ASEsp2, then perhaps some reverse engineering is possible to figure out what exactly was added/changed so that it can be reversed for both DWC, and now Standard mode. I can't stand the new sky-flashing and stutter-fest now associated with the new Standard mode in ASEsp2 and I think DWC mode looks and acts much better - but at the same time, I am now torn between a good looking sky using ASEsp2 DWC mode, and a proper non-slow RC controller issuing timely commands on approach and landing. This not an easy choice for a loyal customer of all three products going on 10 years now.

But what I am failing to get across to those involved, is the fact that with the new UseASEweather switch set to 'yes' (or removed entirely), and ASEsp2 in 'Standard' mode ...

Setting it to "Yes" forces FSUIPC to get weather from ASE even in standard mode. However, omitting it or setting it to 'No' will make FSUIPC revert to getting weather from SimConnect in any ASE mode other than DWC. The default (no parameter) is to get weather from ASE in DWC mode and SimConnect otherwise, because this is the only way to get the correct weather.

... the same bad affect is now duplicated, RC gets the 'slows' throughout the approach and landing. Again, the 'slows' in RC is now happening in non-DWC mode.

I measure a maximum of 2-3 seconds here, consistently, in DWC mode. As I've repeatedly told you, you have something else going on in your system.

I completely understand that this was implemented to make calls for more accurate destination weather to anticpate the landing winds and runway in use.

No, that is completely wrong too! I've explained this to you before but you appear to have ignored me. The main use of the facilities being used by RC are to provide the ATIS. For the runway to be used it is almost always going to be dictated by the runways the AI are using, and that is a completely separate matter, unrelated entirely to any weather readings by RC. In rare occasions where there are no AI showing up using runways at the time RC wants to make a decision, it will of course use the METAR wind reports.However, you stated elsewhere that your problems were on final approach, and there is really no way any part of RC is reading METARs and making runway decisions at that stage. You really do need to get your specific problems analysed along a different tack and stop being misled by incorrect assumptions.

The only way I have been able to now get rid of the RC 'slows' is if I force ASEsp2 to 'Standard' mode and set the UseASEweather switch to 'No'. Removeing it from FSUIPC.ini now has the same affect and the 'slows' are still noted in RC - it must be set to 'No'.

This is absolutely not true. If this parameter is omitted, then FSUIPC will ONLY read the ASE weather in DWC mode. The only extra work it will do is ask ASE if it is in DWC mode. If that simple request is causing you grief then there is something seriously wrong with your Windows setup, as it is a simple Windows message sent and received with no waiting at either end, and this inquiry message is only sent once every 12 seconds. The purpose in repeating it is to check that ASE is still running or has started running, and to see if it is in DWC mode or not. This is the only additional action taking place with the UseASEWeather parameter omitted and ASE not in DWC mode. Setting the parameter to "No" merely omits this action too.I would ask you to please refrain from generalising responses to everyone's reports your own specific problems, which are just that. I keep explaining this to you and it is getting tiresome having to repeat it.RegardsPete

Al, I am currently wondering why the couple of messages exchanged between ASE and FSUIPC every 12 seconds or so are apparently causing some delays or stoppages on your system. Do you note this affecting FSX's frame rate? Because those messages are currently exchanged in the main FSX thread. I have developed an update in which FSUIPC's exchanges with ASE are is a separate, independent, thread. Maybe you'd like to try it and see? It makes no difference whatsoever here. http://fsuipc.simflight.com/beta/FSUIPC4648.zipLet me know if it makes any difference on your system, please.Pete

Al, I am currently wondering why the couple of messages exchanged between ASE and FSUIPC every 12 seconds or so are apparently causing some delays or stoppages on your system.Do you note this affecting FSX's frame rate? Because those messages are currently exchanged in the main FSX thread.I have developed an update in which FSUIPC's exchanges with ASE are is a separate, independent, thread. Maybe you'd like to try it and see? It makes no difference whatsoever here.http://fsuipc.simfli.../FSUIPC4648.zipLet me know if it makes any difference on your system, please.Pete

I have downloaded the above beta this morning but can't test it until I get home tonight from work. I've sent a reply to your personal e-mail as well.

Pete,I have had long-time problems with ASE in DWC mode creating the "slows" in RC4.I have the latest ASE update and FSUIPC update (4648).In FSUIPC4.ini under [General]: UseASEweather=Yes When landing on RWY 28 KFAY I am turning off the active when tower gives me clearance to land. I call that the RC "slows".In ASE Standard mode, RC4 is fast on all calls and replys.My only problem with the slows is ASE DWC mode. Most everyone with ASE wants to use DWC mode because it dipicts the best wx.Thanks for working on this ASE/RC4 problem.zach

I have had long-time problems with ASE in DWC mode creating the "slows" in RC4.

I always assumed this must be due to insufficent power for FSX to update weather second by second, almost, as it needs to for DWC, whilst other programs are also trying to run. However, recent evidence seems to point to some critical timing glitch in RC forcing it to ignore confirmations that the weather is readable.

I have the latest ASE update and FSUIPC update (4648).

There is nothing in those to alleviate any delay problems, only to supply correct weather in DWC mode. nothing more, nothing less.

In FSUIPC4.ini under [General]: UseASEweather=Yes

You should really just omit that. There is no need to get ASE weather when ASE is not in DWC mode.

When landing on RWY 28 KFAY I am turning off the active when tower gives me clearance to land. I call that the RC "slows".In ASE Standard mode, RC4 is fast on all calls and replys.

See above.

Thanks for working on this ASE/RC4 problem.

I was only working on getting the correct weather reported in DWC mode. The way it is done is just as efficient as it was before. If there's some glitch in RC then JD needs to look at it. I have supplied extra information to him about this to him and if I can help him by changes to FSUIPC I will, but I don't understand what RC is doing at present. We'll see.RegardsPete