Pete Dowson

Okay. This shows the problem clearly. Your FSX-SE is not installed correctly. These are the 'clues': 78 NOTE: SimConnect Steam is supported, but it isn't installed. 109 NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed. 140 Trying to connect to SimConnect SP1 May07 ... 483 Failed on SimConnect_Open, return = 0x80070057: FSUIPC4 cannot operate! 483 ... check whether you have a SimConnect.dll in your Modules folder. If so remove it! 483 ... Now trying to connect to another version of SimConnect ... 514 Trying to connect to SimConnect Original ... 514 Now running with SimConnect Original 514 Failed on SimConnect_Open, return = 0x80070057: FSUIPC4 cannot operate! 514 ... check whether you have a SimConnect.dll in your Modules folder. If so remove it! 514 ... Now trying to connect to another version of SimConnect ... 514 FATAL ERROR: FSUIPC4 cannot connect to any supported version of SimConnect! So, please do as it says -- look to see whether there's a SimConnect.DLL in either the modules folder or the FSX folder. There must not be one in either -- delete them if you see them, or at least rename them. Secondly, it would be as well to get Steam to check the installation. To do this, open Steam, right-click on FSX in the left hand column, and select "Properties". In the new window which appears select the "LOCAL FILES" tab, then "Verify integrity of game cache". Then go to the SDK folder in the FSX folder, then "Core Utilities Kit",, "SimConnect SDK", "lib", and execute the SimConnect.msi file there to re-install the Steam version of SimConnect. I think whilst you are there you should also install the FSX versions of SimConnect as many other add-ons need to use one of those rather than the Steam one. To do this go back one folder level and choose "LegacyInterfaces". You'll see three folders -- FSX-RTM, FSX-SP1 and FSX-XPACK. Each contains a SimConnect.msi. Execute each of those, in turn. After all this try running FSX-SE again. Pete

Well, you didn't need to delete everything, but it doesn't matter. So, where is the FSUIPC4.LOG file, please? As I said many messages ago, I need to see that. Post it in a message as you did originally for the Install file. Pete

You could have a small Lua file, run as part of an [Auto] section in the INI, to read the string, extract the number (presumably discarding the alpha characters?) converting it to binary, and placing the result in a user offset (in the range 66C0-66FF). You'd use the "event.offset" function to keep things updated automatically. Not handling strings seems to be a rather big deficiency in Link2FS. There is quite a lot of information in such a form, like the DME readouts for VOR/ILS beacons. Pete

Oh dear. You have left Windows Explorer set hiding the real filenames from you. Please do look at the FSUIPC documentation which does tell you that you need to change the Explorer folder options to stop it hiding the file extensions for "known" files. FSUIPC produces NO files at all with filetype .txt. One of those will be .log and the other .ini, juust as the FSUIPC Install file is .log. Just because they are text files doesn't mean that is their name!! And why did you place the Loader there? That id NOT a good idea UNLESS you know you actually need it. This is made perfectly clear in the Installation and Registration document provided for you to read BEFORE installing. Please remove the Loader and re-run the Installer to correct matters. Pete

Sorry, I don't know what a "Universal App" is. However, if you look at the Header file to see what error 12 is you'll see it shows: #define FSUIPC_ERR_SENDMSG 12 // IPC sendmessage failed all retries (That's from the C ZIP. I don't know C# so I can't advise on that, but it will be the same error). You could have located that using your VS2013 debugger. The most likely reason is that there's some protection or wall between your "Universal App" type of process and the FS process in which FSUIPC is running. One example of such protection is when FSX and the application are running at different privilege levels, e.g.one "as administrator" and the other not. This is the sort of area you will need to look into. Pete

Oh dear. It is the folder where your FSX-SE is running from! How did you find the Installer log then, it is the same place! Where FSUIPC4 is! Checking back to your posted install log it is: E:\Gaming\SteamLibrary\steamapps\common\FSX Pete

The value IS a string already, up to 12 characters, in ASCII, one character per byte, and it is meaningless to convert the first few bytes to a decimal number as you have done for some reason! It might not even be just a number in character form. Flight numbers can have airline codes, like "BAW1455". Pete

It probably is from SimConnect, but FSUIPC offsets for them are integers (and have been since FS98 days -- and FSUIPC has always been about maintaining compatibility for applications across FS versions)., so FSUIPC asks SimConnect for integers. To provide a floating point version I'd need to duplicate the information in 11 new 32-bit offsets, which I'd rather not. Pete

You evidently do not understand what FSUIPC does, what it is for. Just installing it, without registering it and setting your own options -- assignments, calibrations, whatever -- does nothing whatsoever except enable FSUIPC applications to interface into FS. In other words, there is no "joystick feature" to turn off. Pete

Please see threads near here about Registration problems with 4.939j installer of 1st April (only). There's an update now posted -- see the Download Links subforum here. Pete

Hmm. Strange the Key file wasn't automatically copied. I'll have to check that again. No, it is the same file, and the Installer should havce copied it for you. IO'm checking now ... [LATER] Okay, I can see where it can go wrong in the most recent versions of the Installer. I'll fix it and re-upload it. Thanks for letting me know. [LATER STILL] It was a silly bug caused by trying to help someone else who couldn't find the Install Log -- the change on 1st April was to make the Installer also save a copy of the log next to itself. Fixed in the updated install package now uploaded. Pete

What "same problem"? The install log shows everything worked fine, except that you appear to have edited it. Did you take out the part about the FSX-SE installation? Please NEVER edit files before posting, as it makes it impossible to follow the logic properly. I really can't help with the description "same problem" attached to a many weeks old thread, which evidently resolved itself, and doesn't in any way reflect yours, without any explanation whatsoever! [LATER] Perhaps you really meant to describe the problem now also reported in the thread entitled "FSUIPC 4.939j unsuccessful registration in P3D v2.5" very close to yours. Please read that one. [LATER STILL] It was a silly bug caused by trying to help someone else who couldn't find the Install Log -- the change on 1st April was to make the Installer also save a copy of the log next to itself. Fixed in the updated install package now uploaded. Pete

Well, my Jetliner Yoke connected into the back of the Quadrant box, and the latter had a serial port lead connecting to a serial port (not USB) on the PC. That was handled by my PFCFSX driver for FSX, or PFC.DLL for FS9 and before. I don't have them now because I replaced the whole lot with the PFC 737NG cockpit. I understand that, later, PFC made some normal standard joystick-type USB Jetliner Yokes. If yours is one of those then it should connect direct to a USB socket and be recognised in Windows as a joystick device. It wouldn't need any of my software, PFCFSX, or FSUIPC. So you need to know what sort of device you have. Have you never used it before? Is there no documentation for it? I don't know of a "Power Quadrant Cabinet with radio controls, etc etc". How does it connect? Doesn't it come with documentation? And then the Cirrus Rudder pedals. Again, the ones I had connected to the back of the quadrant control box, but they also made standard USB pedals which would be recognised by Windows. Again you need to know the connection. I'm afraid I am NOT PFC support. If you've just bought this stuff new then there must surely be documentation, and you should be able to use the Support from your supplier to get things sorted out. In the Installer, as I already said!!! You are simply repeating yourself. You say you "do have registered FSUIPC and WideFS7", so how did you register them? There is a document inside the downloaded ZIP file which you should read. It tells you these things! You also say "both FSUIPC and WideFS7 come up as unregistered and won't open.". What do you mean "won't open"? WideFS7 doesn't "open" in any case. If nothing "opens" how do you know they "come up as unregistered"? Sorry, but nothing you say makes much sense. Also, shouldn't you have posted two separate questions? One is about PFC things, which is probably better addressed to your PFC support, and the other is about FSUIPC and WideFS. What is the connection in your mind which makes you combine these? Pete

There is no difference in how any version of FS or P3D treats normal standard joystick type devices. Did you not see my previous reply? Are your PFC devices standard USB joysticks, recognised in Windows? If so then there should be no problem.. It is no use repeating your requests for help until and unless you actually supply more information. As I said, I provide drivers for the older original serial port PFC device (like my PFC cockpit), and a separate driver for their later HID type USB devices (like the PFC Consoles). But I know they also do standard devices which need no special drivers at all, only those already in Windows for standard joysticks. Until you can be clearer about WHAT devices you are talking about, I cannot help. Please also READ my previous reply which you appear to have ignored altogether. This is a separate question, nothing to do with PFC devices. You do NOT register either program in Steam, you register in the Installer, as described in the Installation and Registration document which you will find in the ZIP. Pete

Strange how it has become such a mess, then. I think it would save problems later on. You could first just rename the FSX_SE.CFG file just so you can test that it isn't having any affect, not being used. Pete

Fine. But when you had a problem, you didn't come here with the log? Aha. Now for the truth of the matter! Look: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX This is saying you have FSX installed, but in the Steam place. That is normal for a stand-alone FSX0SE installation. But also: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"AppPath" ... >>> OK! FOUND FSX-SE! <<< ... AppPath=C:\Program Files (x86)\Steam\steamapps\common\FSX\ The registry has an entry for FSX-SE as well, which only happens with a side-by-side install with FSX. So, how did that arise? Then: Found FSX_SE.CFG in "C:\Users\ΑΝΑΣΤΑΣΙΟΣ-ΤΑΣΟΣ\AppData\Roaming\Microsoft\FSX-SE\FSX_SE.CFG So, your FSX_SE.CFG file, which SHOULD be the one used by FSX-SE, is in the FSX-SE folder. So that's where the DLL.XML should go! It looks like you messed about with installing FSX-SE in parallel with FSX to start with, but then uninstalled FSX AND FSX-SE, but not properly (failing to delete the FSX-SE folder containing the CFG file) before installing FSX-SE again. I will have a look to see what I can do with the Installer to cope with this mess, but there are already about 4 different combinations for FSX-SE it is dealing with. It amazes me how many ways folks find to make a mess! ;-) Meanwhile, to avoid your own future confusion as well as Installers, please try deleting that FSX-SE folder. Why are you using the loader? It's hardly ever needed. What were the symptoms in FSX-SE which caused you to use it? The OP's log, you mean? Just a couple of messages back in this thread, of course, the one I analysed for him and which shows he does NOT have the same problem as you! (OP = Original Poster). Oh. That never makes any difference to much at all, and certainly not to installation. Pete

Hmm. It should be looking for either folder. The installer was changed a few updates ago. Look, you can see where it looked in the OP's log: Now finding \Microsoft\FSX-SE\FSX_SE.CFG for all users, including this one Now finding \Microsoft\FSX-SE\FSX.CFG for all users, including this one Now finding \Microsoft\FSX\FSX.CFG for all users, including this one and it found it in the that last case, as shown here: . Found FSX.CFG in "C:\Users\Jakob\AppData\Roaming\Microsoft\FSX\FSX.CFG" So it updated the DLL.XML in that folder. This is correct, and is what would have happened in your case with the current installer. So, WHY did you not report it at the time, with an Install Log, and WHY do you think now it has not been fixed? Please see the OP's log. I think you might be mistaken with this solution, but I'd like to know what was wrong with your case if it was not an out of date installer. Pete

Well, it's not too bad, but I meant using the <> button above the Edit area, as I said. It doesn't matter now, but try next time you want to paste in any file. Just press <> and paste into the space provided. But the DLL.XML file isn't the problem -- it is actually the normal DLL.XML that the Installer produces, and that should work fine. So something else is telling SimConnect not to load FSUIPC. Have you ever refused its options for loading? Have you actually used FSUIPC before at all? Look in the FSX-SE Modules folder, see if there's an FSUIPC4.LOG file. If so, show it to me. Otherwise, take a look in the FSX.CFG file, in the same folder as the DLL.XML file. Find the [Trusted] section. Delete from there any lines beginning with Modules\FSUIPC4.DLL, then try running FSX-SE again. Pete

The Install worked fine. There are only a couple of reasons for the AddOns menu not appearing: 1. The DLL.XML file is corrupted in some way, preventing SimConnect loading the FSUIPC4.DLL, or 2. FSUIPC4 being blocked for loading either by a previous refusal to load it (FSX-SE would have asked you), or some other problem associated with trust entries in the Registry. The latter is quite rare (and complicated to sort out), so I'm betting on the first. Find your DLL.XML file ... it'll be in C:\Users\Jakob\AppData\Roaming\Microsoft\FSX Then either show it to me so I can check it (it is a text file, so paste it as you did with the Log -- but best to use the <> button above the edit area to insert it so that it keeps its formatting), or rename it (say "DLL.wasXML") and re-run the Installer so it makes a new one with ONLY FSUIP$ being loaded. Pete

Sorry, not only am I not doing any more development for FS9 or before (after all it is over 11 years old, and my FSUIPC3 code is earlier than that, dating to FS98 in the most part), but I would hve no idea how to do it and don't even have FS9 installed any more. Best if you use SimConnect in FSX and P3D. Pete

No, it isn't available in FSUIPC at present --it never really cropped up as a need. In fact you're the first person to even ask about it in the 9 years of SimConnect! It wouldn't be hard to add. I'd need to find 256 bytes of space for the Theme pathname to be written, but it can be write-only as there's no way to read the name of the currently set theme. So, if you confirm the need Ill see about adding it for the next FSUIPC update. Pete

PFC serial port hardware is handled by my PFCFSX.DLL driver, and it's USB HID hardware is handled by my PFCHID.DLL driver. There's no PFC hardware I've ever had which would be recognised directly by any simulator or other "Steam" program. It is all handled by drivers I wrote for it and which interface to FSUIPC. If you mean you have standard joystick type equipment, recognised by Windows as such, then FSX-SE will see it just as FSX, FS0, or any other 'game' program would, as they will all be using the standard Windows facilities for joysticks. Pete

Weird. That sounds like a virus checker in action. Try downloading 4.939j from the Download Links subforum. Place the Installer on the desktop and run it -- it will put the Log on the desktop too. Then show me the log. Pete

Well, it is certainly there, because otherwise it couldn't find it's way into the Installer and show a path to P3D!!! So what changed on your system? You said you were using that one in any case. Closes again after what? Sorry, I am not understanding much of what you say, and I most certainly need the log to help you. It sounds like your system is really screwed up. Doesn't it come up with any messages at all? No screen, nothing? No, you can start it from anywhere, though I never recommend using the desktop. you could, with some installers, end up with a lot of clutter there. If you really cannot get a log, or any information to help, I'll look at making a test version of the Installer which saves an extra copy of the log in the same folder as the Installer (or, in your case, presumably on the desktop). Pete

It's a typical problem with Saitek -- they get things wrong in the Registry. I think the answers are over in the Saitek support forum. It either involves a driver reinstall, or some Registry editing. Ask over there. It isn't FSUIPC. However, you do seem to have a few superfluous and possibly interacting assignments in your FSUIPC4 INI file. Look: [Axes] PollInterval=10 RangeRepeatRate=10 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=0Z,256,D,22,0,0,0 3=0U,256,D,26,0,0,0 4=0V,256,D,4,0,0,0 5=1X,256,D,7,0,0,0 6=1Y,256,D,8,0,0,0 7=1R,256,D,3,0,0,0 == Rudder 8=2X,256,D,7,0,0,0 9=2Y,256,D,8,0,0,0 10=2R,256,D,3,0,0,0 == Rudder So, in the general (non-profile) assignments you have two rudders -- one on your Yoke, the other on your Quadrant? The same applies to the Cessna and PMDG 737NGX profiles. But in the Latter you also have a real duplication, not of throttles (that's a Saitek install problem), but: THREE different assignments to spoilers TWO ailerons, TWO elevators, and two assignments to a #26 which is strange as #26 isn't an axis. [Axes.PMDG 737NGX] RangeRepeatRate=10 0=0X,256,D,1,0,0,0 == Aileron 1=0Y,256,D,2,0,0,0 == Elevator 2=0Z,256,D,26,0,0,0 == UNKNOWN? There's no #26 so I don't know how you got these 3=0U,256,D,26,0,0,0 == UNKNOWN? 4=0V,256,D,22,0,0,0 ==Spoilers 5=1X,256,D,1,0,0,0 == Aileron 6=1Y,256,D,2,0,0,0 == Elevator 7=1R,256,D,3,0,0,0 == Rudder 8=1V,256,D,22,0,0,0 ==Spoilers 9=2X,256,D,22,0,0,0 ==Spoilers 10=2Y,256,D,9,0,0,0 11=2Z,256,D,10,0,0,0 12=2R,256,D,3,0,0,0 ==Rudder 13=3X,256,D,7,0,0,0 14=3Y,256,D,8,0,0,0 15=3R,256,D,3,0,0,0 == Rudder Regards Pete