John Dowson

The text file you attached does not correspond to the log file. Your log file shows that you have controllers on in P3D: Best to disable controllers completely in P3D if assigning in FSUIPC, as P3D has a tendency to re-assign. check that you have no assignments in P3D, or just disable controllers completely. You also have spoilers assigned to two devices - your T.Flight Hotas 4 and your TQ6: It is not a good idea using two distinct axes for the same control as they will not be syncronised and can send conflicting values. I suggest you delete one of those assignments. And your spoiler calibration looks strange, with a very large null zone: Spoilers=-11903,-7168,-512,12223/24 I suggest you re-calibrate your spoiler axis, once you have decided which axis to use. John

Do not install any Saitek drivers. Disconnect your saitek devices and then take a back-up of your registry (using the Windows Registry Editor, File -> Export). Then create a file called removeDevices.reg (name doesn't matter but extension must be .reg)) with the following content: Windows Registry Editor Version 5.00 [-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_A221] [-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_A221] [-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2221] [-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_2221] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_A221] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_A221] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2221] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_2221] Run that file by double-clicking it in Windows Explorer. This will remove those registry entries. Then reboot and re-attach your devices. Then run FSUIPC7, exit and show me those 3 files again. John

I have no idea what a 'dataref' is... No idea what that means either. What language is that? No idea. I think you need MobiFlight support, not FSUIPC. Try their discord channel. I cannot support MobiFlight. In FSUIPC offset 0x8531 is in an area reserved for 'Radar Contact, verbal command control area'. John

Yes... FSUIPC7 is a 64-bit program, you cannot run that on a 32-bit OS. I posted a link to that post to show you how to run a simconnect client (such as FSUIPC) on an FS client PC. It shows how you configure your simconnect client for a networked connection. That post obviously shows you how to do this with FSUIPC7, but the procedure is the same for any simconnect client, i.e. your simkits. If it requires FSUIPC, then you need to use the 32-bit WideClient, available in the WideFS6 download. John

Then maybe its something the aircraft does while initialising? Just check the 'Send to console window' checkbox in the logging tab. John

You usually get a notification of some sort - a message that is displayed then disappears, but I think this depends on your windows settings. I wouldn't worry about it. You can always check which drivers are in use via the Windows Device manager, if needed. John

No problem.

They still don't work with the AP_ prefix, but the following are accepted: FLIGHT_LEVEL_CHANGE FLIGHT_LEVEL_CHANGE_ON FLIGHT_LEVEL_CHANGE_OFF RPM_SLOT_INDEX_SET I also checked other previously unrecognised control, and the following are also now available: BEACON_LIGHTS_ON BEACON_LIGHTS_OFF AP_SPD_VAR_SET_EX1 I will add these in the next release of FSUIPC7. John

Ok, but that is exactly the same link as in www.fsuipc.com - I just copied and pasted it so I'm not sure what the issue is... John

No, the ini change didn't work. We can try cleaning the registry entries if you like - let me know and I can provide you with a .reg file to do this. No, this is not normal. However, FSUIPC cannot see your yoke at all - is it assigned in FSX? There is an assignment to your ailerons for joystick no. 5L 2=5X,256,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }- But no such joystick (i.e. your Alpha yoke) is present in either your .ini, .log or registered in your registry: Are you sure that the yoke was connected? To a hub or direct to the PC? Maybe try switching ports. The Alpha needs to be connected to either a USB 2.0 port or USB 3.1+ - there are issues with the Alpha on USB 3.0 ports. John

I need to see all 3 files again (FSUIPC7.ini, FSUIPC7.log and FSUIPC7.JoyScan.csv) after the changes you have made and when using the default windows drivers. Once I have seen them, I can advise on cleaning your registry.

Your log shows several autobrake controls being sent: However, these are not being sent by FSUIPC. You need to determine what is sending these controls. As this is not being done by FSUIPC, I'm afraid I don't think I can help you with this. Also, non if these events are being sent after a button press. Maybe you can try running with the logging console open to see what is actually logged when you press a joystick button (any one?) and lose your speedbrake setting, to see what events are being sent when this occurs. I cannot tell when this is happening when looking at your full log. John

Can you not just use the windows default hot keys for this? To maximise, that would be Windows key + Up You can not assign this to a button press in FSUIPC as we no longer allow the windows key as a modifier as this can cause issues (i.e. it will also be acted on by windows itself if assigned in FSUIPC, causing issues). John

Updated.

Ok. When I look at this I will try both with the AP_ prefix and without, to see if any are recognised. Thanks for the info. John

So the simkits software is a simconnect client, and not an FSUIPC client? If its a simconnect client, you can set-up a networked simconnect connection. To do this, you need to configure a network simconnect connection in yuor MSFS SimConnect.xml, and also provide a SimConnect.cfg file for your client, and the client must be configured to use this connection. I have provided instructions on how to do this for FSUIPC7 (i.e. to run FSUIPC7 on a client machine) here: If your client software is an FSUIPC client, then as you have a WideServer license, you can download WideFS6 and use the 32-bit WideClient.exe included with that, as the protocol between WideClient and WideServer is the same for 6 and 7. John

I had added these when they appeared in the documentation, but when I tried to use them I got unrecognised errors when trying to request them. These are the ones that were not recognised: //{KEY_AP_FLIGHT_LEVEL_CHANGE , "AP_FLIGHT_LEVEL_CHANGE"}, -- NAME_UNRECOGNIZED //{KEY_AP_FLIGHT_LEVEL_CHANGE_ON , "AP_FLIGHT_LEVEL_CHANGE_ON"}, -- NAME_UNRECOGNIZED //{KEY_AP_FLIGHT_LEVEL_CHANGE_OFF , "AP_FLIGHT_LEVEL_CHANGE_OFF"}, -- NAME_UNRECOGNIZED //{KEY_AP_ALTITUDE_SLOT_INDEX_SET , "AP_ALTITUDE_SLOT_INDEX_SET"}, -- NAME_UNRECOGNIZED //{KEY_AP_HEADING_SLOT_INDEX_SET , "AP_HEADING_SLOT_INDEX_SET"}, -- NAME_UNRECOGNIZED //{KEY_AP_VS_SLOT_INDEX_SET , "AP_VS_SLOT_INDEX_SET"}, -- NAME_UNRECOGNIZED //{KEY_AP_SPEED_SLOT_INDEX_SET , "AP_SPEED_SLOT_INDEX_SET"}, -- NAME_UNRECOGNIZED //{KEY_AP_RPM_SLOT_INDEX_SET , "AP_RPM_SLOT_INDEX_SET"}, -- NAME_UNRECOGNIZED However, I'm not sure what version I last tested these. I will take a look and if they are now available I will re-activate. There are a lot of new events in the last couple of SU updates. I still need to revise the documentation to see what else can be added. I am planning to do this in the next few days/weeks, once I have cleared the backlog of support requests (and updated my various systems to the latest MSFS/P3D releases....). John

And a Happy New Year to you as well! I will update later today...working through the backlog... John

Did you try a right-click and selecting Sava as... ? Other than that, I have no idea. Can you access from this: FSUIPC WASM Module 0.5.5d Thats the same link as in www.fsuipc.com, with the link source: http://www.fsuipc.com/download/FSUIPC-WASMv0.5.5d.zip Maybe your browsers don't like http? Try pasting that link directly in your browser. Or maybe its some sort of anti-virus software preventing the download?

Button 22 has one assignment: 15=P3,22,Cx03009400,x00000002 -{offset dword set, offset 9400}- which your log shows being pressed and the ssigned vontrol sent: Ok.

Then you must be running 5.2....I have just updated to 5.3HF1 and get this: I really can't see how it is reporting the incorrect version - this is taken from the Prepar3D.exe file properties. What does your P3d Help -> About menu option report? Is there an MSFS update? I'm still on 1.21.13.0 which I thought was the latest - just fired it up and no update available for me... John

No luck with what? What did you try? Yes, but before we do that can you let me know if you did have any saitek software or drivers installed or not. And if you did and removed them, I need to see your updated files.

Are you sure? Just took a look and it says 53 for me: 114047 Monitor IPC:3124 (U8) = 53 114047 Monitor IPC:3124 (U8) = 53 I still haven't updated to the latest 5.3 HF. I will do that today and recheck. Could you check again and if you still see 52 please show me your FSUIPC6.log file. The version in that offset should match the P3D version reported at the beginning (2nd line) of the log: Prepar3D.exe version = 5.3.12.28072 John

Are you sure? Which browser are you using? Just tried in Chrome and it downloaded as expected. Maybe a temporary glitch?

Your log shows both assignments on joystick3 button 23 being performed: That also shows your LandingLightsOn macro being executed. There are no assignments to your compound runwayturnoff macro, so I cannot check that. Therefore I cannot see any issues. Could you maybe explain again what your problem is, and provide an appropriate log and ini file if you want me to look into this further. John