
John Dowson
Members-
Posts
13,180 -
Joined
-
Last visited
-
Days Won
269
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by John Dowson
-
This is not actually correct anymore, but was correct on initial release, and should really have been 'when MSFS starts FSUIPC7 via the EXE.xml file'. However, now that the default auto-start has been switched from using the EXE.xml file to the MSFS.bat file, it should be: “Please note that this feature is only activated when using the auto-start facility, either via the MSFS' EXE.xml file or the FSUIPC' MSFS.bat file (via the Desktop icon)” This is all explained in the latest FSUIPC7 Advanced User guide (for 7.4.12) which I have attached below. If you remove the DetectToConnectDelayAuto ini parameter, auto-tuning will run automatically, no need to add the StartUpTuningActive ini parameter. Otherwise, you can leave the DetectToConnectDelayAuto ini parameter and add StartUpTuningActive=Yes to force auto-tuning. Only if it is needed. If you are using auto-start via the MSFS.bat file / FSUIPC 'MSFS' Desktop icon, then you must use this to start MSFS (and FSUIPC7) as this is where the auto-start component is. If you are using the EXE.xml auto-start method, then it doesn't matter how you start MSFS. Basically it is active if auto-started and not manually started via using the FSUIPC7.exe. Why don't you take a look at your log file as this will log auto-start activity. Looking at the log you attached, this shows that FSUIPC7 was auto-started and auto-tuning was active: Note your log file ends after 70.89 seconds and was attached while FSUIPC7 was still running. Auto-tuning terminates and updates your FSUIPC7.ini when MSFS gets to the main menu (and FSUIPC7 is connected at this stage). What is happening in your case is that you are getting to the main menu, selecting a flight and starting the flight before FSUIPC7 is connected. Therefore FSUIPC7 is not detecting MSFS in the main-menu state and so not updating the auto-start parameters. However, it WILL do this once you terminate your flight and go back to the main menu. If you exit before doing this, auto-start will just activate the next time that you run MSFS. If you want auto-start to do its job, you can always wait for a short while (until FSUIPC7 connects) when you get to the main menu to allow this state to be detected by FSUIPC7. 30-40 seconds should suffice. Anyway, I really wouldn't worry about this to much. Your system loads pretty fast, and the auto-tuning process will do its job and probably reduce the DetectToConnectDelayAuto parameter to either its minimum or until it detects an error, and then increases it again. Note that I will release 7.4.12 when SU15 is released. It is already available from the Announcements sub-forum if using the SU15 beta. John FSUIPC7 for Advanced Users.pdf
-
But you don't! As your log file that you attached states, you are running from C:\Users\dhsim\Desktop\MSFS\FSUIPC7\ as this is where the FSUIPC7.ini file is read from. I am taking this from the files you attached. This is why it is still loading the C510.ini as you are editing the wrong FSUIPC7.ini file. I'm sorry but this is all very confusing for me. As I suggested, please use File -> Open Installation folder which will tell you where FSUIPC7 is running from, and from where it is reading the options. ALWAYS show me files form that location (i.e. where it is actually running from, not where you think it is running from). You need to sort out your locations and provide me the correct files if you want support. You should only have one FSUIPC7 installation folder - remove all others. Please do not attach any more files or ask for support until you have done this as it is confusing and time-wasting doe both of us. Sorry, but I have no idea what this means. What is stacking, and what variables? If you are referring to why the UI is grayed-out when you have overloaded assignments (i.e. more than one assignment to a button or key) then this is just the way the UI was designed many years ago. It is just not possible to use the current UI to add overloaded/multiple assignments to a button or key, and you have to edit the ini to achieve this. Once this has been done, it is not possible to show this in the UI, hence it is grayed-out. This also applies when you add compound or offset conditions. Again, you cannot do this via the UI and hence you cannot edit such an assignment via the UI for such assignments and so they will also be shown as grayed-out. In a perfect world I would modernize and update the UI to allow such things to be achieved via the UI rather than having to edit the ini. But that would be several months development work, and I just do not have the time for this. It is what it is and has always been this way.
-
These are assignments for the End key to switch between cockpit and external: I have checked the insert key and it should work fine. To use this to switch between cockpit camera and drone camera, you can use the following: Try those and adjust as needed. Let me know if you have any issues. If you want to use other camera views or states, try logging those offsets I mentioned and see what values are used for the views you want to be able to switch between. See the offset status document for what the values held in those offsets mean. Also, maybe check-out these similar requests: John
-
I have checked this here now and it is working as expected. Did you solve your issue? I expect it is/was due to the lua script not running... John
-
There is currently no radar or associated functions provided by AS - basically there is no dll and so no dll functions to communicate with AS. This is currently being worked on by AS. I believe there is a HTTP interface but I cannot find any documentation on this. I have asked AS about this and will take a look and see what is available / possible once I see the documentation and will then get back to you.
-
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.
-
Can I use this with the mode switch on my X56?
John Dowson replied to bahnzo's topic in FSUIPC7 MSFS
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?
-
MSFS, Blacksquare Analogue B350, PMS GTN750 and FSUIPC7
John Dowson replied to ThePenguin's topic in FSUIPC7 MSFS
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
-
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!