John Dowson

The FSUIPC7.log is created each time you run FSUIPC7, so no point saving that. If you are using on a different machine or on an update machine, then the GUID's of your devices could have changed and you will need to manually update your FSUIPC7.ini to handle this. Can you please show me your FSUIPC7.ini after it has been updated and your latest FSUIPC7.log file.

Your log shows that 9 Go Flight devices were detected, including the TQ6: However, there is something strange going on with the registry, as the TQ6 is being allocated a joystick id of 1, which is also allocated to a Gamepad F310, which itself is initially identified as an Xbox 360 controller. Do you have a xbox 360 or a gamepad F310 controller? Could you also please show me your FSUIPC7.ini - we can first try changing the id's there, bur if that doesn't work we will need to clean your registry. A couple of other things: - you are using version 7.3.15. The latest version is 7.3.16 - please update - please always exit FSUIPC7 before attaching a log or ini file. Thanks, John

Then show me/attach your FSUIPC7.log file. Finishing now for the evening...check the driver is loaded and see if your device is detected... It works the same way with MSFS and FSUIPC7 as with P3Dv4 and FSUIPC5/6....

It goes in the FSUIPC installation folder. If you don't know where that is, use the File -> Open Installation folder option in FSUIPC7. Once it is installed, restart FSUIPC7 to get it loaded. Why? Remove it from there. No, doesn't help - you need to install the driver. John

Have you installed the GF driver? If not, download the 64-bit driver/dll from http://fsuipc.com/ and try again. John

You don't need to use conditional programming for this (and there is no such thing as conditional programming for axes anyway) - you can just overload your assignments, i.e. have multiple assignments for the same axis. Even though the multiple assignments are sent, only the ones appropriate to the current view mode will be acted upon. Note also that you cannot control any camera in MSFS using the standard controls/events. You have to assign to the keypress which is assigned to the camera control in MSFS. I recently showed how to do this for the external camera on an axis in another post - showcase/drone should be similar. But if it works perfectly in MSFS, why nor just leave the assignments there? FYI, the current camera state is held in offset 0x026D, which will change depending on the view mode.

You should also try the standard method to determine what control to use: activate logging for Events, open the logging console window (Log->Open Console), set the starter in the VC and see what control/event (if anything) and parameter are logged, and if so, try using that. For the B-47 G, there is also a preset available: Starter Collective Switch (Starter Switch On Collective Lever) - although maybe that is different, I am not familiar with helicopter controls. Generally, to determine what to use for controlling any switch or control, you should, in the following order): 1. Use logging first, and if anything logged, try that. 2. Check any SDK/ custom controls available for the aircraft (third party) 3. Check if any MF presets are available (see https://hubhop.mobiflight.com/presets/) - these are available for assignment by checking the Select for preset box 4. List the lvars and see if any look appropriate, then try using them using the Add-ons->WASM->Set Lvar menu option. If that works, you can then use that (see the Advanced User guide on how to use lvars).

Which aircraft are you using? No - in the SDK, the key event for this is defined as (in gauges.h): #define KEY_SET_STARTER1_HELD (KEY_ID_MIN + 1471) and an error would be reported if "SET_STARTER1_HELD" was not a valid key string. Some events work when assigned in MSFS but not when used via the SDK, and this can be aircraft dependent. So, let me know which aircraft you are using and I can check - if I have the a/c. You could also try the Magneto controls to see if they work. John

Could you also try updating windows - your CoreMessaging.dll version (where the crash is) is 10.0.19041.867, quite a but older than the one I have (10.0.19041.2193). If you get the same issue after that, please show me those files as well as the crash/error event. Thanks.

I guess you can do that - but you may have difficulties setting up reverse... Would be better to remove the scaling, go into the flypad and configure the throttle axis for no reverse : Settings -> Sim Options -> Throttle Detents, uncheck 'Reverse on Axis' and then 'Save and Apply'. John

I have replaced / regenerated the previous installer zip file: http://www.fsuipc.com/download/Install_FSUIPC6a.zip Sorry about this - not sure why this is happening.... John

Also you can try switching to assign using 'Send direct to FSUIPC calibration' and calibrate in the calibration tab, making sure 'No reverse zone' is checked'. Please report back and I can look into this further tomorrow - been a while since I looked at the FBWA320 and now my MSFS is behaving strangely after it updated - keeps freezing.... John

First, you are using an old an unsupported version of FSUIPC7, 7.3.7 - please update to the latest version, 7.3.16. Check your throttle calibration in the flypad - make sure 'Reverser on axis' is set to off: see https://docs.flybywiresim.com/fbw-a32nx/feature-guides/flypados3/throttle-calibration/#5-test Remove that... I can take a look further if you still have issues - been having internet issues and have reconfigured my network and need to complete this. Hopefully I will be back to normal tomorrow... John

You need to assign to the THROTTLEn_AXIS_SET_EX1 controls for the JF BAE 146 - see You should create a specific profile for this aircraft, import your current axis assignments and then switch the throttle to assign with 'Send to FS as normal axis' and then select the appropriate throttle _EX1 control. If you also need to reverse, scale by -1 as shown in that post. John

See the section Additional parameters to scale input axis values on page 41 of the Advanced User guide. Basically you need to need to scale the axis by multiplying by -1, so you add ,*-1 to the end of the axis assignment line in your FSUIPC7.ini file. I could maybe also allow Axis Helicopter Throttle Set to be calibrated using FSUIPC's calibration page.

Ok, thanks, Are you running any anti-virus software (including Windows Defender)? If so, can you also try disabling any and all antivirus software while you install to see if that helps... In the mean-time, I will put back the previous installer version that allows the installation to continue even if no P3D version detected. Should be available sometime tomorrow - although I cannot guarantee as I am having internet connectivity issues at the moment - its been down most of the day and has been very flakey the past few days, not sure what's going on.... John

Can you please attach your WideClient.log, WideClient.ini, WideServer.log and FSUIPC log file. Was this previously working for you, and if so what has changed?

Do you mean that no P3D installation is detected? I don't understand what can be causing this...Can you confirm that you ran P3D at least once and have the mention registry entries please. Did you install the latest combined VC++ redistrbutables? if not, please also do that and try again - please also uninstall any of the original or combined VC++ redistribs that you already have installed for 2015, 2017, 2019 and 2022 before installing the latest combined package.. If you still get issues after that, I will look into making the hacked installer available again, but would rather not if possible. John

The SDK doesn't provide any facilities to save flight plans unfortunately, only to load them. It would be up to the aircraft to save this information - I guess that is what PMDG does. You should probably ask FBW about this. Note also that the FlightSave and FlightPlanLoad SDK functions are still documented as noy working (NOTE: The current status of this function is NO ERROR, NO RESPONSE.) so there may still be issues using those, and the only flight function currently documented as working is the FlightPlanLoad one. John

Note that FSUIPC also provides an additional control that allows you to turn auto-save on/off (when auto-save is activated). Some folks use this to turn auto-save off on take-off and/or approach to prevent these pauses during critical periods. John

You only need FSUIPC6 for P3D - version 4 and 5. For MSFS2020, you need FSUIPC7. If using FSX, then you only need FSUIPC4. All the latest FSUIPC versions, and info on the Flight sims they support, are available from either the Download Links -> Updated Modules section of this forum or from fsuipc.com. John

Thanks for the additional info and links. John

This can happen when a flight is being saved, especially if using a complex aircraft. You can check that your flight-save folder isn't being scanned by any anti-virus software, but other than that there is not much that can be done. FSUIPC just uses the SDK provided API, and it is MSFS that actually saves the flight. John

Download the zip file (from either the Download Links -> Updated Modules section of this forum or from fsuipc.com), unzip it and run the provided installer. Please read/check the README.txt and the installation guide, especially if you have any issues. I will delete your other posts...please stop posting messages that mean nothing in other topics. Just saying 'it doesn't work' means nothing and you will get no assistance. Please explain any issues you have clearly, whether that is with installing or running FSUIPC, and also attach any log files that you may have that would be of assistance, e.g. your InstallFSUIPC7.log file if you have problems with installation, and your FSUIPC7.log file if problems running FSUIPC7. Also, please heck the provided documentation before posting again - at least read the README.txt and the Installing and Registering FSUIPC7.pdf.

You have posted on the wrong sub-forum - please use Paul Hent'ys vlient dll for .Net sub-forum for support for this - I will move your post. John