Damian, Three ideas to throw into the mix for future versions if you think they are worth while: (Based on version my 1.15)1. I start ActiveSky wxRE from within a "programs" section of FSUIPC.ini. I have noticed that occasionally I end up with two instances of ActiveSky wxRE running in the computer(my fault I know but still easy to do and I may not see the extra ActiveSky wxRE form because it's hidden beneath full screen FS2002!). Both instances don't cause a crash but they slow FS down. Shouldn't your program check to see if ActiveSky wxRE is already running before launching?2. I run ActiveSky wxRE on my second monitor. Therefore, I'd prefer that the screen position of ActiveSky wxRE is preserved from run to run. Now each time, I have to drag Active Sky wxRE's form over to the second monitor. I think this is just a check mark in the VB code Form? (You could make this an option in ActiveSky wxRE ini if you think no one else would make use of this feature).3. I have noticed that sometimes ActiveSky wxRE updates just as I am lined up on final. How about an option that disables updates if you are say 25 miles from destination. If the update occurs when I am on final, I notice that FS stutters and the FPS goes way down.Great program which is priced right and well supported. It's so good I have yet to read the documentation which is a testament to the programs worth! Thank you!Larry J

Larry,These are all good ideas.#3. With V1.15 try to uncheck "Update METAR on new Station" and see if that helps. Many, many airports are the station and that is why you are getting that final update.I think I can safely say that this will be changed in the next update.Hope this helps,Jim

>1. I start ActiveSky wxRE from within a "programs" section >of FSUIPC.ini. I have noticed that occasionally I end up >with two instances of ActiveSky wxRE running in the >computer(my fault I know but still easy to do and I may not >see the extra ActiveSky wxRE form because it's hidden >beneath full screen FS2002!). Both instances don't cause a >crash but they slow FS down. Shouldn't your program check >to see if ActiveSky wxRE is already running before >launching? Hello Larry! As to question #1, there is an option in FSUIPC's "Run Options" application, which lets you have FSUIPC detect if the application is running already, and if so, it won't start a second occurance.Just load the "Run Options" application, double-click on the application you want to have FSUIPC check before starting (presumably ActiveSky wxRE), and check the "Detect if app is running" checkbox.Personally, while I think this is a great feature of FSUIPC, I rarely have it start any of my add-ons with FS. Instead, I have placed shortcuts to all of my FS add-ons in a "Checklist" folder on my desktop so I can easily start them (manually) as required. My reason is mainly to conserve system resources during the flight-planning stage when I don't require accurate weather or a link to SB (via AIBridge), and only need to program my FMS and decide which DP's/STAR's to use. Once planning is completed and I'm ready for departure, I will start a "Multiplayer" connection in FS and start all of the add-ons.Hope this helps!~ Andy SutterMA825/KSFO (Meridian VA)kZAU ARTCC

Hi Larry,Thanks for the feedback..#3 is already done and in 1.6 via option to disabled when within force (after the final force update).#1 and 2 I will work on! Thanks..-Damian[table border=0" cellspacing="30" cellpadding="0][tr][td align = "left"]Damian ClarkHiFi Simulation SoftwareDeveloper of ActiveSkyThe next-generation weather environment simulation for FS2002!http://hifi.avsim.net/activesky[/td][td]http://hifi.avsim.net/activesky/images/wxrebeta.jpg][/td][/tr][/table://http://hifi.avsim.net/activesky/ima...][/tr][/table

Damian,Below is based on Visual C dot NET. I think VB and VC.NET are very similar these days. (Maybe not in which case, please disreguard)To save the Form Location, just preserve the Form1.Location property upon exit, This property looks to me like a Point, ie something like Point FormStartLocation = new Point();in your wxre.ini perhaps perhaps similar toStartLocationX = Form1.Location.X;StartLocationY = Form1.Location.Y;When wxRE reads the ini, plug the two values back into FormLocation which should be something similar to Form1.Location = New Point (StartX, StartY); // where StartX + Y are the integers read from the ini file.I think Form1.StartPosition would have to be set to "Manual"To prevent a second instance of wxRE from running, look at http://support.microsoft.com/default.aspx?...B;en-us;q185730in the M$ Knowledge Base Article 185730.(Their method seemed overly complicated to me. I thought you could just use GetProcessByName("wxRE") and count the number of wxRE's returned. If more than one, don't launch a second copy.)All this just FYI. All my programming expertise (!.!) was learned the hard way, that is by making lots of mistakes so look on this skeptically!Thanks for addressing my concerns.Larry

Thank you Larry, for naming the "stutters" when AS updating the weather.Seems there are more people who have to deal with this same issue!vortovor