John Dowson

I still don't understand this - what exactly is grayed-out? If you have an Assignments menu option in the menu bar, then you should be able to open the assignments panels. Maybe attach a screen-shot so I can see what you mean here. Ok. John

Yes, just a "glitch"...if it happens again, try a system reboot - that usually sorts things out. Anyway, glad its all working again. John

That is very strange as that is related to FSUIPC7's monitoring of MSFS2020, and nothing to do with client applications connecting to FSUIPC7. Maybe it was something temporary...can you try removing that now and see if it connects or not. Note that option is set automatically if running under windows 11, which you seem to be using - from your log file: Therefore I cannot see how that can change anything... How about those other two apps - PACX and Self Loading Cargo?

When I start LRM, it connects straight away when FSUIPC7 is available/running, even without MSFS running, regardless of the order in starting. The usual reason for clients not connecting is that they are being ran at different priority levels - everything must be ran at the same priority level. Could you be running these clients with admin privileges but not FSUIPC? If you has set the previous versions .exe to run as admin, you will have to do this each time you update. John

Also, please note that your old FSUIPC7.ini may not work directly out-of-the-box with your new PC, as the GUIDs of your devices/controllers may have changed. If you run FSUIPC7 ince with your old ini, exit and then attach your updated FSUIPC7.ini file here, I can take a look and update it for you if needed. John

That log file shows that FSUIPC7 was still running when it was attached. Please ALWAYS exit FSUIPC7 before attaching log files. Can you also attach your FSUIPC7.ini file please. This is rather worrying: Do you not have any general button assignments? John P.S. Try attaching here now instead of file.io

No wonder the file is so large - you have a lot of unnecessary additional logging activated. Please disable all logging for the moment and show me a clean FSUIPC7.log file. Also please make sure that you exit FSUIPC7 before attaching the file. John

The FSUIPC7 config file, where all your settings and assignments are stored, is called FSUIPC7.ini. The config.ini file is nothing to do with FSUIPC7. What do you mean by this? For auto-start issues, see What do you mean by this? What is grayed-out? Are you running/using a licensed/registered version or the freeware/unlicensed version (i.e. Do you see an Assignments menu option in the menu bar)? They will be in your original FSUIPC7.ini file. John

Your upload file size will increase the more you post. I need to see your FSUIPC7.log file though - try compressing it, or use an on-line file sharing app (e.g. https://www.file.io/) if the file is still too large. I will take a look with LRM later as I believee that is a free one I can test with here... John

Ah, ok then. Must be the device also returning a non-usable GUID for some reason. Just ignore. Your files look good! Regards, John

Great! Do you have two VPC Panels or just the one? The HID scanning reports two of these, but only one is acquired: The 2nd one looks dodgy (N in ValsOk? column) so maybe there is only one of these devices and that can be ignored... John

Ok, its good to know the cause. Thanks for updating, John

It would be useful to understand what actually causes this warning - any ideas?

As I said, FSUIPC does nothing with such files. I don't see any good reason why these files should be loaded, but many possible difficulties (e.g. how is FSUIPC supposed to know the name if this file?). As I said, if you want some data from such files available via FSUIPC offsets, then you will need to write a bespoke lua script to read/parse the file, extract the data you need and then add this to a free/spare FSUIPC offset. John

Can you also add custom logging (Log->Custom) with a value of x200000 - this will log further information around the acquisition of HID devices.

I am not sure what can be done if the parking brake is being given the same GUID as one of your rudders... Can you try changing the ids assigned to your Parking Brake using the JoyIDs program. These are the current entries: Try changing to use ids 13 and 14 (instead of 5 and 12). It would be better to remove that first entry completely, as the GUID for that entry is the same as the one for your Fulcrum One yoke, but if it is removed it will probably just get re-created. Once you have changed the ids, run FSUIPC7 and re-attach your files again. Have you installed any specific drivers for the Parking Brake, or do you just use the windows default drivers? If you have installed specific drivers, try uninstalling them and using the standard windows drivers instead. Also, who makes this Parking Brake - do you have a link?

Not sure why you attached that image - I know what simdirector is, I have just never used this tool. Attaching the generated file would have been more useful (what is it called?), and also the location. But FSUIPC probably does nothing with this file, unless it is one of the standard files loaded when loading a flight or mission. If you want any information from such files available via offsets, you would have to write a lua script to read the file, extract the information that you require and then add this to a free/spare FSUIPC offset. John

¿Qué es este programa? ¿Es compatible con FSUIPC3? Consulte la documentación de este programa y tambien de FSUIPC3 para ver si hay información sobre el uso de dispositivos VRInsight. Tenga en cuenta que FSUIPC3 ya esta muy viejo y no puedo ayudarle mucho con este problema...

Just click Yes to trust and run FSUIPC. If you get this message every time, see If FSX crashes when you click Yes, see John

To assign a preset to an axis, you need to select Send Preset to FS (below Send to FS as normal axis). The Select for Preset checkbox is for assignment to button controls on entering/leaving axis ranges on the right-hand side of the axis assignment panel. Note that in an early release there was only the one checkbox (Select for preset) which controlled the menus on both the right and left-hand sides, so some older posts may only mention this checkbox. John

I will update the documentation. This is different - it passing the keypress through to the FSUIPC assignments, It will still go to the FS and trigger any assignments there, I will clarify in the documentation. John

Try with [Profile.FenixA320] 1=FenixA320 2=Fenix A320 Or if the A320 is the only aircraft from Fenix that you have, you can use: [Profile.FenixA320] 1=Fenix John

It has now been updated. John

If you open the windows device manager, do you see your Parking Brake there? If so, try uninstalling it from there, disconnect the device, run the reg script, reboot and try again....

Did you run that .reg script? If so, it is just adding the same entries back. Not sure what to advise, except to go unplug again and go back to your previous working ini - you should do this each time if/when you connect the parking brake and get issues. Maybe try connecting it to a different USB socket or hub to see if that makes a difference. Otherwise, I am not sure what to advise, sorry. I will have a think and get back to you sometime next week,,, John