Pete Dowson

That's strange. I wonder what can be different about your Win10 2004 install? Thomas tested it fine on his (I am not a Windows Insider so haven't got it yet). Here I tested on Win7 and Win10 1909. Anyway, I need to see the Installer log. I cannot do anything without information. If the install attempt with the non-Beta FSX-SE aborted without crashing it will have produced a Log fil, which I need to see. If the install attempt with the Beta crashed, there may or may not be a partial log prouced to that point. If not, if a picture of the one-screen log can be captured, p[ease d0 so. Either way, I need to crash details from the Windows Event Viewer. This is what I see in my Install Log for the non-Beta FSX-SE: Checking version of the FSX-SE EXE: ... Version 10.0.62615.0 (Need at least 10.0.62607.0) Checking compatibility with installed SimConnect: Looking for SimConnect.dll with "C:\Windows\WinSxS\Fusion\*SimConnect*" Looking for SimConnect.dll with "C:\Windows\WinSxS\*SimConnect*10.0.60905.0*" Found the path, now trying "C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll" Found SimConnect build 10.0.60905.0 Looking for SimConnect.dll with "C:\Windows\WinSxS\Fusion\*SimConnect*" Looking for SimConnect.dll with "C:\Windows\WinSxS\*SimConnect*10.0.62615.0*" Looking for SimConnect.dll with "C:\Windows\WinSxS\Fusion\*SimConnect*" Looking for SimConnect.dll with "C:\Windows\WinSxS\*SimConnect*10.0.61242.0*" Found the path, now trying "C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SimConnect.dll" Found SimConnect build 10.0.61242.0 Looking for SimConnect.dll with "C:\Windows\WinSxS\Fusion\*SimConnect*" Looking for SimConnect.dll with "C:\Windows\WinSxS\*SimConnect*10.0.61259.0*" Found the path, now trying "C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll" Found SimConnect build 10.0.61259.0 Now of course I have also been using other programs which interface via Simconnect and those tend to be written for FSX rather than FSX-SE specifically, so I have the FSX RTM (60905), SP1 (61242) and ACC (61259) SimConnnects installed. Perhaps, as a test you could try installig those too -- you'll find them in the LegacyInterface folder (please see the IMPORTANT note included in the ZIP). Same for you. I need information please. Pete

There's another report somewhere near here about a CTD since ASP3D Beta was installed. I've beed using it successfully since its day of release, but it is a Beta and possible may not play nicely with all add-ons. Perhaps you should post on the Active Sky support forum? Oh, also BTW I've read a couple of reports on AVSIM's forum about CTDs which follks initially thought might be down to ActiveSky but subsequently determined were due to AI Traffic programs. (I'm using AIG's traffic which seems okay, but I would guess it depends on the models being used). Pete

Please download FSUIPC 4.975. now released. This works on the Windows 2004 insider updates, and also now supports FSX-SE Beta build 63003 for proper connection to Simconnect (but the hacked facilities are still not included). Pete

Please download FSUIPC 4.975. now released. This works on the Windows 2004 insider updates, and also now supports FSX-SE Beta build 63003 for proper connection to Simconnect (but the hacked facilities are still not included). Pete

Your "mappings" are not deleted. They are still in the FSUIPC6.INI file you placed into the P3DV4 Add ons folder. Now you reinstalled into the P3DV5 Add ons folder you just need to copy that file scross, overwriting any default one now generated. As Thomas explained above, you are given the choice of where to Install FSUIPC, and whether you want two separate installations, one for each of P3D4 and P3D5. If you only choose one of those and don't provide an alternative folder then the installer will install into the relevant Add ons folder. And, also as Thomas says, this is explained in the Installtion guide provided in the ZIP!

Okay. Glad you identified the cause! Thanks for letting us know. Pete

Sorry, I don't remember it and I'm not searching. If yuou wanted me to look at it you needed to include a link. Does PI support Windows 7 or later? If not, you cannot run WideClient on it. That doesn't appear to be a question about FSUIPC or WideFS. Pete

I have them both running together fine, no trouble. The only difference in FSUIPC for ASP3D is to reference the revised name for the installed "AS_connect" DLL. Functions in that DLL are used to obtained the rain cloud matrix data set, and other values not otherwise available. And the functions called are identical to the previous version, and HiFi have assured me there's no change in the interface. So the change in FSUIPC amounts to just changing the characters "64" to "v5" in the DLL name when P3Dv5 is being used. Can you please send your report to the HiFi support forum, to see if they have a view on this? It really sounds like there must be a problem with the ASP3D install. Pete

Do you have to buy FSUIPC to interface to a "mobiflight connector"? I don't even know what it is. If you want to use FSUIPC, whether you buy it or not, there's only one version available for FSX -- FSUIPC4, as it clearly shows on the simMarket website and on our website FSUIPC.com. Pete

If you have your plan loaded into FSX for its built-in GPS then there are offsets which provide some data. See the Offsets Status document in your FSUIPC documents folder (offsets in the 6000 - 61B8 area). There's no departure ID (I think you are supposed to know where you came from :-)) but there is the destination ID 6137 5 GPS: Flight plan destination airport ID If you really want the full plan you can read it from the file PLN file. the full filepath for that is in offset 0130. If possible 9i.e. the folder is shared) the filepath is provided in UNC format so you can read it from another PC. Pete

Every system is different. Why is he still on 4.3? Perhaps he never updated, never having need for support and not interested in improvements and bug fixes? Sorry, not possible. what version are you using? If not the latest (see FSUIPC.com) then update first. THEN if you still have a problem and think it is FSUIPC related, please describe the problem properly and provide the FSUIP4.INI, LOG and JoyScan files from the FSX or P3D Modules folder. And please, for your next and future posts, entitle the thread you create with some more appropriate title. "tariq" is completely meaningless and won't help get other users involved in helping you, ones who may more about your add-ons than I. That's the whole point of an open forum, so a more collective knowledge is applied. Start with your reply to this one. Pete

I've test the Installer on my Win10 system and it worked fine, but I am on what I thought was the latest (or it was not long ago, when I last checked. And no automatic updates have occurred since then):: Win10: 1909 build 18363.592 Your 19608 seems a lot later. Are you sure that isn't just an earlier 2004 build? I've made a version of the Installer which looks through all three possible folder names now, and Thomas tested with his 2004 install and still gets the problems. Something has definitely changed for the worse in at least one of the standard Windows APIs I am using here. So, sorry, this may well take a little while to resolve. I've been all day on it here and not achieved much so far except more bafflement. Oh, one other thing. If you are using “Everything” for the search then i just discovered that that normally (for me) infallible program doesn’t actually find everything it ought to in those folders! I had to sort the folders in Explorer then scroll through them manually to find things! Pete

Ooops! I seem to have posted at the same time as you, John! Sorry. Dad

There's never been a way of purchasing FSUIPC during installation. not without opening your browser and going to the SimMarket purchases page, paying, getting the key, and coming back to the waiting Installer. The only purchase way has always been via SimMarket. Pete

Seems one of the Win10 updates has changed how the Side-by-Side installation works. Though I don't understand why Arrow gets them in C:\Windows\assembly\GAC_32\ whilst Thomas gets them in: C:\Windows\WinSxS\Fusion\ Which makes a little more sense -- still in WinSxS but another level down! 😞 I'll see what I can do to deal with these variations. Pete

That's why FSUIPC's Installer can't find them, then. Something is stopping the SimConnect installers working correctly. Can you find a SimConnect.dll anywhere on your system? If we knew where it had installed it might help. You never know, you might be able to make the correct WinSxS folder (as pin my earlier message), and copy it there -- allusing an Explorer in Administrator mode, obviously! To find files I use a program called "Everything" which is excellent at quickly searching complete systems for files. Get it from https://www.voidtools.com/downloads/. An excellent and very useful program -- and it's free (well, donation-ware). Another thing which might be worth trying is temporarily turning off UAC (user account control) and re-running the SimConnect installers. You don't need all of them anyway, just the latest you have. Pete

Without access to the equipment I'd be at a bit of a loss. In any case aren't there more user-friendly ways of doing things with Saitek stuff now? Have you looked at SPAD? https://www.spadnext.com/home.html Pete

Good. Happy flying! Pete

Sorry, not seeing the plug-in file itself I've no idea which is "line 17". Good! Well done! 😉 Pete

The offsets you are using are hexadecimal, so should be represents with the prefix 0x. You appear to have recognised that in these comments: -- Park_Brake = 0x0BC8 -- FSUIPC Offset Values 0=OFF 32767=ON-- Canopy = 0x3367 -- FSUIPC Offset Values 0=OFF 1=ON but then you've omitted them in the ipc.writeUW calls. I would have thought it would give errors when you tried to execute it. did you check the FSUIPC log? One other thing. The doors offset 0x3367, is only a Byte, so for writes to that you should use ipc.writeUB. Pete

So you are watching the throttle movement in FSUIPC calibration? Is that how you are detecting that Throttle 4 isn't moving? Pete

By the "programme" do you mean the PMDG 747, or FSUIPC's calibration? How did you assign the Saitek lever? Perhaps you could show us the settings? You can paste the content of your Settings file, FSUIPC6.INI, which you'll find in the folder you selcted for the FSUIPC6 install. If you are assigning in FSUIPC you also need to disable controllers in P3D, or there will be conflicts. Pete

Did you run the Installer "as administrator"? If you are sure you did, then I'm afraid something went wrong with your SimConnect installs. There should be a SimConnect.dll is one of the C:\Windows\winsxs folders. For example, I have all four versions installed here and these are the folders: C:\Windows\winsxs\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297 C:\Windows\winsxs\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20 C:\Windows\winsxs\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568 C:\Windows\winsxs\x86_microsoft.flightsimulator.simconnect_8791cf09e30348a9_10.0.62617.0_none_68d0ad6179edc71a These folders will be protected against reading or writing unless you are an Administrator or run the program as administrator. Pete

The installer for FSUIPC6 is not on the "SimMarket shop", it is in only one place and has alreay been downloaded and installed by many users. The download links on SimMarket are the same as those on this Forum, in the "Download Links" subforum above, and on our website FSUIPC.com. And they cannot be corrupted as they are in use by many. Furthermore, we are now on version 6.07, after several updates and revised files. Which have you last tried? In future please try to provide rather more information in your posts if you want to receive some help. If you look back at your previous posts (from well over two weeks ago now!) there was no useful information at all, nothing to explain what you were talking about at all! Just ended by a rather nasty comment "wasted money". It was with reluctance I bothered to answer such a post back then! Pete

Not really. i just go for it. Most things turn out better for a fresh start anyway! If you have saved things to restore, just try the programs first in their "raw" state. You might be pleasantly surprised! And when you do restore things, do it slowly, checking each time. Pete