All Activity

Why not just uodate? It only takes a few minutes... Otherwise check the documentation or search this forum...I am sure this has been asked before... I think the OpenOnStart (or similar) ini parameter set to Never may prevent this, but I am not sure... I am on holiday now until next week, and can check further then. John P.S. Please use the FSUIPC7 sub-forum for all questions/issues with FSUIPC7. I have moved this post.

The GUIDs of your devices have most probably changed. To redolve this, you need to update the [JoyNames] section in your FSUIPC7.ini file. New letter entried will have been added to that section. You need to copy the GUID strings from the new entries and use those/paste them in the original letter entries, then delete the new letter entries. Do this when FSUIPC is not running. If you attach your ini file, I could do this for you. But I am now on holiday and cant do this until next week (difficult on a phone!), so please try yourself. Any issues, attach your ini and I will take a look when possible. John

*** Moved to FSUIPC7 support sub-forum *** Hi there, is there a way to somehow disable the update popup message / check, if I would like to keep an older version for a while? Thanks

Hi I have recently had to do a clean install of Windows 11 and also MSFS2020. That's all gone fine. I had saved my config file for FSUIPC which contained all the settings for binding the buttons and switches for my Hotas Throttle and stick for the Fenix A320. However, when I have transferred my saved config file back into the fresh installation of FSUIPC 7.5.3 the bindings are not being seen by FSUIPC and all the button/switch assignments are blank. Hope you can help. Regards Barry

Then MSFS2020 was not detected. Please show me / attach your InstallFSUIPC7.log file. You should ALWAYS attach this if you have installation issues.

I just installed FSUIPC7.5.3 and it removed MSFS2020 as well as MSFS2024 but only reinstalled MSFS24 (MSFS2020 did not reinstall), there was no option to choose one or both.

I don't understand why you keep messing around so much with your devices and creating such a mess. Looking at you registry, you have all these entries: and the log file is reporting duplicate ids: You need to do exactly the same as I suggested the last time this occurred - clean your registry and update the GUIDs to the new ones on your assigned JoyLetters, and remove the other entries. Sorry, but I just don't have time to look at this in any more detail at the moment (and I am on holiday from the 2nd - 7th April). I can help again sometime later next week, but I am just too busy to look at this in detail at the moment. Go over the last post and try and understand what you did to resolve it the last time. Report back after the 8th AApril if you require further assistance.

Thank you for your support! Kind Regards, André

Ok, that probably changed with the SU1 update - that offset holds the version number (major*10 + minor) as received from the FS. I will update the documentation to reflect this. Thanks for reporting. John

The documentation for v7.5.2 states that 0x3124 will hold 120 for MSFS2024, however it actually reports 121 when connected to the sim. I don't know when this may have changed as I've just installed MSFS2024 today. Gerard

Part1: So I have added a new device (vector one rudder) 2 weeks ago and flown with it for at 2~3 legs in P3D(and far more in other sims) without issue. OK, no big deal, restart P3D, not good, restart PC, no good, unplug all joystick, start P3D, plug them back one by one, all others work, but not MJOY32. (again, hardware works fine as well as in other games, even in P3D's own input system and linda (EDIT: I realize all my previous flight this device is assigned by LINDA, so it could have been failed in FSUIPC as soon as new rudder added) Today I noticed my homemade MCP (MJOY32) not working in FSUIPC again. Under frustration I start MMJoy configure tool and update it's firmware VID and PID form 8888,8888 to 7777,7778, reconnect, and now it recolonized, reassign the joy Letter and after 2 hours I'm finally ready to go. BUT, in the middle of flight, after pushback, I noticed some other device have wrong letter assign, so I went to ini and changed that, reload button, and take off. Then I noticed my MJOY32 stopped been recognize again..... Tried rename it back to 8888,8888 (thus I don't need to reconfig my other games anyway.) still no good.... FSUIPC6_lostMJ32.zip FSUIPC6_2ndstartafterlos.zip

Before buying, try the trial license in the first post in this forum. This also includes a trial license for WideFS7. It will expire after tomorrow, but I will update in a few days (and you will need to download and install again). Always better to try it first to make sure it suits your needs (as no refunds available!). Cheers, John

Thanks !!! So I'll buy a license for FSUIPC7 and a license for WideFS7.

Ok, thanks for the update. That is strange though, especially as those controls are being sent so early.... I will look at the Sim Rate offset 0x0C1A when time permits, as this is still documented (and implemented) for FSX (same as in FSUIPC4) and will almost certainly have changed... Anyway, glad that is now solved! Regards, John

Hi John, sorry for the late reply. I think i found the issue: I've had buttons assigned for time acceleration. 301=PG,13,Cx02000C1A,x0100 -{offset word set, offset 0C1A}- 302=UG,13,Cx02000C1A,x0400 -{offset word set, offset 0C1A}- 303=PG,12,Cx02000C1A,x9600 -{offset word set, offset 0C1A}- 304=UG,12,Cx02000C1A,x0400 -{offset word set, offset 0C1A}- When starting up FSUIPC, this would (sometimes) trigger fsuipc to continuously trigger the event: SIM_RATE_INCR continuously. Since i assigned a press and not repeat function, i don't quite understand what i did wrong here? You can see the event happening in the attached log file. After removing the above entries, the problem stopped. Kind Regards, Andre fsuipc.zip

FSUIPC5 is for P3Dv4 only, not FS2020. Only FSUIPC7 works with MSFS2020. Do you mean offsets 0x9002 and 0x9006? Those offsets are not (and never have been) used by FSUIPC itself. Looking at the code, offset area 0x9000 - 0x93FF has been allocated to "Nico Kaan for Lekseecon(Level D 767, 757)". I have no idea who this is or what these offsets are supposed to do - they were allocated way before my time. All I can tell you is that they are not used at all by FSUIPC. John

Hello, I automated a throttle by adding two 12V DC motors via an FDBUS card. I declared the output command values as 0x9002 ( 16U) and 0x9006(16U) in Prosim737. When I launch FS2020, I look at the FSUIPC log and see that my values 9002 and 9006 remain at zero even though I move the throttle levers. before I used FSUIPC 5.134 with FS2020 (I think) and it worked but not anymore. before I used win10 and now win11. I checked the firmware and updated VC++ but nothing changes, the values remain at zero Question : The variable 9002 and 9006 are used for something else ? Any idea ? Thanks in advance Lamine

When FSUIPC7 starts, you should see a splash-screen displayed for a few seconds which tells you it is running. If you don't see that, then it hasn't started. When it is running, it will be n your system tray and you can open the main window from there, or use the (default) hotkey combination of Alt+F. If it is not running, try starting it manually to check it is installed correctly and working, i.e. double-click the FSUIPC7.exe in windows explorer. If it does not run, you may need to update/.install the correct VC++ redistributables - see the README.txt for details. If it is not auto-starting with MSFS (and you have selected to install an auto-start component), see the following FAQ entry: John

Your ini file shows that you have assigned your throttles to the Y axis on your Saitek Pro Flight Quadrants (devices D and E): But the images you attached show Throttle1 assigned to the Z axis. Therefore the images and ini files don't seem to match. (Also, please make sure that you have exited FSUIPC7 before attaching files). I think what is happening is that when you are moving the axis you want to assign to the throttle, another axis is being detected first. This can happen, and when it does you can either click Clear to start again, or Ignore Axis if the same axis keeps getting detected. Check the In/Out values are changing once the moved axis is detected - if they stop changing (or only change slightly) then a different axis has been detected and you need to try again, Also, why are you using a delta value of 1? That is extremely low and is not recommended - the default value of 256 should be sufficient, so just use that for now and only update if you really need a finer resolution, and reduce in stages (e.g. try 200 first, then maybe 175, etc). But 256 should really be sufficient resolution when you have a 32768 value range. So, I would again delete any axis assignments to throttle (as well as those empty assignments) and try again. Delete these when FSUIPC7 is closed, or when the axis assignment panel is open and click Reload all assignments afterwards. And then re-assign following what I have said. That is ok and how it should be. You are assigning with no reverse zone, so the axis range of -16384 to +16384 is calibrated to the forward thrust range of 0 to 16384, so when the axis is at position -16384 the actual axis value that should be sent is 0.

If you mean the FSUIPC profiles folder, this is only created/used if you are using profiles-in-separate files. This is not active by default and all your profiles are kept in the FSUIPC7.ini file. If you want to use profiles-in-separate files, you have to manually changed the UseProfiles ini parameter setting to Files (as it says in the documentation).

**** Moved to FSUIPC7 support sub-forum **** I have downloaded FSHUB and it needs FSUIPC7 for FS2020. Everytime i am running FSHUB it says and it has not detected FSUIPC7. Multiple places show me that FSUIPC7 has to be running in the tray bar but is not there. I have tried uninstalling and installing it again and does not solve my issue. Any help is greatly appreciated

I didn’t see a profiles folder like in documentation.

Still weird things happening. Deleted the places you said and started over. With the new setup Throttle 1 works, n#. 2 doesn't move. And in the Joystick Calibration picture there is a big difference between In and Out on 1 and 2. FSUIPC7.ini Axes.rtf

What lvar? Lvars are aircraft specific - check any documentation for the aircraft you are using, or list the available ones. I asked if there was a simvar available for this - I don't know of any, and couldn't see anything in the Asobo documentation. If YOU can find where this information is held, then I can look into adding it. I couldn't find anything when I looked before. As far as I know, this info is only available for AI aircraft with the simvar AI Traffic State, which has the following values: char states[28][32] = { "STATE_WAIT_FOR_ENGINE_START", // 0 "STATE_SLEEP", // 1 "STATE_FILE_FLIGHT_PLAN", // 2 "STATE_IFR_CLEARANCE", // 3 "STATE_PUSH_BACK_BEGIN", // 4 "STATE_PUSH_BACK_CONTINUE", // 5 "STATE_ENGINE_START", // 6 "STATE_PRE_TAXI_FOR_TAKEOFF", // 7 "STATE_TAXI_HOLDSHORT", // 8 "STATE_TAXI_ONTO_RUNWAY", // 9 "STATE_TAKEOFF", // 10 "T&G depart", // 11 "STATE_ENROUTE_AS_FILED", // 12 "STATE_TRAFFIC_PATTERN", // 13 "STATE_LANDING", // 14 "STATE_LANDING_ROLLOUT", // 15 "STATE_GO_AROUND", // 16 "STATE_TAXI_TO_PARKING", // 17 "STATE_ENGINE_SHUTDOWN", // 18 "STATE_SUPPORT_PREFLIGHT",// 19 --> 0 "STATE_SUPPORT_POSTFLIGHT",// 20 --> 18 "STATE_FLY_UNTIL_NEXT_EVENT", // 21 non ATC AI --> 12 "STATE_TAXI_FOR_TAKEOFF", // 22 non ATC AI --> 8 "STATE_TAXI_TO_REFUEL", // 23 non ATC AI --> 7 "STATE_WAIT_FOR_ENGINE_SHUTDOWN", // 24 non ATC AI --> 18 "STATE_WAIT_INIT_CONFIRM", // 25 --> 0 "STATE_SIMPLE_TAKEOFF", // 26 -> 10 "STATE_SIMPLE_FLIGHT", // 27 -> 12 }; Presumably you are supposed to know the state of the aircraft you are piloting....! This could be useful for external programs though - you could ask on the Asobo forums about this.... John

Rather than delete the existing assignments, just create a new (empty) profile for your devices/controllers if you are assigning in FSUIPC. Looks like MSFS2024 handles things differently though. Duplicate your existing profile, giving it a new name (e.g. FSUIPC). You should then be able to clear that profile, or just delete the things you want to assign in FSUIPC, John