John Dowson

All the FSUIPC documentation is installed (optionally for FSUIPC6/7) when you install FSUIPC. If usingFSUIPC6 or 7, then they will be under your windows documents folder in an FSUIPC6/7 subfolder (v7.0.4 also creates a link to this location under your installation directory). For FSUIPC4/5, the documents will be under an FSUIPC Documents sub-folder of your FSUIPC installation folder. The FSUIPC documentation is also available for download as a separate package here (although these won't be up-to-date): John

I cannot help as you do not supply any information, such as your FSUIPC7.log file. However, if MSFS is crashing then you are probsbly experiencing this issue: Asobo are aware of this and we are waiting a fix. Please check for similar problems before creating a new post/topic. John

Please see this topic: Asobo are aware of the issue and we are awaiting a fix. This topic is now locked. John

@imagecrafting There is an updated FSUIPC4.dll attached to the last comment in this post, if you could try that to see if it works with your joysticks disconnected: John

I see Pete has responded. The button presses in your log are assigned to toggle a lua flag for that script, which is why they aren't working. Correct that script and try again. John

There are several posts topics on this now, and still nothing has changed. Please check for existing topics for the same issue before posting a new topic. For example, see or John

In the latest version of FSUIPC7, v7.0.4, FSUIPC7 is started from the MSFS EXE.xml file. If you don't want it to start with MSFS, edit that file and remove the section that starts FSUIPC7. If you don't use it to start any other programs, you can remove the file completely. For MS Store installs, it should be located under your AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\ folder. For Steam installs, its under AppData\Roaming\Microsoft Flight Simulator. John

Yes, sorry - forgot to attach. Here it is: FSUIPC4.ini John

Note that there is now a new version, v7.0.5c and the offsets for these new items has changed slightly. Please see the following for details and to download the new version: John

Ok, then thats the correct driver for your device, but you have probably placed it into the wrong installation, unless 'FSUIPC for MSFS' is your FSUIPC installation folder. If you are not sure where you installed FSUIPC7, you can use the File -> Open Installation Folder option from FSUIPC, which should show you the folder where the PFCcom64.dll should go. Yes, please download from www.fsuipc.com. Also check that you are using the latest version of FSUIPC7, which is v7.0.4. I see Pete has also replied... Not quite true. It is loaded during FSUIPC initialisation even without MSFS running, and you should see this in your log file after the LogOptions are logged: 703 Loaded PFCcom64.DLL okay! However, the PFC menu entry and initial dialog box will not be displayed until connected to MSFS AND you have an aircraft loaded. John

Can you check that again please - I get 1 or 2 in that offset directly... In the attached version, v7.0.5c, you have (note the offset changes!): 0x0290 4Bytes AUTOPILOT ALTITUDE SLOT INDEX Read/Write 0x0294 4Bytes AUTOPILOT HEADING SLOT INDEX Read/Write 0x0298 4Bytes AUTOPILOT SPEED SLOT INDEX Read/Write 0x029D 1 Byte APU SWITCH Read Only FSUIPC7.exe Do you know if there a control/event I can use for this? If so, I can make 0x029D also writable. I've previously read that its tricky to do this, but some have had success with lua. e.g. from here: John

@mermoz33 I have noticed the following in this post: Maybe try that, or ask the OP how he did this via lua. John

But the CTD is for MSFS, not FSUIPC7. This is why you need to report to Asobo. not me. I cannot do anything with MSFS crash reports. FSUIPC7 is an exe, and should not cause MSFS to crash - if it does, its a problem with MSFS. Of course, if it was a CTD of FSUIPC7, then I would investigate. So, Asobo are aware and are looking into it. There isn't anything i can do. John

What type of device do you have - hid or com/serial? What is the 'appropriate PFC file' you are using? The PFC dll should go into the FSUIPC7 installation folder, not the MSFS2020 folder. If you don't know where that is, startFSUIPC7 and use the File -> Open Installation Folder option. Not also that, if using the PFC com driver, this was updated this morning so you should download the latest version. The issue for this update is described in this post: John

Sorry, but I cannot read your images. Please describe your issue - what offsets are you trying to read/display, and as what? You are most likely using the wrong type, but I cannot tell from your images. If in doubt, please attach you FSUIPC7.ini file and I'll take a look. Most of the electrical offsets are 8 bytes (64bits) (except for ELECTRICAL MASTER BATTERY which is 4 bytes, 32bits). You look to be trying to display them as S8, which is a signed byte (8bits). Please see the Monitor Facilities section in the FSUIPC7 for Advanced Users document (P13) for a description of the display Type codes. I suspect they are FLT64 types. This is how the title bar display works - it will only show the last updated offset. John

The config that should work is when you get the CTD. Very strange. I think the other solution should work though, which is: - remove the start of FSUIPC7 from the EXE.xml - use FSUIPC's [Programs] section to start TrackIR - set FSUIPC7 to run with administrator privileges - re-enable the start of FSUIPC7 from the MSFS.bat file (as described above) Then, if you use the desktop link to start MSFS with FSUIPC7, this will start MSFS without admin privileges and start FSUIPC7 with them, which will then also start trackIR. John

First, when you provide files, can you always give me both the latest FSUIPC4.ini and your FSUIPC4.log. I always need to see them together (and sometimes the Joyscan.csv file). You didn't respond to this. This is important as I need to know what assignment is assigned to what device. For example, your P3D A320 axis profile has your aileron, elevator and rudder assigned to device 1, your T.16000M - is this correct? There is also an error in your My320functions.lua that needs correcting: 241771 *** LUA Error: ...Users\Rich Dogg\Documents\Prepar3D v4 Add-ons\FSUIPC6\My320functions.lua:188: 'end' expected (to close 'function' at line 121) near '<eof>' And your latest log shows that you have event logging activated, but not Buttons & Keys, as requested - but I cannot confirm as you didn't attach your FSUIPC6.ini file. So, to be clear, please do the following: - correct the error in your lua script - let me know if your axes assignments are assigned to the correct device or not - change AutoAssignLetters=No to AutoAssignLetters=Yes in your FSUIPC6.ini - disable Linda (temporarily) by renaming your linda.lua file - start P3D/FSUIPC6 and load the Aerosoft A320 professional UNITED AIRLINES N449UA - activate logging for events and buttons and keys in FSUIPC6 - press one of your assigned buttons - Stop P3d, and show me your latest FSUIPC6.log and FSUIPC6.ini files John

Ok - so 2 WAS (not P2 - P is just for 'press') your wingman. However, this is now device 3. 3 couldn't have been a GoFlight module - these will have ids >= 100 (if loaded using the GF driver) - or is it a standard HID joystick device? Anyway, please try the attached FSUIPC4.ini (save your current one please). In this, I have removed all assignments to your '3' device, moved your assignemnts from your '2' device to '3'. and set the winfman to be device 3. With this, your 2nd yoke should now hopefully be recognised as device 2. Please try this updated, run FSX to see if you can now see and assign to your second yoke, and check if your existing assignments still work, especially for the Wingman. If you have any issues, please attach your updated FSUIPC4.ini and FSUIPC4.log files, as well as your JoyScan.csv file. John

You can still use the Modules folder id you wish, but still better to install outside of the LM folder really - and outside of windows protected folders, like Program Files. You did say it was installed in the LM top-level folder, not the Modules folder. Anyway, the file must have the extension .mcro. That file has .MACRO.txt John

Really? You installed FSUIPC6 in your top-level LM folder? I would advise against that... Did you check your FSUIPC6.ini file? Please attach both your FSUIPC6.log and FSUIPC6.ini files and I will take a look. John

Please see the FSUIPC User Guide for the additional features provided by the payware version. The FSUIPC SDK applies to the free as well as the payware version. FSUIPC's Lua interface is only available in the payware version. As for MobiFlight, I'm not a MobiFlight user and so will leave to others to respond, or ask on the MobiFlight forums. If you are just using the MobiFlight WASM module, you should be able to use the MobiFlight added events via code as custom controls. But you cannot assign directly unless using the registered version/ John

First, you posted in the User Contributions sub-forum where it explicitly states NOT for support requests. I have moved your post for you, but please take care in future to post in the correct forum. Are you sure that is you FSUIPC installation folder? You can verify this by using the 'Open Folder' button in FSUIPC's Logging tab, which will open a windows explorer window on your FSUIPC installation folder. Try that and see if you can see your macro file in that folder. I suspect not! Also, when FSUIPC6 detects a macro file it will add it to the [MacroFiles] section of your FSUIPC6.ini file. Do you see anything there? If not, you will not be able to assign to it. Note that it does this automatically - do not manually edit that section. John

If you mean ProvideAIData=No, then that goes in the [General] section of your FSUIPC7.ini. Please see the Advanced User guide. John

The mouse macro should emulate the mouse click, so it is very strange that they give different results. And also weird that assigning to keys doesn't work, as that was reported as a possible solution in that thread on the PMDG forums. Sorry, but I'm out of ideas on this one. Maybe try posting on the PMDG forums to see if any one else has had this issue and has found a workaround. John

The latter. But if you can always do the other option - rename your linda.lua to linda.lua.unused (or whatever new name you want to give it). I just want to know that Linda isn't doing anything behind the scenes. Its probably not related to your issue, but always better to eliminate (at least temporarily) when investigating an issue. I'll look at your new log tomorrow.