Pete Dowson

So that's how to include a textual & in an XML file? If so, that's all I needed, thanks. BTW what does the "amp; part supposed to mean? Seems quite complicated compared to, say, C's method fo for exaple including textual \ using \\. Pete

Two things to do: 1. Version 62607 of FSX-SE is out of date. Log into Steam and get it updated. The current version is 62615. 2. If you still get a reported SimConnect not found error (which updating FSX should fix), then you'll need to find the SimConnect.msi installer, in the FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-XPACK folder and double-click it to install it. Pete

Well, I could eliminate all & signs, but where it is part of a file or path name, as here, that will make that file or pathname incorrect. So what do you suggest that would work apart from asking all Scenery designers to avoid using &? There must be other XML files which need file and path names, so how are they managed? Pete

Events and Offsets are two completely different things. FSUIPC calls events "controls" (as they used to be called in older versions of FS). The events list I publish is called "List of FSX and P3D Controls" (or similar for FS9). My documents are in the FSUIPC Documents subfolder of the Modules folder.. The offsets list is a list of address-based variables which can be read or written through FSUIPC. They are neither "controls" nor "events", which are transitory things, messages passed to FS to ask it to do something. I don't think there are any such events. Try putting the number as the parameter for the control. If you want toggles to act like separate on and off switches, best to use the FSUIPC offsets to control them. You can assign buttons and switches to FSUIPC-added controls called "Offset <type of value> Set" to do this. However, you cannot access these from XML. You do need to refer to the list more carefully. There re 4 pause controls -- PAUSE OFF, PAUSE ON, PAUSE TOGGLE and PAUSE SET (the last would take a parameter -- 1 for ON, 0 for OFF). Parking brakes are better dealt with via the offsets controls I mentioned, though again, not from XML. Pete

Thanks. If I work it out, would you test the result for me, please? Won't be till next week. Pete

Ah, I see. Yes. The "BULK" one should probably be ignored (but gets listed incorrectly it seems). FSUIPC should only use the HID ("Human Interface Device") interface. I'd like to modify FSUIPC to eliminate the "BULK" listing and auto-letter assignment, but I'm not sure where the difference lies in what I'm reading. Do you think you could show me the USBDeview output, and the joystick listings in your INI file now, telling me which is the one you actually see? (I don't have access to any devices which do this sort of thing). Thanks, Pete

Hmmm. Strange -- the INI file shows TWO X-55 sticks connected: 3=Saitek Pro Flight X-55 Rhino Stick 3.GUID={A9660090-6567-11E6-8004-444553540000} 4=Saitek Pro Flight X-55 Rhino Stick 4.GUID={A965D980-6567-11E6-8003-444553540000} Both have unique GUIDs assigned by Windows. But neither 3 or 4 show anything in the axis or button assignments? You have them both assigned to different letters: E=Saitek Pro Flight X-55 Rhino Stick E=GUID={A9660090-6567-11E6-8004-444553540000} F=Saitek Pro Flight X-55 Rhino Stick F=GUID={A965D980-6567-11E6-8003-444553540000} Could you try the JoyIDs program. Use it to check which number is truly assigned by Windows to that stick (the ONE stick?), if any, and either way then changing it to some other number (e.g. 6 or above, which are free it seems). See the FAQ thread entitled "Fixing joystick connections not seen by FSUIPC " for details. Delete the above "stick" entries in the INI file first. You do actually already have some button assignments to both the E stick and the F stick! 15=PF,2,C65570,0 -{GEAR_TOGGLE}- 16=PF,5,C65752,0 -{PARKING_BRAKES}- 17=PF,3,K83,8 -{Key press: S}- 18=PF,4,C65589,0 -{SPOILERS_TOGGLE}- 19=RF,12,C65758,0 -{FLAPS_INCR}- 20=RF,10,C65759,0 -{FLAPS_DECR}- 21=PF,13,K120,8 -{Key press: F9}- 22=PF,11,K123,8 -{Key press: F12}- 23=RF,9,C66278,0 -{RUDDER_TRIM_LEFT}- 24=RF,7,C66279,0 -{RUDDER_TRIM_RIGHT}- 25=RF,8,C65615,0 -{ELEV_TRIM_UP}- 26=PF,6,C65607,0 -{ELEV_TRIM_DN}- 27=PF,0,K65,8 -{Key press: A}- 28=PE,5,C65752,0 -{PARKING_BRAKES}- 29=PE,3,K83,8 -{Key press: S}- 30=PE,1,K112,11 -{Key press: ctl+shft+F1}- 31=PE,13,K120,8 -{Key press: F9}- 32=PE,11,K123,8 -{Key press: F12}- 33=RE,10,C65759,0 -{FLAPS_DECR}- 34=RE,12,C65758,0 -{FLAPS_INCR}- 35=RE,9,C66278,0 -{RUDDER_TRIM_LEFT}- 36=RE,7,C66279,0 -{RUDDER_TRIM_RIGHT}- 37=RE,8,C65615,0 -{ELEV_TRIM_UP}- 38=RE,6,C65607,0 -{ELEV_TRIM_DN}- 39=PE,4,C65589,0 -{SPOILERS_TOGGLE}- Not sure how you did that if they aren't responding. I assume one set of those above is redundant, and should also be deleted. The renumbered stick should appear as device E if you delete the current allocations before reloading, so delete the PF and RF entries (which, oddly, were made before the E assignments, another strange thing!). If you do really only have the one stick, then I can only think that somehow Windows has old spurious entries in the Registry (which is where FSUIPC finds this data), and one "real" entry, but the latter has no ID assigned -- a seemingly common problem with Win8 and later, but rare in Win7 and before. JoyIDs fixes the Registry entry giving the ID number. Once you'd done all this, best change the "AutoAssignLetters=Yes" to "No" before next reloading in case the Stick wanders around again. Pete

Thanks for the INI file. I can reproduce the problem. I will fix it over the weekend -- no time tonight. It appears to be only with Axis assignments, which is why I haven't seen it here. All my similar assignments are only for buttons. Odd, because both use the same encoding / decoding facility. But now I can reproduce it, should be easy to fix. Thanks, Pete

You don't "switch" to it! <custom control> is in the list of assignable controls, right at the top. Your PMDG aircraft installs with a folder called SDK or similar. It's a file in there. Sorry, but I don't use PMDG aircraft so I can't help further. Maybe the PMDG forum? PMDG is not related to FSUIPC. Pete

SimConnect networks okay, too. Haven't you tried it? Pete

The important part is this, from the client log: 593 Attempting to connect now 593 Trying to locate server: Need details from Server Broadcast 593 Failed to connect: waiting to try again The broadcasts from the Server aren't being seen by the Client. This may be because the Workgroup name is not the same in the two PCs. Windows only broadcasts withing a workgroup. Note that Windows 7/8/10 have different default workgroup names to older versions like XP. You can either correct the workgroup name (mine is universally called "PETES"), or put the server name (or IP address) and the protocol to be used into the Client INI file. Please see the WideFS documentation where all this is explained -- in the section with a red plea to actually read some of it! Pete

That's correct, then. If the request to ASN had failed, the file yould only be 1kb and blank. The size varies according to the range requested, unless FSUIPC gets no response from ASN. Just to double-check, you could also add the line to FSUIPC's INI file to get a Bitmap file. When you get one of those you can view it in any Windows bitmap viewer -- I think just double-clicking it will display it, in fact. Once checked in this way it's over to Prosim I'm afraid. FSUIPC can do no more than provide the data as supplied by ASN. Pete

This seems to be a common misunderstanding. There's no difference whatsoever between "registered version" and "unregistered". All registration does is unlock features in FSUIPC's user interface, the interface you see in Add-Ons FSUIPC menu entry. So the registration or otherwise doesn't affect it loading and initialising the Add-Ons entry at all. If the FSUIPC entry does not appear in Add-Ons then FSUIPC is probably not being loaded. But please, next time, check the Modules folder in P3D and see if there is a log file ("FSUIPC4.LOG") being produced each time you load P3D. If so, FSUIPC4 is being loaded but is not connecting to SimConnect properly. In this case I seed to see that Log file please -- paste it here. If FSUIPC4 is not being loaded there is a different problem -- probably your DLL.XML file is corrupt. Go to your AppData\Roaming\Lockheed Martin\Prepar3D v3 folder and find it there. Show me that, or test by renaming that file and re-running the FSUIPC4 installer so it creates a fresh DLL.XML. If you have difficulty finding these things, show me the Install log and I can direct you. Pete

The log is from a sessions which closed normally, not with a crash. A log from the crash might show that point reached in FSUIPC's actions, but one from a successful session is not useful I'm afraid. Are you running somewthing which is possibly using FSUIPC to get something into or out of FS which might still be happening when the current aircraft is being unloaded? What sort of CTD is it? The actual error code is significant. Crashes in "Kernalbase.dll" are serious -- that's at driver level! FS's own API.dll can be related to aircraft loading. Pete

Is this the serial port device using my PFCFSX.DLL driver, or some new USB one looking like a standard joystick? FSUIPC uses Windows APIs for joysticks which only know certain axes - X Y Z R U V standard axes and sliders S,T and POVs P Q M N. (Some of that nomenclature is probably local to FSUIPC). I know later versions of DirectInput supported 8 normal axes instead of 6, (and 64 buttons instead of 32), but FSUIPC doesn't extend to those extra ones. If your device is a standard USB joystick device, maybe those two axes are the two FSUIPC doesn't see. Is there any technical information available for it? Pete

No. That's really weird! I have many many keypress assignments and don't get any problems. Can you attach or send me your INI file please (petedowson@btconnect.com)? Is the PMDG 777 loading initially, by default, or do you load it after P3D is loaded? If not default, which is? Pete

Please give more specific information -- i.e. what you assign to and which options you select. You should also realise that the named controls in FSUIPC's list are FS controls, not PMDG ones -- the PMDG 737NGX implements its own system and doesn't use FS controls. Test switch assignments to FS controls using a default FS aircraft. For PMDG 737NGX you need to assign to <custom control> and enter the PMDG control number which you calculate for their SDK file of type .h Pete

Sorry, there's no useful information here. Maybe a debug log with WideClient would show more, but beware the size of the log. You will need to ZIP it and send it to me as an email attachment -- petedowson@btconnect.com. Debug options are shown in the Technical guide for WideFS -- try Log=All first, then Log=DebugAll (separate sessions). Send e both in suitably named ZIP files. Incidentally, have you checked that PF3 will actually run Networked? Are others doing it? Is it documented? Pete

Interesting thread, this! I think I'll move it to "the User Contributions" subforum, so that it becomes a reference for others. Pete

Ctrl+K disabled all controls in FS? Really? I didn't know that! (Does that include the "disabled controls" control? :-) ) Use FSUIPC logging. Enable Button/Key and Event logging, then when the AP disconnects check what happened in the log file. Pete

Have you verified that things work okay in a default FS aircraft? Pete

You are also using AES I think -- the log shows that. Okay, but according to the log FSUIPC4 has terminated normally. I assume this is a log after one of the crashed? I think the crash is only occurring because one of the other things you are running is not heeding the termination notice it would be getting and is still making calls into FSUIPC or SimConnect or elsewhere in FSX, and that is causing a crash which appears to be in FSUIPC because FSX is not unloaded quite yet. FSUIPC's code doesn't get unloaded from memory till FSX itself closes. From the log it is also seen that something is continually loading a Plan: C:\Users\xxxx\Documents\Flight Simulator X Files\WX.PLN It seems to being loaded at regular intervals, though two times at the same time earlier on. This activity seems to go in spates. I've no dea what is doing that. Is "WX.PLN" something to do with ASN? I've used ASN (and ASE, ASX, before it, and now AS16) for a long long time, but I've never seen that. I wonder if it is related. I sometimes get ASN (and now AS16) crashing after I close FSX. I think this is due to similar things happening. They are very timing dependent. One thing you could try, to see if it's related to FSUIPC's weather functions, is to add NoWeatherAtAll=Yes to the [General] section of the INI file. Other things to try involve a process of elimination. Try, if you can, without ASN, then AES, etc. I'm afraid after tonight I'm away for a bit over two weeks. Pete

Maybe something else running using FSUIPC after some of its services have finished. Can you list what else you have running please, whether inside or outside FSX? Is it consistent, or only happen once or occasionally? Does the log finish abruptly? What are the last few lines? Are you using ASE, ASN or AS16? Have you enabled the WX Radar feature in FSUIPC? If you are using Active Sky, does the error occur still if you close it before closing FSX? Pete

There are 4 ADF ident controls, none called "ADF IDENT" ithout qualification.: RADIO_ADF_IDENT_DISABLE RADIO_ADF_IDENT_ENABLE RADIO_ADF_IDENT_SET RADIO_ADF_IDENT_TOGGLE These are all for ADF1. If you have an ADF2 there are 4 more. So, perhaps you are using the wrong one? If you have got two controls being sent, then either it is because you assigned both, or because something else in the Aircraft code is sending the other. If the former, I don't understand. Why did you program the release if you are only using a button? If you use the TOGGLE control instead, only on the Press, then it will switch it on with one press and off with the next. How do you mean? FSUIPC doesn't "lose" assignments They are stored in your FSUIPC4.INI file and will only be changed if you change them. Are you assigning to both press and release? Don't, not for a button. If you are not, then it's some behaviour of the aircraft you are using. I can't control that. Please try making your assignments with a default aircraft. Get them working there. Then, when you try the add-on, if it still doesn't work correctly, contact their support. Pete

The proper sequence of Windows commands arriving is important too, though. For each Key in a combination there will be a WM_KRYDOWN, then there's almost always a WM_CHAR for the Graphic key involved (if any), then in reverse order, sually (though it probably isn't important) the WM_KEYUPs for each key as it is released. The free Microsoft utility Spy++ can be used to monitor the messages being received by a selected process. You might be able to use that to see what it is doing. Pete