Hi JD et al,I'm now running the latest ASE SP2 on a wide-client PC with DWC on and the latest FSUIPC with the "activesky" edit in the ini file. The funny thing is, RC now works fine even with ASE in DWC mode, up to a point. I'm now getting a bad RC lag (pause) right when OTTO goes to contact weather @ 40nm out in the approach - it takes forever for RC to switch between controllers for the rest of the approach. This includes contacting approach, tower, ground, etc..What's even more wierd, it now does this regardless if I have DWC enabled in ASE or not. I have tried toggling "force destination weather", ASE priority, disabling extra stations, etc, to no avail.Is it possible that I have some buggered-up wav files or something? RC has been installed since I rebuilt the OS with Win7 64bit early in 2010 and no other issues are noted with the PC, OS, or other FS Addons including FSFK, ASE, AES-Remote, TopCat, etc... No issues in the Win7 event log either. I regularly run the makerunways utility on the FSX host and update the client PC.Why am I getting pauses when switcn between controllers starting at the 40nm crossing, and onward?

Hi JD et al,I'm now running the latest AES SP2 on a wide-client PC with DWC on and the latest FSUIPC with the "activesky" edit in the ini file. The funny thing is, RC now works fine even with AES in DWC mode, up to a point. I'm now getting a bad RC lag (pause) right when OTTO goes to contact weather @ 40nm out in the approach - it takes forever for RC to switch between controllers for the rest of the approach. This includes contacting approach, tower, ground, etc..What's even more wierd, it now does this regardless if I have DWC enabled in AES or not. I have tried toggling "force destination weather", AES priority, disabling extra stations, etc, to no avail.Is it possible that I have some buggered-up wav files or something? RC has been installed since I rebuilt the OS with Win7 64bit early in 2010 and no other issues are noted with the PC, OS, or other FS Addons including FSFK, AES, ASE-Remote, TopCat, etc... No issues in the Win7 event log either. I regularly run the makerunways utility on the FSX host and update the client PC.Why am I getting pauses when switcn between controllers starting at the 40nm crossing, and onward?

i don't recall otto getting the weather at 40 miles out. maybe at 70. is that where it's happening? do you have pre-recorded chatter clicked? if so, uncheck it, and try it again. and this time, make a log, instructions pinned to the top of the forumjd

If you can in RC options turn of Display Text since controller actvity becomes more dense.If you are using UT2 AI should be set to spawn at 40 nm so RC can see it but that also increases AI rendering loads.With the various loads on the CPU and the longer content of things like ATIS and weather, it can take RC longer to compile and speak this audio.Another issue is that your scenery complexity increases as you approach destination. If you are also using a complex aircraft this also increases CPU load. On the plus side of Win 7 complex calculations in your CPU can be handed off to your graphics processor (GPU) if available. Remember that FS9 and FSX do most of their object rendering in the main CPU, not the graphics GPU. If the only thing as changed is your installing ASE SP2 I'd check the service notes for best performance.I'm not sure running ASE on a client PC to an FSX host is the best way to go as it makes extensive use of SimConnect. If RC is also on your client in busy areas your slow down could be on your network connection. See if the SP2 release notes have anything to say about running on a client.Try running two tests:1. Fly without ASE running and then try with different selections of the new options.2. Fly with AI set to 0 percent.See if this narrows down your issues.