John Dowson

Do you mean the DHC-3 Beaver? I can create an lvar with this name and this is then picked-up by FSUIPC: So if such an lvar existed, it would be listed. So I am confused about this issue... Maybe ask on the MobiFlight Discord server about this... Please report back, or provide further details. John

Please show me / attach your FSUIPC7.ini, FSUIPC7.log and FSUIPC7.JoyScan.csv files nd I will take a look. Most probably your joystick GUIDs have changed and these will need updating, but this should not affect key assignments. Finishing now for the day, will take a look tomorrow. John

It did look like a USB hub power issue and the cable re-organisation is important information that wasn't included in your original posts. Anyway, no problem - and thanks for the update, John

It is not possible to read the location of the aircraft.cfg file in MSFS2020/2024 if the file is encrypted, which is usually the case for paid add-ons. In MSFS2024, aircraft are 'streamed' - I haven't checked if the aircraft.cfg is readable for such aircraft. I will take a look on Monday, or possibly later today if I have time. John Later: Looks like it doesn't work either for streamed aircraft (i.e. all aircraft in MSFS2024) - see https://devsupport.flightsimulator.com/t/simconnect-requestsystemstate-aircraftloaded-returns-partial-path-of-aircraft-cfg/9041/7 I will still check this though and report back.

No - lvars can only hold numeric data. From the Adobo documentation: IMPORTANT! "L:" vars can only hold numeric data and nothing else, eg: no strings, no binary values, no structs, etc... Are you sure there is an lvar with this name? Are you sure it isn't just 'EHSI_1_HDG' and the '1:' is some MobiFlight syntax? How do you read this in MobiFlight? And what do you mean by 'the default Canadair'? Which aircraft is this - there is no such default aircraft as far as I am aware... Nothing is written as no such lvar exists. I am pretty sure FSUIPC would pick it up, even with a name like '1:EHSI_1_HDG' - it is only a string after all...

Please don't attach the events.txt file (I have removed those) - that is the file that holds the presets, is installed by the installer and doesn't change. It was the FSUIPC7.log file that you should also attach. Did you change the USB port for the USB pad? Or is it in the same hub as another device, or was the logitech joystick connected to the same hub as the UDB pad? If using hubs, are they powered? Your joyscan csv shows the device is detected twice, with the same GUID, but with different vendor and product ids: Not sure why its doing this - looks to be a strange usb issue - especially as this was previously the problem with your logitech joystick but now its with the UDB pad. You could try ignoring that dodgy entry with the empty name by adding: IgnoreDevice=0x28DE,0x11FF to the [JoyNames] section of your FSUIPC7.ini file. If that doesn't work, please show me the files again, but include the FSUIPC7.log and no the events.txt file (if you cannot see the log file, it is because you have windows explorer set to hide the extensions of known log files - change this setting). John

The log file you attached is from 7.4.17, where you say everything is working. Although that log file does contain errors. 7.4.17 is also quite old now - there have been 6 release since that version. You should update more often.... One change that was introduced in 7.5.0 that could affect some third-part add-ons is the offset that holds the sim version (0x3308), Some add-ons expect a value here on start-up, and prior to version 7.5 this was always set to 13. With the introduction of MSFS2024, this offset is now only populated once FSUIPC has a connection to the FS so that it can determine the version being used. For add-ons that need this offset populated earlier, you can add the following ini parameter to the [General] section of your FSUIPC7.ini file: init3308=13 So please try that. Any issues, please set logging for IPC Reads and IPC Writes and show me / attach your FSUIPC7.log file. Also, please always exit FSUIPC7 before attaching logs. Many people use SIOC with FSUIPC - I would have expected a lot more support requests if there was an issue here. If you still get issues with that change, after saving the log file from 7.5.4, can you also please try the attached version below, which is 7.5.3 (just rename your current FSUIPC7.exe and save the attached to your FSUIPC7 installation folder). Also show me / attach the log file from this version. John FSUIPC7.exe

Hi Luke, Could you be more specific -seems like there were several issues in this thread. Also, be aware that MSFS2024 is a different beast and I think that for many aircraft it is not possible to read the aircraft.cfg file. But I will check further tomorrow. John

Peter retire > 5 years ago now. It looks like the name has disappeared from the registry entry for your Saitek X-56 stick. Can you please attach your files - your ini, log and JoyScan.csv files and I will take a look. John

To assign to presets, check the Select for Preset checkbox in the top-right of the Buttons & Switches Assignments dialog box. You can then click the Find Preset... button to find the relevant preset, ordered by provider, aircraft, subsystem etc. A more complete search interface can also be found at https://hubhop.mobiflight.com/presets/. Please also take time to read the User and Advanced User manuals. You will find more details on using presets (as well as lvars, etc) in the WASM section of the Advanced User guide. When I get time, I will make a FAQ entry on how to determine what to assign to using FSUIPC's logging facilities as I am continually explaining how to do this. For the time being, try using the support forums as such questions on assignments have been asked many times before. Let me know how it goes and if you have any further issues. John

Please use the FSUIPC7 sub-forum for all issues/questions regarding FSUIPC7. I have moved your post. Many of the standard controls do not work for add-ons (or even some Asobo aircraft), especially complex ones, and you have to investigate other methods, such as lvars, custom controls, input events or presets. For the FSLabs lights, try presets: As you see in that image, there is a Beacon ON and Beacon OFF preset you can use. In general, if standard controls don't work, check for a preset. If there is no preset, use FSUIPC's logging facility to determine what is being used. For The FSLabs, many buttons/switches can be controlled using custom control, via the standard FS control Rotor Brake, where the parameter indicates the switch. For example, see the following post where I explained how to do this for the APU Master switch in the FSLabs: John

I don't know why you pasted both your log and ini in your last post - I have removed them. They did not add anything new. I was just reminding you to exit FSUIPC7 before showing me files and did not need to see the same one again. And if a file is more than 10 or 20 lines, please attach it rather than pasting it - and this does not mean that I want you to attach them now. Only attach if you have followed my instructions and it is still not working. As for your issue, please re-read my last comments and report back, As I said, try starting FSUIPC7 after MSFS has started and arrived at the main menu, or use the auto-start feature. And if you get the same connection issues, read that FAQ entry and manually configure the initial connection parameters - and read the section on auto-tuning of start-up parameters in the Advanced User guide. John

As I said, can you please exit FSUIPC7 before attaching log (and ini) files. But your log shows that FSUIPC7 couldn't establish a connection to MSFS. First, you started MSFS manually, and it looks like you did this before MSFS was running. If starting manually, you should start FSUIPC7 after starting MSFS, and one MSFS has arrived at the main menu. However, it is far better to use the auto-start feature so that FSUIPC7 is started by MSFS when ready. To use auto-start, please re-install and leave the selected components (to install) as they are. For details on tuning the start-up parameters for preventing connection issues, see the following FAQ entry.: Note that once you have configured the DetectToConnectDelay / DetectToConnectDelayAuto parameters correctly, you can also set the InitialStallTime parameter to 0 which will then instruct FSUIPC7 to wait indefinitely for a response to the connection request. Also see the section Auto-tuning of initial start-up ini parameters on page 11 of the Advanced User guide. John

Is FSUIPC7 actually connect to MSFS? Maybe you can show me / attach your FSUIPC7.log file (from a session when you get this error, and please exit FSUIPC7 before attaching the file). If FSUIPC7 is connecting to MSFS and there are no error in your log, you need to contact Aivlasoft about this issye - I only support FSUIPC and not third party clients. John

No problem - glad its now sorted. John

It is better to disable controllers completely if assigning in FSUIPC, as P3D has a habit of re-assigning controllers which can cause issues. This is nothing to do with the curve, it is due to your calibration.. The minimum value calibrated is 4534 for throttle 1, and 3272 for throttle 2. Axis ranges usually go from -16384 to +16383, so you are losing more than half your axis range. Calibrate the minimum value correctly. The reason you only see the right-hand part of the slope is explained in the User guide: Also, for future reference, please always attach your FSUIPC ini file when you have any issues with assignments - this tells me a lot more than images do (including which version of FSUIPC you are using, which you didn't mention!). John

As you have no assignments in FSUIPC that could cause such behavior, it mut be coming from somewhere else. First, just disable controllers in P3D and see if you get the same behavior - if not, the issue is with your P3D assignments. If you do get the same behavior, please show me another log file bit with logging for Buttons & Keys as well as Events (non-axis controls) activated. John

This is available now....you may need to clear your browser cache to get the updated installer. Please let me know if that solves your issue. John

Ok, but that is strange - you shouldn't need to re-enter or re-register your license on an update (unless you have changed your installation folder). When you update, the license page of the installer should be pre-populated (from your FSUIPC7.key file), and you should just skip the registration. John

Ok. I have corrected the installer for this and will make this available tomorrow (no new version). So either add a new line and re-install, or wait until tomorrow, download the updated installer and try again. John

Anywhere in the [General] section... order is not important in ini files.

You have controllers set to ON in P3D: Either disable controllers in P3D, or check your assignments in P3D and remove those that are not needed. P3D has a habit of re-assigning controllers if not disabled. Better to disable controllers in P3D and assign everything in FSUIPC. If you must have assignments in P3D, then be aware that it can re-assign and give unwanted behavior. John

Strange...but I have already DM'ed you your key details... John

This probably ,means that you are using an unregistered version, i.e. there is no license/key file (FSUIPC7.key) in your installation folder. Did you install into a different folder? When you re-installed. were your previous key details shown on the last screen, and did you skip key validation? Installation does not touch your FSUIPC7.key file, unless you opt to re-validate. John

Log in to your SimMarket account and get your purchased key from there. I can also PM you your key details. John