John Dowson

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

No, sorry - there are just no controls for this. It may be possible using an ground-services add-on, such as GSX (I don't know), but P3D provides no other pushback controls as far as I am aware. John

But MSFS will receive all key presses. FSUIPC receives key presses from MSFS and will then act on them if assigned, it cannot prevent MSFS seeing these key presses. This is necessarily different in FSUIPC7/MSFS than in previous versions as FSUIPC7 is a separate executable, so it can no longer directly receive the key presses from windows when MSFS has the focus, it can only get them via SimConnect. Therefore how have you configured 'to not do so'? Then there probably isn't one! Just checked here and there is no default binding for that key combination. The log looks fine to me... I wouldn't worry about this if its working...FSUIPC is just logging what it sees. I suspect that this is just the way PG3 loads/adds the entries, as you say... John

Actually may be worth removing the registry entries of the Parking Brake first....ah, too late. Please do what you did before - disconnected the parking brake and replaced the ini with the last working one and check that all is ok again. Then, before re-connecting the parking brake, run the attach script and then reboot. removeDevices.reg

Yes, your files look ok again now... Isn't this what you did last time, except for keeping the Parking brake connected? No, no need to run that script at the moment - the Parking Brake doesn't even appear in your registry anymore. Try re-connecting the parking brake again and lets see what we get... John

I don't see why an axis would depend on the direction of travel... Do you not use the tiller when taxiing? Ah yes...well, it should control the nosewheel direction regardless, but for pushback you don't want to be using the nosewheel steering... For pushback control, you need to use offset 0x31F4. However, you cannot control the angle precisely, you can only set the direction -tail swing to the left or right. You will need a lua script to do this if you want to control using the tiller, and you need to take care that the nosewheel also isn't being controlled when in pushback, so the lua script should also control the steering when not in pushback. You therefore need to assign your tiller to write its value to an FSUIPC offset, The lua script should have an event function on this offset, and when the value changes it can decide if this is meant as a steering control or a pushback control by reading offset 0x31F0 - or, better, have an event on this offset that sets a flag in the lua script that you can use to determine steering control [value of 3] or a pushback control [value != 3], and then either send on the steering control or write to the pushback control offset if the value there needs changing.

What FS and version of FSUIPC are you using, and what A320 model? Use events/controls, not variables. Have you tried assigning to the FSUIPC axis SteeringTiller (under Send direct to FSUIPC calibration - calibrate on page 9), or the standard control Steering Set? John

There also seems to be an issue with your new parking brake, as windows is reporting the same GUID for this device as one of your T-Pendular-Rudders: GUIDs are supposed to be unique...not sure what is going on here or what can be done about it....lets wait and see what your updated files say.... However, may be best to leave this disconnected for the moment, and we can add this back once we have corrected the rest of your devices. John

This is a very bad idea - please do not do this again... Your registry is in a complete mess now, with many of the GUIDs associated to your deices being wrong. This issue may now take quite a few iterations to get things back in order. First, we'll try and remove all the dodgy registry entries and see if they can be regenerated correctly. Take a backup of your registry, and then please disconnect the following devices: Fulcrum One Yoke Parking Brake Joystick - HOTAS Warthog AGRONN B737 Yoke V2.2 Cat3Design A320 FO Tiller V2 Landing Gear Lever Then run this attached .reg file to remove the registry entries for those devices: removeDevices.reg Reboot and re-attach those devices. Download and use the attached FSUIPC7.ini: FSUIPC7.ini Then run FSUIPC7 and exit, and show me/attach those 3 files again. Is your "throttleTek 3" device no longer connected?

For help with MobiFlight, please use the MobiFlight discord channel. For help with FSUIPC6, please use the main FSUIPC support channel: https://forum.simflight.com/forum/30-fsuipc-support-pete-dowson-modules/ Not sure why you posted in the FeelThere support forum - shall I move your post to the FSUIPC support forum? Or do you require support from FeelThere? If so, there support platform has moved - see John

I will update later today if I find time, otherwise tomorrow or possibly on Monday morning. John

I have released 7.4.8 now - please update to the released version. Regards, John

Because FSUIPC is an embedded dll in P3D, and in MSFS2020 it is an external app/exe. With XINPUT, only applications that have the window focus will receive the input from such controllers. With P3D, FSUIPC will receive the input when P3D has the focus (as it is embedded), and with MSFS2020 FSUIPC will not receive the input as MSFS2020 will have the focus and not FSUIPC7.

First, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. Please take care to post in the correct place if you require support. I have moved your post. What are these files? Where are they located? What do they contain? What do you expect FSUIPC to extract from them. i.e. what data do you want to find in the offsets from these files? As I do not know what files you are talking about, I expect that FSUIPC currently does nothing with these. Maybe you can attach an example and I will take a look. Is there a fixed location where these files are located/created? John

The xbox controller uses XINPUT protocol that is not supported by FSUIPC7. However, you should be able to use this by using a conversion utility - from the README,txt file (included in the zip file that you downloaded): Have you tried this? John

I think I have found the root cause of this issue! Looks to be related to the new Input Event interface which is still rather flakey - there are already quite a few issues/bugs reported in this. I have added further checks around this now which should prevent such issues Hopefully this will be the ;last beta and should prevent any issues. I will probably release this tomorrow or Sunday, after further testing. John FSUIPC7.exe