John Dowson

Thats very strange, but interesting...I have no idea why that works...!

MSFS profiles are not associated to an aircraft. If its FSUIPC profiles you mean, then these have nothing to do with MSFS - they are loaded by FSUIPC. The usual reason that a profile isn't loaded is that the aircraft name has changed (this happens is you use a different livery or version) and you are using a full aircraft name rather than a substring to match the aircraft name to the profile (under the [Profile.xxx] FSUIPC7.ini file section). This cannot be correct - FSUIPC cannot associate an aircraft to a profile without a match with the aircraft name in a [Profile.xxx] section. Are you sure you edited a file in the correct location? When FSUIPC7 is running, try File-> Open Installation folder to see the installation folder. Looking at your log file, you are running FSUIPC7 from a folder on your Desktop It is not a good idea to install FSUIPC7 there - you should consider re-installing in another non-windows folder. Are you sure the ini file you attached is the one from that folder? What is a PMDG radio button? This makes no sense. Note the controls are grayed-out if/when your assignments are overloaded, i.e. you have more than one assignment on the button. Looking at your C510.ini file, you have many overloaded assignments, so I expect that is the issue here. I looked at this quite a while ago - please see That was quite a while ago so things may be easier, but please read that thread and try what is advised there. Any further questions on this, please use that thread, not this one. Not really...can't just ignore it? This is information that I need to see for support purposes when looking into issues for support requests, and I see no reason to remove this. Why do you want this removed anyway?

No - there is no such section, and no need for such a section The documentation on comments in the buttons section states (from Advanced User guide): So that line comment may be moved - and also comments should go before the annotations added by FSUIPC. So use either or (better, IMHO) Note that ini files are a windows construct that FSUIPC uses (FSUIPC adds the indexing), and the # symbol is also indicates a comment line, and it looks like this holds position, so also maybe try: For example, these comments are kept: See https://www.w3schools.io/file/ini-comments-syntax/.

Wow - I am surprised that ChatGP can do that! Looks good. Note that it is generally easier to use macros to cycle through lvar values (ie. use a macro for the lvar with the Cyclic action), but this only works if the values start at 0, so you would need to use a lua script for an lvar that has values that start at any other value.

There is an issue in 7.4.11 where the PMDG threads are not starting correctly in some circumstances, fixed in 7.4.12 - see This is the PMDG issue that is addressed in 7.4.12. However, this will not be causing any freezes. The PMDG WASM crash? FSUIPC has nothing to do with this - it uses its own WASM. Ok - please update if you find out anything. Cheers, John

There are no standard controls for the camera. You can use the camera offsets 0x026D - Camera State 0x026E - Camera Substate 0x026F - Camera View Type and Index:0 0x0270 - Camera View Type and Index:1 However, it may be easier to use the presets - look under All Vendors -> All Aircraft -> Camera. They are not toggle controls, so you will have work out how to do this yourself. For example, to switch between cockpit camera and external camera, you would need to assign to both the presets External View - Default Pilot View - Normal and then add an offset condition on offset 0x026D. Give it a go - I can help further if you have problems, but I won't have time until the weekend at the earliest. 'insert' (or 'VK_INSERT') is a valid key string and is requested just the same as all other keys, so not sure why this isn't working. I will check this here later. John

There shouldn't be... Is the lua script running? Can you please show me/attach your FSUIPC7.log and FSUIPC7.ini files. the latter with Lua Plugin logging activated.

Read the documentation again...should be: 59=CP(+E,134)E,29,CPPMDG_B737_MCP_HDG_INC,0 60=CP(+E,134)E,30,CPPMDG_B737_MCP_HDG_DEC,0 i.e. no ,P after the offset condition.

Have you? Then I must have answered often, so why ask again? This depends on the section., You can certainly add comments to button and key assignments and they are not deleted. I think I recently allowed comments in the [Auto] section see I am not sure about other sections - which sections are you referring to?

This implies that when you are updating the PMS GTN750, it is somehow corrupting FSUIPC7. I am not sure how it can do that, unless it is overwriting something in the FSUIPC7 installation folder (or community WASM folder). You should maybe report this to the provider of this software. Note that uninstalling via the windows app managemtn panel simply calls the FSUIPC7 uninstaller. You can just re-run the installer without uninstalling first, and this will do the same. John

Why do you think this has anything to do with FSUIPC7? Both log files show no issues (with FSUIPC7), and that FSUIPC7 was running and exited normally. One log file does show some errors though - looks like MSFS crashed after 10899 seconds (just over 3 hours).

I really don't understand your issue - all download links are working fine here, both from the SimFlight download section of this forum and from fsuipc.com. Note also that all links link to the same downloadable files, and all are on the SimFlight server, so I really can't understand why you have issues.

This file is installed by default - if its not installed, then you must have de-selected it during the installation process. The MF presets are extremely useful - you should install this file. Not sure what file you are referring to, but if you have the beta installer then yes, run this again and re-install. You could download the latest 7.4.12 release, but this is built using the MSFS SDK for SU15, so better to wait until this is released before installing that, unless you are already running the MSFS beta version. Once re-installed, please try again. Any issues, please attach your FSUIPC7.log file and the InstallFSUIPC7.log file. If you previously installed using that installer, the uninstaller may not remove the EXE.xml file entry for FSUIPC7 - check this after installation and remove manually if needed. John

Note you can also try/use https://www.fsuipc.com/

Did you install the 7.4.12-beta using the installer or by downloading and replacing the FSUIPC7.exe? The auto-start method for FSUI{C7 has changed between 7.4.11 and 7.4.12. In 7.4.11, the MSFS EXE.xml file is used - the installer adds an entry to the EXE.xml file (or creates this file if not already available) to start FSUIPC7 via MSFS. In 7.4.12, the MSFS.bat file starts FSUIPC7 after a pre-defined delay/wait after starting MSFS - the console window will be created (hopefully iconised) and is visible when the bat file is running, i.e. for the delay period between when MSFS is started and when FSUIPC7 is started. Looking at the log file you attached, FSUIPC7 IS being started via the EXE.xml file: So it looks like FSUIPC7 is being started both via the EXE.xml and via the MSFs.bat file. You should use one method only. If you installed FSUIPC7 via the installer, it should only implement one auto-start method. I don't know why you have two enabled - you need to remove one. The easiest way to do this would be to download and install the full release of FSUIPC7 v7.4.12. Otherwise you either need to manually edit the MSFS EXE.xml file to remove the FSUIPC7 entry (or delete altogether if not used by anything else) or comment-out the start-up of FSUIPC7 from the MSFS.bat file. The location of the MSFS EXE.xml file will be logged in your InstallFSUIPC7.log file. and the MSFS.bat file will be in your FSUIPC7 installation folder. Sorry, but I do not understand this. The log file you attached shows that FSUIPC7 is running as a registered version: from the folder D:\MSFS Programs\FSUIPC. If that message is logged, I cannot see how you cannot have access to the Assignments menu... How come you have opted not to install the MF presets file: ?

That message should be self-explanatory - FSUIPC7 was already running when you started MSFS via the FSUIPC7-installed MSFS.bat file. What do you mean by this? Was FSUIPC working before you closed this error message? Why was FSUIPC7 running already anyway? Perhaps it is being started both via the EXE.xml and via the MSFS.bat file? This implies that you are using an unregistered/unlicensed version of FSUIPC7. Do you have a license, or are you using the trial license? If the latter, then this probably expired after 1st May. There is a new one available, valid until 1st June, but if you have already tried the trial license, you should either purchase or forget. Re-installing FSUIPC7 will not do anything, so no - if you are on a version before 7.4.11 (current released version) then re-install. Looks like you are using a 7.4.12 beta, so don't re-install unless you want to go back to 7.4.11 or update to the 7.4.12 official release (see below). Note that I have now released 7.4.12, but this is for the SU15 beta release of MSFS (1.37.17.0 and later). It does work with the current MSFS release (1.36.2.0), but I cannot guarantee the stability with this version as it is built using the MSFS SDK of the SU15 release (0.24.2.0). This is available here: For any further issues/questions, please attach your FSUIPC7.log file. John

To disable controllers in P3Dv5, uncheck Enable Controller(s) under Options -> Other Controls. John

Not sure what you mean by this - the download links work perfectly fine here (using Chrome). What browser are you using? If having issues, try right-clicking and select 'Save link as...'.

Thats interesting - and a reasonable sounding but completely made-up answer!

If you have purchased a license, your registration/key details will be in the purchase receipt email, and also available in your SimMarket account. If you have not received the purchase confirmation email, this is an issue for SimMarket. Alternatively, if you have not yet purchased a license, you can try the trial license, available from here: That is because you are using an unregistered / unlicensed version, i.e. you have not registered a license and so only the freeware facilities are available. John

That is strange - filtering should in no way affect the yoke sensitivity- that is what the sensitivity curves/slopes are for, as you say. What 737 and version of FSUIPC are you using? You can try activating logging for Axes Controls and open the logging console window. If you do this and then move the elevator, you will see the elevator axis control/event logged, together with the value (the parameter), Try this with both filtering enabled and disabled - you should see the same value/parameter sent when the yoke is in the same position regardless of whether filtering is active or not. If your elevator axes isn't spiking, there should be no difference. John

The Filter option only suppresses large fluctuations in short time frames. and is meant to be used if you have a jittery axis (some older/warn devices can send unwanted spikes in axis values). There should be no performance change when using this, so it surprises me that it is less responsive with this option enabled. Having never flown a real boeing 737, I would not be able to answer this. Cheers, John

Sorry but I have no idea - I have not heard of this panel and do not know how it uses FSUIPC7. You need to ask the panel providers, i.e. javasimulator.com. If the panel software is using FSUIPC to drive the push-button indicators, I would need to know what aircraft you are using and what offsets are being used (by the panel software) to determine the push-button state. I doubt this - just having the paid version will make no difference, unless the panel software uses some of the registered facilities (e.g. lua), but the panel provider/documentation should say if you need the registered or free version of FSUIPC7, You can also try the full version - there is a trial license available in a post at the top of this forum (i.e. the FSUIPC7 support sub-forum, not the main support sub-forum). Regards, John

@GeorgeBarlow Sorry for the delay. I did ask Pete about this when he got back from his holidays, and he says he has no technical references of any Cockpit Sonic hardware. Many years ago he developed a driver for a 737 forward overhead from CockpitSonic for ProSim, but has no experience with any other hardware from CockpitSonic, and that was a long time ago. Sorry I (or Pete) can't be of more help. John

That is the console window for the bat file. That is created but should be iconised, i.e. in your system tray. That window will stay around until FSUIPC7 is started, but if you kill that window, then FSUIPC7 will not start. Does that window actually show, or are you opening it from your task bar? If you just leave things and wait, you should see that console window disappear and FSUIPC7 will then start. Also, please post in the correct forum for support, which for FSUIPC7 is the FSUIPC7 / MSFS sub-forum - I have moved your post. John