John Dowson

Yes, I did point this out to you: 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. Yes it does: It is only there because you must have assigned this at some point. There is no way that it can be there otherwise. John

Of course I need to see that. You stated that your issue is that FSUIPC does not recognise your yoke. How can it recognise it if its not connected? The new log and ini files you posted shows the Alpha was recognised, now it is connected: And you have your ailerons assigned to the X axis: and that you have also set a very large slope on the this axis (in the calibration tab): Such a large slope will give very little movement unless you move the axis to its extremes (check the slope curve in the calibration tab). So, if your ailerons are working but only when moving the axis to its extremes, remove that slope. If the ailerons are not moving at all, try switching to a different aileron control such as Aileron Set, or, better still, switch to using 'Send direct to FSUIPC Calibration' (rather than 'Send to FS as normal axis' and use the Aileron or Aileron/SlewSide control, and then make sure you calibrate that axis in the FSUIPC calibration tab. John

Happy New Year. Sounds very strange.... First, try reinstalling FSUIPC. If you get the same issue, take a look add both of your add-on.cfg files. One is in C:\ProgramData\Lockheed_Martin\Prepar3Dv5 and the other is in C:\Users\[your_name]\AppData\Roaming\Lockheed_Martin\Prepar3Dv5. The FSUIPC entry should be in the latter - is this where it shows Active=true? If that is the case, you should not have to reactivate. You could also try tr-installing the P3D client. If you still get issues after this, can you show me your add-ons.cfg file from your AppData\Roaming\Lockheed_Martin\Prepar3Dv5 folder. John

No it hasn't - the current license is valid until the 28th January:

Then either - you placed the key file in thr wrong folder - the file does not have the correct name - it should be called FSUIPC7.key - check this as explorer sometimes hides extensions of known file types. If the key file is in the correct location, then you will see the registration details in the installer registration screen. But just skip - validation will not work. However, the usual way is to install fsuipc7 and skip registration, then drop the key file into the installation folder. You cannot drop the key file into this folder before you have installed, unless you are re-installing.... It really isn't that complicated....

Ah, didn't realise that you were using the Announcements page....haven't updated that for a long time. I will update that page - Please just use www.fsuipc.com. This is because you extract it into that folder which is, by default, created by the extractor. You need to extract directly into the Community folder, and not let the extractor create the default folder which it does based upon the zip file name. John

Please read the initial post on how to use this license: John

Can you please provide more information. Just installing FSUIPC7 will not do anything - how have you configured it? Where/how does your transponder get its input from? Have you made any assignments to this device in FSUIPC7? As a minimum, I need to see your FSUIPC7.log and FSUIPC7.ini files. But I suspect that you really need support from the device provider on how to configure/set this up. John

You should have tried FSUIPC7 with the trial license before purchasing... To use lvars, you need to either - add the lvar to a free FSUIPC offset, and then assign using one of the offset controls - use a macro file - use a lua script Please see the provided documentation. If you are new to FSUIPC, you should at least take a look at the User guide. Access to lvars/hvars/calculator code is provided by the FSUIPC WASM module. Please see the Advanced User guide, starting on page 43. For macro use, see P33 for general macro information, and P35 on how to access lvars using macros, also in the Advanced User Guide. John

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