John Dowson

Ok, I have found it - It triggers the control/event Nose Wheel Steering Limit Set, Use with a parameter of 2048 or 6027 to turn on, and 0 to turn off. Not sure how to switch between lo/hi though.... Also, see this post: https://forums.flightsimulator.com/t/f-a-18-nose-wheel-steering/513803/4 John

Yes there is...and I quoted the appropriate section - lines 603-605: It is in the file called PMDG_NG3_SDK.h - although the FAQ does reference PMDG_NGX_SDK.h, which I will correct... Take a look in your Community\pmdg-aircraft-737\Documentation\SDK folder. Anyway, the number is given in the FAQ and I have told you what to use....I do not understand what your issue is. Look for that file, but try the numbers I have already given you...it really isn't that complicated, and the FAQ entry is provided so that I don't have to continually answer such questions on this.... John

Something must have changed.... Check your firewalls (disable and test without to see if its a firewall issue), check your Workgroups, check if your IP addresses have changed (if you are using the address rather than name) - basically read the documentation and follow the instructions given there on connection issues. If you still can't get it to connect, please show me your WideClient.ini, WideClient.log, WideServer.log and FSUIPC?.log and FSUIPC?.ini files. John

Your log shows a couple of issues. First, you have installed FSUIPC under your Documents folder. This can cause issues, and I recommend that you re-install into a different folder, e.g. C:\FSUIPC6 or C:\Prepar3D v5 Add-ons\FSUIPC6. You can skip registration, and after you re-install copy across your FSUIPC6.key, FSUIPC6,ini and your *.mcro files. The second issue is a problem with the registry entries for your devices, To correct this, please disconnect your rudder, stick and throttle, open the windows regedit program and take a back-up of your registry and exit. Next download and run (i.e. double-click in Windows Explorer) the attached .reg file - this will remove the current registry entries for your devices. Then reboot your PC and then re-connect your devices. Then start P3Dv5, load an aircraft and then exit. Then show me your updated FSUIPC6.log and FSUIPC6.ini files. John removeDevices.reg

What does this mean? There is no 'custom control offset'... please see that FAQ entry I referenced on how to determine the custom control number to use. Then you have misread it...you just need to know the value of THIRD_PARTY_EVENT_ID_MIN, which is defined here: i.e. THIRD_PARTY_EVENT_ID_MIN is 69632, as it says in the document. So, the control number for EVT_OH_DOME_SWITCH is 69632 + 258 = 69890. You can also use the defined presets for the PMDG Dome switch, which use the Rotor Brake control: These are available by checking Select For Preset in the assignments window. There is also a FAQ entry on using the Rotor Brake control method for the PMDG in MSFS of you want to use that instead. This is marked as deprecated as the Rotor Brake control has been deprecated by MSFS, although it can still be used. However, custom controls are preferred and are more powerful as Rotor Brake controls only provide access to mouse actions. John

Not necessarily. It changes from an unsigned char (1 byte) to an unsigned short (2 bytes). Not only does the size increase, but 2-byte data type must be stored on a 2-byte boundary, so it can't be on 6C8D and moves to 6C8E. Did you take a look to see if the AircraftModel is held in that offset? I will check this layer... John

Sorry, missed your second post.... John

I can't help with RCv4, sorry - maybe other RC users can help, or you maybe better off asking over on avsim.com - there are plenty of RC users there... John

Have you tried using the custom control: #define EVT_OH_DOME_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 258) The parameter will be: 0: DIM 1: OFF 2: BRIGHT (as the value held in offset 0x6443, once the PMDG SDK broadcasts have been enabled). If you don't know how to use the PMDG custom controls, see

Did you also install SP1 and SP2? If not, please do that....at least SP! is required... If/when using a boxed version, you usually also need to download and install the service packs.... John

I certainly don't have the time or resources to take on any further work.... Maybe ask about this over on avsim,com, although there may be some developers familiar with the FSUIPC SDK that may be able to help you... but not me! Regards, John

Let me know if that simvar is the one you are looking for.... ...and a very Happy New Year to you and your family as well. Regards, John

Its John, not Pete - Pete has retired. Updating FSUIPC will in no way affect any of your assignments, unless you have changed your installation folder. If that is the case, you need to copy across your FSUIPC7.ini file (where your assignments are stored) from the old location to the new one, as well as any other files you may use (*.lua, *.mcro, *.evt, *.dll, etc). Otherwise, if using profiles, it could be that you are using a variant not covered by your current profile assignment. If this is the case, then you can either add that variant to the profile, ot edit your profile section to use substrings to match all variants (see the documentation on how substring matching for profiles works). If you were using an older version of FSUIPC before updating, presets were moved to a separate drop-down om v7.3.8, now available by checking the Select for Preset button. Presets are stored in a file called events.txt, located in your FSUIPC7 installation folder. If you are still having issues after reviewing the above, please attach your FSUIPC7.ini and FSUIPC7.log files. John

MSFS is crashing but this has nothing to do with FSUIPC7. Check the Asobo forums - I cannot help with MSFS CTDs. John

First, that lvar-to-offset definition us not valid - you also need to specify the size/type. Presuming that lvar holds an integer in range 0-255 (probably just 0 or 1, no?), then add it as an unsigned byte, i.e. Then you can assign your button to Offset Byte Togglebits, giving A000 as the offset and 1 (or x1) as the parameter, as explained in the Advanced User guide. John

Try offset 0x0798 (Autopilot target altitude value, as metres*65536) or 0x07D4 (Autopilot constrained altitude value (limited by Flight Plan and flight profile as in SID), as metres*65536), or 0x0818 Regards, John

Try the provided custom controls: #define EVT_MCP_VNAV_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 386) #define EVT_MCP_LNAV_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 397) If you don't know how to use the custom controls, see John

The current version of FSUIPC7 is 7.3.15, so I can only check with that (only latest version is supported), and the latest PMDG version is now 3.0.56, so I will check with that...I have also received a message from PMDG tech support informing me of this change. Looking at the latest header file, it is only the AircraftModel that has changed size, which is held in offset 6C8D, so only this offset and those after it (WeightInKg, GPWS_V1CallEnabled and GroundConnAvailable) should be affected. I will update the documentation - there shouldn't be a code change necessary, but I will check. This should be the new offset allocation if you can check: 6C8E 2 BYTE x 2 AircraftModel 6C90 1 BYTE WeightInKg 6C91 1 BYTE GPWS_V1CallEnabled 6C92 1 BYTE GroundConnAvailable 6C93 Last byte of first reserved area for PMDG 737 Note that as this change is near the end of the allocated offset area, I will shift those other 3 offsets down, rather than spoofing or moving the Aircraft Model offset. Hope thats ok. John

As well as what @brybechr has said, it would be useful if you could also attach your WideClient.ini - from what your log says, it still looks like its using the server name FSXCOMPUTER, which is resolving to 192.168.1.100, and not the address.

Logging of Buttons & Keys would help to confirm the key press/releases are being sent, as well as maybe IPC Writes... With the key press and release control (1070), the release is sent directly after the press, with no delay. It has been this way since inception, so I do not want to introduce an artificial delay between the press and release, especially without confirming this is indeed the problem, i.e. with appropriate logging showing the press/release is actually being sent and the time difference between them. I could add a delay maybe based upon a new ini parameter, but would rather not - this is why separate pres and release controls are provided after all. Then just do this! And best wishes for the New Year to you - regards, John

Have you tried using the provided presets: ? John

Why suddenly - what has changed? Your ini only shows a throttle - in fact, the throttle is registered twice with different GUIDs: And you only have assignments to the second, with JoyID of 2. There are no other devices recognised or assigned, including your rudder which you sat is assigned and working... Check that you are not using either the software or the drivers provided by Saitek. If so, uninstall them and use the windows default drivers. Also, please change the AutoAssignLetters parameter (shown above) to Yes - this will prevent issues if/when the joystick Ids change, which can happen quite easily. If you still have issues, please provide a fuller explanation, and also attach your FSUIPC6.log file as well as your FSUIPC6.ini file. John

You could try uninstalling and re-installing SimConnect on its own first, before you go for a full FSX re-install.... John

Not having this aircraft, I can only advise to use the logging facilities to see if any event or lvar change is registered when you move the throttle out of cut-off, and if so try and use that,,, Note also that there are now quite a few presets available for the HJet, including HA420 Throttle 1 Set and HA420 Throttle 2 Set, so you could try those. John

What is this? There is no such thing for FSUIPC - it is either licensed/registered or not, and I support both versions. I can't see how FSUIPC's auto-save facility can be involved in this issue, as all it does is call the SimConnect SDK function SimConnect_FlightSave at the defined interval. However, there are still issues with this function - it does seem to work sometimes, but also many issues have been reported, and this function is still documented as: NOTE: The current status of this function is NO ERROR, NO RESPONSE. i.e. it is still not working correctly. Therefore any issues with the saving of flights need to be fixed by Asobo. If it is causing issues for you, then disable this for the time being. John