John Dowson

This is because you have a very large DetectToConnectDelayAuto set: Auto-tuning is gradually reducing this: but it will only reduce by 10 seconds at a time. This high value was probably set via auto-tuning when MSFS took a long time to load (for some reason). Try manually setting that value to 30 in the [General] section of your FSUIPC7.ini file. If that is too low, auto-tuning should increase this to the correct value, which will take effect on the next restart of MSFS. See the Advanced User guide section Auto-tuning of initial start-up ini parameters on how this works, or the following FAQ entry: John

For help with presets, please use the MobiFlight Discord server on the MSFS2020 channel.

Can you please re-download 7.4.18 and re-install and try again please. The build date should read 3rd November, not the 1st. Please check this. You may need to clear your browser cache to download the version again. The initial release of 7.4.18 was accidentally built against the MSFS2024 SDK, but I correct this a day later and re-uploaded but didn't change the version number. Sorry about this. John

Please show me this file as well: C:\Users\marty\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml Yes, but it connected and was working when you did this, although it took far longer to connect than it should. I do not know or understand why simconnect is either not responding or taking a very long time to respond, I can only think that this is due to other simconnect clients, which is why I would like to see a simconnect log file (as this shows all simconnect activity. Not sure why you attached that log file - just shows that you exited FSUIPC after 14 seconds, and there is no additional logging. For the time being, please run with the logging console open (Log -> Open console) and monitor the messages, and only exit FSUIPC if you see that it cannot connect after a minute or so. Also please set the following options in the [General] section of your FSUIPC7.ini file: InitialStallTime=45 DetectToConnectDelayAuto=20 StartUpTuningDoneVersion=-1 TestOptions=x800 This will reset those parameters and prevent auto-tuning changing them (as well as setting the additional logging), This issue seems very different from your original issue. Did this connection problem start recently?

That seems very quick...so when FSUIPC tries to connect, MSFS is in the main menu state. I don't understand why it cannot connect then... Are you doing anything with MSFS, or is it just waiting un the main menu? The log file you attached shows that FSUIPC eventually connected, but took over 3 minutes, and you manually quit FSUIPC after 6mins 25 seconds. That is strange - I don't know why it would do that... You could maybe try with FS Realistic not running 9or auto-started) to see if that makes a difference. Could you show me / attach your EXE.xml file so I can see what else is being started - the location of this file will be logged in your InstallFSUIPC7.log file. I think you will need to activate logging in SimConnect (see that FAQ entry I referenced above) and show me a SimConnect.log file. Once activated, start MSFS and ley everything auto-start. Leave it for a few minutes, and if FSUIPC doesn't connect, exit MSFS and show the the SimConnect.log file (or files), together with your FSUIPC7.log file. They will be very big and will need zipping/compressing. Even after that they will probably be too large to attach and you may need to use a file-exchange service to show it to me. Can you also add the following to the [General] section of your FSUIPC7.ini file please: TestOptions=x800 That will add additional logging around the start-up and connection.

Please show me /attach your FSUIPC7.log file from when you get your issue and close FSUIPC (and before you restart),

What do you mean by this? Do you not see the FSUIPC splash screen when FSUIPC starts? Can you not see the main window after pressing Alt+F? The log file you attached is again showing that FSUIPC cannot connect to MSFS. But I don't understand why it stops after 4 attempts. What other add-ons are you using? Once MSFS starts, how long does it take to arrive to the main menu state? Can you time this please - do the following - start MSFS and time how long it takes from when you see the MSFS window appear (or, better, from when you see the FSUIC splash screen) to when it gets to the main menu state. Also, when FSUIPC starts (i.e. after you see the FSUIPC splash-screen) exit/quit FSUIPC - do this by opening the main window (Alt + F) and then select File -> Exit. - Once MSFS started and has reached the main menu, manually start FSUIPC7. Does it now connect? Exit MSFS and show me the FSUIPC7.log file from this test, - Open the FSUIPC7.ini file and set the DetectToConnectDelayAuto ini parameter to the approximate number of seconds it took MSFS to start and arrive at the main menu. Also set the InitialStallTime ini parameter to 45. - then restart MSFS. Does FSUIPC7 now start and connect ok? Show me the FSUIPC7.log file from this test. If this issue persists, then I may need to see a SimConnect log file, as it seems that FSUIPC is unable to obtain a simconnect connection for some reason. To generate a SimConnect log file, see the following FAQ entry:

No - they would be further away. The max value should be 16383 and the min value -16485. I do not understand what your 'mid' value is though - is this the value when your axis is roughly in the mid position? What do you mean by ' isn't consistent'? You can easily calibrate for the max and min values, and the centre values are only really relevant for certain axes (elevator, aileron, rudder), and you can calibrate for the off-centre mid values by using a calibration slope. Well, you would probably get the full range for a new controller, but you should be fine with those axes values really. Are you having any issues, and if so what? You can also try calibrating your devices/axes in windows (game controllers) first - this may improve the axis range values seen by FSUIPC. John

That should be running as it is in your auto section. But if you think you have an issue with a lua script you should set Lua debug logging, and as you seem to have quite a few lua sript running you shout also set to log lua plugins separately, and each running lua script will be debug-logged to a separate file. Your upload limit will increase the more you post. If its still too large after compression, you will have to use one of the free file transfer services, e.g. filetransfer.io or wetransfer.com. Make sure you also include your latest FSUIPC7.ini file.

I think you mean 'write to' or 'update' not 'configure'. It is FSUIPC that configures the offsets... The easiest way is to update an offset is to use the FSUIPC-added controls that write/update offsets, probably you want to use Offset Byte Set. But your device needs to be seen/visible to FSUIPC to use assignments. Otherwise it may also be possible via lua if its a an HID-type device. Or of using the FSUIPC SDK (in your own software), you can just write/update the offset directly. John

Right-click and select Save as... But here it is: FSUIPC460Francais.zip

By the way, when you change to Files it will move your profile assignments to separate files. If you change back, it does nothing, and so FSUIPC will NOT see your profile-specific assignments.

You also have two [LuaFiles] sections....that can cause issues as you don't know which is being used, and one changed the LuaPath. And the files are assigned different numbers. Determine which is being used and remove the other. You should NEVER touch that section - it is maintained by FSUIPC.

I don't understand your ini...you are using profiles, but it looks like you were previously using profiles-in-separate-files, but no longer as you have: UseProfiles=Yes rather than UseProfiles=Files So most of your profiles are empty, except for your JF Hawk profile. Switch back to using Files to restore your profiles. Also, update your profile aircraft names to use substrings. e.g. change to and do similar for all your other aircraft profile names. When you add an aircraft to a profile, you should always edit the name for the shortest string that will catch all variants and no others, John

Why 'again'? This is your 1st post... What has changed? Please show me/attach your FSUIPC7.log file.

No need. A knob us just a collection of buttons (usually either 1 or 2 in each direction) or an axis. From your ini, your knobs use buttons. Please see my previous reply. You have assigned to the standard FS controls. For PMDG aircraft, use the custom controls. Try logging events (with the logging console open) and turn the knob/knobs you want to replicate. You should see Rotor Brake controls logged with the parameter indicating the function and mouse control applied. You can also use/assign to these - to use the PMDG custom controls via the Rotor Brake control, see That is deprecated as the other method (via custom control numbers) is preferred, but it is still valid and maybe easier to use for inc/dec assignments (which usually correspond to left/right mouse-clicks on the VC control). John

When using PMDG aircraft, many if the standard FS controls won't work - you need to use the PMDG custom controls - see John

Can you also set Debug level logging in the WASM and show me the FSUIPC_WASM.log if this happens again - please also exit MSFS before attaching a WASM log file. Also check the build date in the first line of your FSUIPC7.log file - if this is the 1st November, please download again and re-install. It should say 3rd November. John

This indicates that you are experiencing a WASM crash. Are you using the latest version of FSUIPC, 7.4.18? If not, please switch to that version. If you get the same issue, you will need to disable the scanning for lvars - see the following FAQ entry on this issue: John

What aircraft are you using? Can you please show me / attach your FSUIPC7.log and FSUIPC7.ini files. As a new forum user, you will have a low upload limit, so you may need to compress/zip the files, or use a file-sharing service. Your upload limit will increase the more you post. John

Cam you both check the build date of the 7.4.18 version you are using, on the 1st line of your FSUIPC7.log file. If you see the build date of 1st November:: Then please download again and re-install. It should be: The initial release of 7.4.18 was accidentally compiled using the SDK for MSFS2024. I corrected this but did not change the version number. Note that you may need to clear your browser cache as the initial download may be cached. Please let me know if that was the issue. John

I didn't see this...and there is no such request in your activity. Anyway, check the Documentation section - there is a french translation for FSUIPC4: John

Please see the README.txt file, included in the zip file you downloaded - this section: John

Are you no longer using your JetMax737 throttle or your Alpha Flight controls? If not, you should remove from your ini - I have done this in the attached if you want to use that. FSUIPC cannot see your FMS and is doing nothing with it... However, it has been reported that sometimes FSUIPC's calibration can affect the PMDG737, although this is usually the climb rate and nothing related to the flight plan. Anyway, I have also removed unneeded calbration entries in the attached ini, so you could try that, If you get the same issue, try switching your assignments to use 'Send to FS as normal axis' rather than 'Send direct to FSUIPC calibration' and remove/reset any and all calibration settings, You also attached the log file when FSUIPC was srill running, and it ends after 31 seconds and so doesn't show much. Please show me a log file generate when you experience your issue, and ALWAYS exit FSUIPC before attaching files. John FSUIPC7.ini

Your files are a bit strange,,, First, you have disabled the WAPI: Why have you done this? Your log indicates that you had assignments to presets: but I can't see any assignments to these in your ini, but you do have (now invalid) assignments to custom control 0: Maybe these were assigned to presets, and as they are no longer available they have been removed - although this shouldn't really happen... I will check this. Also, please use substrings for your aircraft profile names, i.e. change to This will prevent issues with your profile not loading when you use a different variant. As for your actual issue, I cannot help with this as this is done by the CPFlight driver/software, so you need support from them really, and I do not own or have access to any CPFlight equipment. There are other CPFlight / FSUIPC users who may be able to help - maybe @fischkarl, @ppatys or @Ron Vogel can help?