Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Getting ASV new version to detect FSX

Featured Replies

  • Author

As requested I have emailed you a copy of the FSUIPC Log. Downloaded the new version and same result. ASv6.5 will not write weather to FSX.Regards

  • Replies 55
  • Views 4.7k
  • Created
  • Last Reply

Top Posters In This Topic

  • Commercial Member

Hi,Didn't receive a log but we have been experiencing some e-mail problems (we're indeed working on it). Please post it here instead for quickest service. Thanks!

Damian Clark
HiFi  Simulation Technologies

  • Author

Here ya go. FSUIPC actually generated two logs but the other was 96KB didn't fancy posting that on here. ********* FSUIPC4, Version 4.02 by Pete Dowson *********User Name=""User Addr=""FSUIPC not user registeredWIDEFS not user registered, or expiredRunning inside FSXModule base=61000000LogOptions=00000001DebugStatus=0 5625 System time = 00:30:19 5625 FLT UNC path = "C:Documents and SettingsJason ShephardMy DocumentsFlight Simulator X Files" 5625 FS UNC path = "F:Program FilesMicrosoft GamesMicrosoft Flight Simulator X" 7953 SimConnect_Open succeeded: proceeding to initialise interface! 7953 FSUIPC Menu entry added 17203 Running in "Microsoft Flight Simulator X", Version: 10.0.60905.0 (SimConnect: 2.0.60905.0) 226391 F:Program FilesMicrosoft GamesMicrosoft Flight Simulator XSimObjectsAirplanesAirbus_A321Airbus_A321.AIR 226391 c:documents and settingsjason shephardmy documentsflight simulator x filesA321 KSEA Cold & Dark.FLT 378453 C:Documents and SettingsJason ShephardApplication DataMicrosoftFSXPrevious flight.FLT 539203 AppKey="9G9LCNT2MDUY" 555735 AppKey="9G9LCNT2MDUY" 585875 AppKey="9G9LCNT2MDUY" 592016 AppKey="9G9LCNT2MDUY" 605453 AppKey="9G9LCNT2MDUY" 619328 AppKey="9G9LCNT2MDUY" 664250 AppKey="9G9LCNT2MDUY" 670235 AppKey="9G9LCNT2MDUY" 677328 AppKey="9G9LCNT2MDUY" 682453 AppKey="9G9LCNT2MDUY" 688485 AppKey="9G9LCNT2MDUY" 700500 AppKey="9G9LCNT2MDUY" 706703 AppKey="9G9LCNT2MDUY" 712828 AppKey="9G9LCNT2MDUY" 718797 AppKey="9G9LCNT2MDUY" 724953 AppKey="9G9LCNT2MDUY" 731078 AppKey="9G9LCNT2MDUY" 737188 AppKey="9G9LCNT2MDUY" 752110 AppKey="9G9LCNT2MDUY" 757188 AppKey="9G9LCNT2MDUY" 760078 READ0 0020, 4 bytes: 00 00 00 00 .... 760078 READ0 31E4, 4 bytes: 00 00 00 00 .... 760078 READ0 0574, 4 bytes: 00 00 00 00 .... 760078 WRITE0 2DE0, 8 bytes: 00 00 00 00 00 00 34 40 ......4@ 760078 WRITE0 2DE8, 8 bytes: 00 00 00 00 00 00 28 40 ......(@ 760078 WRITE0 3128, 4 bytes: 08 01 00 00 .... 760078 WRITE0 312C, 4 bytes: 08 01 00 00 .... 760078 WRITE0 3127, 1 bytes: FF . 760078 READ0 0840, 2 bytes: 00 00 .. 762078 READ0 0020, 4 bytes: 00 00 00 00 .... 762078 READ0 31E4, 4 bytes: 00 00 00 00 .... 762078 READ0 0574, 4 bytes: 00 00 00 00 .... 762078 WRITE0 2DE0, 8 bytes: 00 00 00 00 00 00 34 40 ......4@ 762078 WRITE0 2DE8, 8 bytes: 00 00 00 00 00 00 28 40 ......(@ 762078 WRITE0 3128, 4 bytes: 08 01 00 00 .... 762078 WRITE0 312C, 4 bytes: 08 01 00 00 .... 762078 WRITE0 3127, 1 bytes: FF . 762078 READ0 0840, 2 bytes: 00 00 .. 762266 READ0 F000, 2 bytes: 28 00 (. 762266 READ0 F004, 2 bytes: 00 00 .. 762266 WRITE0 8001, 14 bytes: 39 47 39 4C 43 4E 54 32 4D 44 55 59 00 00 9G9LCNT2MDUY.. 762266 AppKey="9G9LCNT2MDUY" 762266 READ0 0564, 4 bytes: 00 00 00 00 .... 762266 READ0 3364, 1 bytes: FF . 762266 READ0 056C, 4 bytes: 00 00 00 00 .... 762266 READ0 02A0, 2 bytes: 00 00 .. 762266 READ0 034E, 2 bytes: 00 00 .. 762266 READ0 3118, 2 bytes: 00 00 .. 762266 READ0 0574, 4 bytes: 00 00 00 00 .... 762266 READ0 0238, 3 bytes: 00 00 00 ... 762266 READ0 02B4, 4 bytes: 00 00 00 00 .... 762266 READ0 3364, 1 bytes: FF . 762266 READ0 3364, 1 bytes: FF . 762282 READ0 3364, 1 bytes: FF .[Log closed by user request, and continued in new file] 762922 System time = 00:42:56 762922 *** FSUIPC log file being closedMemory managed: 2 Allocs, 1 Freed********* FSUIPC Log file closed ***********Regards

  • Commercial Member

Hi Jason,Thanks...It appears it has to do with the "FS ready status" offset 3364. This has changed in FSX and apparently is causing problems for us...I am investigating in depth now but in the mean time you may wish to try default AS options and/or toggle the "ignore FS location until ready" option. Also make sure you are not starting paused and using the "unpause on ready status" option.Best,

Damian Clark
HiFi  Simulation Technologies

Hi Damian,I did as you suggested. I tried it with and without "Ignore FS location..." and no change. Other than AS selected DGTK as the default station instead of KSEA. I did see a message about "FS Busy..." while FS loaded, whether that makes any difference or not. I made sure that I was not starting paused and not using "Unpause on ready status". Actually, I tried it with that last option on and off and there was no change.Thank you for working on this. I miss my ActiveSky.John

  • Commercial Member

Hi John, Jason, all,I've been experimenting a bit and unfortunately cannot duplicate this scenario at all in any configuration or startup order thus far.There are now 2 reports of this with many others running without problems, which indicates that there is something specific probably with configurations and options or perhaps the order of doing things. Have you attempted normal default AS options just to attempt to isolate?It is also possible there is some kind of interaction going on with other add-ons. Perhaps also an obscure FSUIPC issue. It needs some further thought, testing and isolation to get a handle on.Please list the order you are starting things up, startup location, and any other information you think might be helpful... Also, e-mail is working fine again, so please try enabling weather, reads and writes logging options in FSUIPC while duplicating the scenario (making sure ASv6.5 gets loaded and connects) and send me any log files (they will probably be big). My email is damainc AT hifisim.com (replace " AT " with "@").Thank you for your assistance and patience in this matter, and please accept our apologies and regrets that things are not already working good for you. We'll work hard to make sure we get you up and running ASAP.Best,

Damian Clark
HiFi  Simulation Technologies

Hi Jason,Is this a netowrk installation or a single computer install?Thanks,Jimhttp://www.hifisim.com/Active Sky V6 Development Team Active Sky V6 Proud SupporterHiFi Beta TeamRadar Contact Supporter: http://www.jdtllc.com/AirSource Member: http://www.air-source.us/FSEconomy Member:http://www.fseconomy.com/

  • Author

This i single computer installation. Will try the things you suggested and get back to asap.Regards

  • Author

Hi Damien Have sent you email with fsuipc logs attached along with exactly how I run fsx with ASv6.5.Regards

Hi,and first thank you so much for an outstanding add-on!I have the same problem as Jason reported. I did try using it with the previous version of ASV6 in FSX without a problem with FSUIPC 4.01. Fsx loaded the weather. I had only a drop of the FPS when ASV6 was writing the weather in FSX. Since I updated to ASV6.5 it download the weather proced but never write it in the FSX weather stations even if it indicate that Fs is active. My OS is a french version and FSX also.I hope that can help you tracking the problem.Christian from Paris

  • Commercial Member

Hi all,While we continue to work on this issue, it occured to me that this MAY all be due to firewall security issues. Since SimConnect uses TCP/IP to talk with its clients (such as FSUIPC) it is certainly a possibility.The mention of this only occuring when updating to 6.5 goes along with this theory. Most firewall software is setup to be application-specific. When updating, the exe changes, and the application is no longer recognized or trusted. If those of you having this issue could check your firewall configuration (and perhaps disable it to isolate) and also let us know what firewall/security software you are running it would be much appreciated!Thanks for your assistance and patience while we work this out...

Damian Clark
HiFi  Simulation Technologies

Hi Damian,First, thanks for a great product and a first-class support team.I had the same problem as Jason until I changed the path in asv6.ini to point to the FSX folder. The first time I ran asv6 after making this change, it gave me a pop-up saying that it couldn't find my flight sim folder and asking me to browse to the correct location, which I did. Since then, everything has worked as it should.Dugald

Hi Damian,Thx for your quick aswer. I don't use any firewall. I am on intranet behind a Linksys router and connect to Vatsim with SB3 or FSInn without any problem. I even disabled the XP SP2 internal firewall which I don't need. My router does all the securities needed and is set to forward few ports for the Vatsim and clients connections.Thanks for all your hard work.Chris

  • Author

I have Norton Internet Security which includes Norton Antivirus 2007 and Norton Systemworks which I have fully disabled but still ASv6.5 will not connect to FSX. :-(regards

I've been playing around with different things and no success. I am also using a Linksys router, which is probably why AS6.5 popped up initially with a message about "We have detected you are on a network.....".I use Windows XP SP2 firewall which I have disabled.I use Norton AV which I disable every time I use FS.I removed AS6.ini completely forcing AS6.5 to reinitialize.I reverted to default options, which I was using before except I had disabled the thunder sound at start up.I have tried it offline as well as online and with "Ignore FS location until ready" disabled and enabled.My starting location was KDFW. I did a flightplan KDFW - > KAUS and loaded it in AS6.5. It processed it fine but did not send the weather to FSX.I did get the message the first time I entered my FS path in AS6.ini asking me to point to it again. I did but that hasn't resolve my problem.I've loaded AS6.5 first then FSX, and also in reverse order. No effect.I have a registered version of FSUIPC4.DLL (version 4.02). I have tried AS6.5 with it and the unregistered version (temporarily removing the key file). No difference.While none of those have resolved my problem, and it appears the problem is system-specific, I will keep trying different things to see if I can find out what the problem is. I don't know the first thing about how FSUIPC works but from what I am hearing is that something is interfering with the communication between it and AS6.5,Cover me. I'm going back in.John:-jumpy

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.