Hello All,I was wondering if you could provide me a little help. I have ActiveSky 6 with the SU4 service pack. I've got it setup in the "WideFS" configuration. And I need a little help.This past week, I was forced to rebuild my secondary computer (aka my WideFS computer) from the ground up due to a hard disk crash. Part of that rebuild included setting up WideFS and reinstalling ActiveSky. No worries there.But I'm not entirely convinced that my ActiveSky Graphics and the submittal process is working like it's supposed to, and I was wondering if you could give me a little info on the underlying implementation.When I make my Quick Selections and press the "Send to FS" button, I see a lot of disk activity on my secondary computer, but very little (almost none) network traffic between the secondary and the primary computer (the one with FS9 on it).How does the submittal process work? Are all the textures pre-installed on the primary computer or does the secondary computer transfer a set of textures over to the primary computer when you make the submittal? Based on the disk and network activity, I'm not convinced that my primary comptuer is picking up the graphics changes.Any insight would be greatly appreciated.Thanks,Tom

Maybe I should provide a little more info that might be relevant.I followed the WideFS installation instructions that were provided with the install package. This means that I have a copy of FS9 installed on the WideFS computer. When I "Browsed to the FS9 folder" during the installation wizard, I browsed to the local installation on the secondary computer computer. At the end of the installation, I mapped a drive from the primary computer, navigated to the AS6 installation on the secondary comptuer and ran the ActiveRadarConnector.exe on the primary.The weather does work. ASV6 does have control of the weather on my primary computer.

Hi Tom,"This means that I have a copy of FS9 installed on the WideFS computer. "Technically, in our experience, this is not the ideal situtation. FS9 should be installed only on the "FS9 computer" aka. Wideserver machine. All external add-ons run on the WideFS/Wideclient machine.In your case, with ASv6 and FS9 on the same machine, ASv6/ASG by default picks up the local FS9 installation and copies textures there. Since you're not actually running that FS9 installation, you never see the texture updates. In addition, ASv6 is looking at the wrong installation when updating FS weather station files, so additional psuedo stations and increased coverage will not be available on the actual in-use FS9 install.The easy fix to all this is:1) Edit your ASv6.ini (modulesASv6) to point FS9Path and PersonalAppDataFolder to the correct network path locations for FS9 and Documents and SettingsusernameApplication Data on the other machine.2) Edit your ASG.ini (modulesASGraphics) to point FS9Folder to the correct network path location for FS9.This requires that you setup two shares on the FS9 machine. One for the FS9 base folder and one for the Documents and SettingsusernameApplication Data folder. Remember to set both shares for "allow network users to change my files". By default the share names will be "Flight Simulator 9" and "Application Data". So in your .ini files you will be using FSPCnameFlight Simulator 9 and FSPCnameApplication Data.One last important bit: To get ActiveRadar to work in this configuration properly, you'll need to also create a share on the WideFS/client machine for the ASv6 folder (again, allow network users to change my files), then run the ActiveRadarConnector application FROM the FS PC, using windows explorer to browse through the ASv6 network share (then follow the default prompts). For more information on this check out the readme.txt and activeradarconnector.txt files. Let me know how it goes!Best,

Oh my! What a difference!! I can say, without a doubt, it's working. And it now makes me think I've had this goofed up all along, even with the old installation.Being that you're one of the AS team, can I pass along how I got this way? In your installation wizard, somewhere along the way, it asks you to Browse to the FS9 folder with the caveat that for WideFS users, don't browse to the remote FS9 installation. I interpreted that to mean only one thing... the FS9 folder on my local machine. My next logical step was to install FS9 on the WideFS machine and point AS6 to it instead. Obviously, I goofed. It's now working like it's supposed to, but if I could pass feedback to you, it would be to perhaps clarify the installation steps a little better. Specifically, mention that for the WideFS installation, you need not browse to an FS9 folder, but to another directory. (Or something to that effect.)Thank you so much for your help. It's working like a champ now!Tom