Pete Dowson

Well, I installed them, loaded up FSX .... all is fine. FSUIPC's dialogue comes up 100%, no crashes, FS closes down ok. Is there something else I must do to make a failure? On your system I'm sure the bad affects on FSUIPC and on Weather DLL must be down to some corruption of weather data somewhere in the system. It has all the indications of this. Pete

Where have you been these last three years? That was done a soon as the original PMDG 737NGX SDK came out supporting exported data, in FSUIPC version 4.84, July 2012. And the data was extended for the more recent SP1d NGX enhancements -- included in FSUIPC nearly a month ago. You must have an extremely old, completely unsupportable, install of FSUIPC. Please do try to keep up to date! :sad: Pete

Looks very smart! No, no problems with violating anything at all! ;-) Best wishes Pete

Sorry, I don't know. I could research it on-line when and if I get time, but then so could you. I have no idea why the name I use, "\\.\WCEUSBSH001" worked nor how it is derived -- that, as it says, was from another user. In my case the "active link" was a Garmin GPS driver, installed when I wanted to upload/download maps and waypoint data. I had to use Task Manager to terminate the process or service (sorry, don't remember which). Pete

Well, I won't have much time to look before the end of the month. (Also I've followed your link and see the files described but there seems to be no links to download them,). Pete

My only experience with a non-computer connection for GPS needed the program which connects to the USB port in the way you state disabling. That was, however, on a Windows XP PC. I never got "USB Easy Data Transfer", but if you can find the application or applet which is doing that, and disable it, then you might be able to access it as a Port. But I doubt if it will look like a COM port as such. There are ways of addressing USB connections as if they are COM ports, but not with the COMn name. Check the FSUIPC4 User Guide, page 12. The suggested name there was \\.\WCEUSBSH001, or 002, 003 etc. Whether this name format still applies I cannot say. All this stuff is really beyond me.The GPSout facility was intended only to link to moving map programs on another PC, never to other sundry devices. The fact that so many folks have managed to connect such things always surprised me. Maybe you'll find more advice (not necessarily FS-related) on Forums more specific to your device or device type. Pete

Yes, and in fact there's nonthing non-standard in the [General] section either, so I think thev INI was a bit of a red herring -- i.er diversion down the wrong path. Hmm. Strange. Glad you sorted it out, but do you still have the bad files? I would be curious to work out how they could affect otherwise normal actions in FSUIPC. If you have then, could you ZIP them and send them to petedowson@btconnect.com, please? Pete

Did you try removing the weather files as I suggested? There should be nothing at all in any INI file that can do this. It'll be something invoked by an option there which is having the problem. just not invoking it is avoiding, not fixing the problem. I'd like to see the problem actually fixed, or at least understand the reason for it! Have you still got a copy of the original INI? If so please show it to me. And you don't need to delete it all. If there's an option set which is invoking some facility which causes a crash, it will most certainly be in the [General] section, so just delete that. All your assignments, calibrations and so on will then still be intact. Pete

No, it is needed by ASN. Is your ASN up to date? Try updating / re-installing. It definitely sounds like there is something wrong. Pete

No, it is not supported, not needed, and it doesn't work in FSX. It dates back to FS98 and FS2000 days. The facilities it provided are included in FSUIPC, on the first options (front) page. Pete

It is not supported nor needed, and hasn't been for a long time. There are facilities in FSUIPC, on its first options page, to do the same things. Pete

Aha! Then it may all be down to a corrupt weather file after all! In that folder, where DLL.XML is, delete the file called Wxstationlist.bin. FSX will make a new one. Then go to the Documents Flight Simulator X Files folder, where your flights are saved, and remove all of the .WX type files. Put them elsewhere if you think you might want them, but if you use any sort of weather program you don't need them. Try that and let me know. Corrupted weather files read by SimConnect can lead to all sorts of odd symptoms. This would be the first time I heard of it affecting the menu system, but the reason it happens when running FSUIPC is because FSUIPC asks SimConnect for the weather regularly. Pete

Please read my last message above in any case. Pete

Sorry, my mistake -- typo. If the only one is in the ASN folder, and you are using ASN and it is up to date, then everything should be okay. Pete

I suggested you run several SimConnect.msi files! That's ALL you had to do!! I have no idea how you messed up your FSX-SE installation, but it cannot possibly occur just by installing SimConnect. I explained all this. I think your FSX-SE installation must have been in a complete mess to start with, which is why I suggest you start over. Uninstall it all, including Steam, then download Steam and install again. I cannot support FSX or FSX-SE myself. If you get into more trouble please use FSX-SE support. Pete Pete

Just rename the Key file to FSUIPC4key.txt or something then. If you are using a 64-bit Windows, since these programs are 32-bit, it "hides" these in a "WOW" section, so you need to go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Lockheed Martin\Prepar3D v2 You need to leave the space in, i.e. Prepar3D v2. Or just search for Prepar3D. It must be there -- the FSUIPC installer doesn't invent lies about your system. it finds the SetupPath parameter in the key, pointing to J:\Flight Simulator X Well something you've installed has added that Registry entry, perhaps to allow something originally intended to be installed in P3D to be installed in your FSX? Those horrible migration tools also make a right mess of things, like this. [LATER] In your Modules folder you said you only had these entries: FSUIPC Documents FSUIPC4 Install.log FSUIPC4.key Were there no FSUIPC4.DLL, FSUIPC4.INI or FSUIPC4.LOG files? Certainly FSUIPC4.DLL must be there? But if there is no INI and no run-time LOG files then that FSUIPC4 has NEVER been run. Are you sure there aren't two installations, and the Registry is pointing to a different one to the one you are running? Pete

It looks like something is stopping SimConnect entering Dialog Mode when requested. I suspect it might be another add-on, one other of those using the menu. Can you give me a complete list please? Just to prove this, go to the folder where the FSX.CFG, EXE.XML and DLL.XML files are -- your Appdata\Roaming\Microsoft\FSX folder -- and temporarily rename the EXE.XML (if it is there) and DLL.XML files, maybe to EXE.XXML and DLL.XXML, say, then re-run the FSUIPC installer so it makes a new DLL.XML file with only it loading, then try that. If this fixes it, it is definitely some bad add-on which is somehow messing with SimConnect. It would then be a matter of elimination to find which it is. Meanwhile, I'll try to solve another problem that this one causes. If FSUIPC sees the Menu request (which it does -- they are logged above) -- but never sees the subsequent DLGMODE confirmation from SimConnect (which it did in the first instance above, but not in the second), then it will never ever try again because it is effectively still waiting for the first notification. All that is shown in the log. Leave the additional parameters in the INI for now. I will make another version of FSUIPC with this latter situation rectified -- I will make it timeout after, say, 3 seconds and assume dialog mode is not going to start, which will allow it to try again if you select the menu again. It may then mean making several attempts, but it is better than nothing till the culprit can be nailed. Pete

Well, there's never ever been any difference in how the dialogue is opened when you select FSUIPC in the menu. It just depends on SimConnect relaying the selection. The dialogue is standard Windows calls, nothing special, and hasn't been changed since well before FS2004 release well over 12 years. I can only think one of the other addons are conflicting somehow. I need more information. Try this. Find the FSUIPC4.INI file in the Modules folder, and add these two lines into the [General] section: Debug=Please LogExtras=x8000 Then try again. Close FS and show me the log again. Pete

ASN = Active Sky Next. The current weather program from HiFi Simulations. It's predecessors were AX and before that ASE, AS2012 etc etc. AS_btstrp.DLL assists add-on programs like FSUIPC and some aircraft ot make weather radars. They are only accurate when used with ASN though. Something you've instlaled is illegally also installing as_btstrp.dll. Can you tell me what that might be, please? Yes, but it clearly shows yuo are using a very old unsupported version of FSUIPC. You must ALWAYS keep up to date before you ask for support. I cannot support old versions. You just posted one! What do you mean, "reinstalled 4.939", you only had 4.90 installed before! Show me the log from that, please. And see if it works if you switch FS into Windowed mode. quite often this is a video driver problem. Pete

Just installing SimConnect versions most certainly won't have any affect whatsoever on FSX-SE itself. SimConnect is merely an interface for applications like FSUIPC. You have either made a mess, not following the instructions properly (ie ONLY running the SimConnect.msi files, nothing else), or you already had a really screwed up system already. I suggest you start again, uninstalling everything, and/or get help from DTG via their support email. Pete

This looks like it is either due to an old version of ASN, or a misinstalled "as_bstrp.dll". Check for such a DLL in your FSX folder, or in the Modules folder. It needs removing. Please let me know. Pete

NEVER EVER post your email and associated Key openly!!! I may have to make that an unauthorised key now! If you don't have and never had P3D it wouldn't ask where it is! It looks like you installed it then deleted it without fully uninstalling it. You need to remove the Registry entry which says it is installed. Look: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v2! <<< ... SetupPath=J:\Flight Simulator X Since your KEY file was generated in any case, the more important file for me to see is thew run-time log -- the FSUIPC4.LOG file. You could also send me your KEY file as an email attechment (ZIP it first or it won't get through). Send to petedowson@btconnect.com. Pete

Yes. It sounds like that USB port on the phone is preset, by the software in the phone, to allow reading/writing data, like photos and videos, from/to the internal memory. Unless you can find, in the phone's settings, a way to turn that off . Is the program you installed to "receive mock GPS information" actually specified for use on that phone? If so it should be able to get the software in it (Android, I assume?) to make the correct confiiguration change to the USB port. Ah, yes, I've read about those. They are wired slightly differently inside -- I think certain pins are jumpered to signal to the device that it needs to do something else. Worth a try. Yes. I suppose so. You can get those too. Only the different wiring configuration in the OTG cable. Pete

Do you have more than one Sim it is installing into? e.g. FSX, FSX-SE, P3D? If so please re-download the Installer from the Download Links subforum and try again. Pete

The log is the Installer log, which doesn't help at all. I need to see the run time log, please. The one named FSUIPC4.LOG. There's no way installing any version of FSUIPC4 ever loses any settings at all. The FSUIPC4.INI file, the one with all your settings, is not touched by the Installer. And ALL versions of FSUIPC since about 4.2 work with the version of FSX you are using, so something else must have screwed up the loading. I'd need more information about that -- like what do you mean by "no access to the popup"? What popup? Do you mean the options dialogue? Or do you mean the AddOns menus entry "FSUIPC ..."? Without actual run time logs and better explanation it is difficult to help. [LATER] Checking the location of the crash, it looks like it might be related to ASN. Are you using an older build of ASN by any chance? have you tried to enable FSUIPC's facility for ASN weather radar? {LATER STILL] Check also, please, that you do NOT have a file "as_btstrp.dll" in the main FSX or Modules folders. Remove it if so. There has been a previous crash which was caused by this mis-installed ASN module (and from someone who said he hadn't even installed ASN!) Pete