John Dowson

Which aircraft are you using? If its a default one or an add-on that I have then I can check here for you. Otherwise, you can try logging axis controls, operate the toe brakes in the UI and see if anything is logged in the FSUIPC7 console window - if you open the console window you can see what is logged as you activate the toe brakes in real-time. John

If you add the lvars to offsets, you could use the Offset monitoring facility to log the lvar changes (to the console or MSFS title bar). As the simconnect text display facility seems to be permanently broken, I am considering changing this to allow logging to be displayed in a wnd window. I could also look into adding specific lvar logging - I will add this to my list of new features to look into. You can use hvars via executing calculator code or via presets (which are also executed as calculator code), but such hvars are not known to FSUIPC7. The only way to make them known, and so have them listed, is via the *.hvar files. But there is no need to do this, except if you want to be able to list them or use them via macros or the lua ipc hvar functions. John

I will look into adding a 'Force Main Window to Top' option to see if this helps, as you can do with the logging console window. John

Nothing at all has changed w.r.t. the hot key. The first Alt-F will show the window, bring it to the top and remove the tray icon. It most probably disappears behind MSFS as that is then requesting to be on top. The second Alt-F will hide MSFS again to the system tray. The third Alt-F will again show the window and bring it to the top. For me, the MSFS main window will never show on top of the MSFS main window - it is always obscured unless I actually select the window itself. I'm not sure why this is, and I don't think there is anything that can be done as I am already requesting that the window be on top when its shown, but it looks like MSFS is overriding this somehow. I'm surprised ou see the window on the third Alt-F - I don't. As I said, nothing has changed in this area and I don't think there is anything I can do, but I will take another look at some point. Hvars are loaded from *.hvar files based upon a match with the aircraft name (or possibly the aircraft.cfg folder name), and the *.hvar files must be in one of two distinct locations. Please see the Advanced User guide and check that you have the correct hvar file in the correct location and the name is a substring match to the aircraft name. If you have any difficulties, activate debug logging in the WASM and take a look at the WASM log - this should tell you what hvar files have been found and which ones match and are loaded. Also, rather than using hvar files, you can just create a preset to activate a hvar instead, using the myevents.txt file. This has the advantage of being directly assignable (in the assignments UI) and the hvar names do not need to be made known to FSUIPC7 via the hvar files to be used. Also see the Advanced User guide for details. John

Change to The first one removes the comments for the delay, the second from the line that starts FSUIPC7. I would have thought this obvious from the comments...and also explained in several other posts... John

Best to create a new post/topic in the User Contributions section (with an appropriate title. Looks ok to me. One thing you should be aware of (and maybe update your comments on this in the lua file) is the size and positioning if the wnd window being displayed. The size/position you provide in the wnd.open call will only be used the first time the script is ran, so if you change these after the first run the new size/position will be ignored, as this will be taken from the [ExtWindow] section of the FSUIPC7.ini. The size/position can be changed there, or you can use the arrow keys to move the wnd window (when it has the focus) and the ctrl+arrow keys to resize. John

Neither do I!

Your EXE.xml and installation log look fine (for an MS Store installation). If MSFS is not auto-starting FSUIPC7, I do not know why. All I can suggest us that you go back to the old method of starting FSUIPC7 which is via the batch file itself. Open the MSFS.bat file (in your FSUIPC7 installation folder) and enable the line that starts FSUIPC7 as well as the delay/timeout line (by removing the comment characters '::' at the beginning of the line). Check other posts I've made about this if you need further details. John

What doesn't work? Why haven't you answered any of my questions? Please respond: Your installation log looks ok - it is for a Steam installation of MSFS. You have also created a new topic for what maybe is the same issue, but I am confused by your posts. Please respond to my questions so that I cannot understand what your issue is.

Why have you reported this again? I have already responded with various questions which you have not responded to. Is FSUIPC7 running? If not, try running it. If your problem is with FSUIPC7 not auto-starting, please see the other thread you posted in about this. If FSUIPC7 is running, what sure that it is running at the same priority level as VAMSYS. Otherwise, please ask VAMSYS support about this - I know nothing about this program. This is confusing...I cannot advise you how to run VAMSYS. This is FSUIPC support. Do you have MSFS installed with Steam and also with MS Store on the same computer? I didn't think that was possible, but if that is the case then the FSUIPC7 auto-start component will only be installed in the Steam version. You will have to manually create or amend your EXE.xml file in the MS Store version (or copy the Steam EXE.xml to the location for this in MS Store).

When you say 'unmodified, original as you attached', what do you mean? I haven't attached anything... Do you mean the one installed, unmodified? If so, then I don't understand this at all, as all the batch file does is display a splash screen and the start MSFS in the same way as it starts when you start it 'directly'. Do you have an MSFS Store or steam version? What is the location of your EXE.xml file? I did ask for your InstallFSUIPC7.log file (and not the FSUIPC7.log file), which would tell me this... Other than that, your EXE.xml looks ok, although the SimBase.Document version is '1.0' and not '1,0' (which is what the FSUIPC7 installer would use), but this shouldn't make a difference. John

Hmm, yes - strange... Glad its now working. John

Just replied to that one! Back from a weekend away and just catching up... John

Switch the inc/dec button numbers, so change: to Rather than using the Heading Bug control, switch to using offset 0x07CC (Autopilot heading value) with the Offset Sword increment decrement controls, where you can specify the inc/dec value that works for you. This is explained earlier in this thread... This is also how your elevator trim is configured, so take a look at that to see how this assignment is made. Again, if the speed is too slow, switch to using the relevant offset instead - check the offset status document to get the right offset. You can log the offsets (using the Log -> Offsets menu item) to see how the values change using the current settings, and to confirm the offset to use. Use the correct (inc or dec) control to get the right direction. John

Also check that is the actual folder being used - use the File -> Open Installation Folder menu option to confirm. John

You need to specify that this is a multiplication, so change: to Also, your profile will only match when using the EasyJet livery. To match all versions of the A320neo, change: to John

Hi John, The ini file should update each time you run FSUIPC7. If its not updating, this is usually due to being installed in a windows protected folder, such as under your Documents or Program Files folder. If this is the case, re-install into a different location. You can skip registration, but remember to copy/move across your FSUIPC7.key, FSUIPC7.ini and any *.mcro, *.lua, *.dll files that you use to the new installation location. John

If you still have issues with this, attach your EXE.xml and InstallFSUIPC7.log and I will take a look. That shouldn't affect the auto-start. John

As the directory name contains spaces, you need to use quotes, i.e. runif1=READY,KILL,"C:\Program Files\IOCards\iocard.exe" Changes were made as there were issues when using command line arguments to programs that were startted by FSUIPC. Can't remember the version for these changes (but quite a while ago now) - check the changes file or the history document. John

Hi Adamski, I can take a look later in the week. I'm away from home at the moment and will be travelling/busy for the next few days, but I'll review this when I'm back. John

I have no idea what 'VAMSYS Austrian' is, or what you mean by 'does not work', but if your issue is with that program, then you need to contact them to resolve your issue (as I already said in the other post where you reported the same issue - please don't do this!). Also please check what version of FSUIPC7 you are using. The latest (and only supported) version is v7.3.3. FSUIPC7 should be auto-started via the MSFS EXE.xml file, in both the MS Store and Steam versions. The included batch file (which you pasted some contents of in your question) has not been used to start FSUIPC7 for quite some time (over a year) and is now only used to display a splash screen while MSFS is starting. MSFS then starts FSUIPC7 via the EXE.xml file (if you selected to install the auto-start component during the FSUIPC7 installation process). If you want further help, please provide more information. Is FSUIPC7 running? Is it connected to MSFS? What exactly is your issue? What error message do you see, and where is the error message from? Also note that if VAMSYS is an FSUIPC client program, it needs to be ran at the same privilege level as FSUIPC7, otherwise it will not be able to connect. John

I'm sorry, but this still doesn't make sense - you assign an axis to an axis control (left hand side of axis assignments box) and you can also assign to send non-axis controls when the axis goes in/out of a particular range using the right-hand side of the axis assignments dialog. You cannot assign part of an axis range to one control and another range to a different control via axis assignments. if that is what you want to do, you need to use a lua script. What actual controls the RPM - is it the prop pitch 1/2 control or the throttle control? You can try logging axis events and see what controls logged when you adjust the RPM via the UI. What helicopter are you using? I'm away from my sim rig at the moment but can take a look when I'm back later in the week. Maybe also attach you FSUIPC4.ini so I can see your actual assignments. John

What do you mean by this? Do you mean that FSUIPC7 cannot connect to MSFS? If you are having problems with FSUIPC7, please show me (attach) your FSUIPC7.log file. If you are having issues with installation, show me your InstallFSUIPC7.log file. If your issue is with VAMSYS, then you need their support. John

I copy my response from your other psot with the same question: FSUIPC6 will create a default FSUIPC6.ini file if non is found in its installation folder when ran, and as you need FSUIPC running before starting LINDA, I can't see how you can get such a message... The FSUIPC6.ini file will be in your FSUIPC6 installation folder, which is not necessarily the same folder as your add-on.xml file, in fact I strongly recommend that you don't install FSUIPC6 in this folder. To check your installation location, use the Open Folder button in the FSUIPC6 logging tab. I suggest you read the Installation and Registration guide which explains the different folder locations. You have probably copied the Linda file to the wrong location, so check that. But for Linda issues, you should contact Linda support. John

@Demoulin You posted in the FSUIPC7 support forum - please use the maim support forum for FSUIPC6 issues. FSUIPC6 will create a default FSUIPC6.ini file if non is found in its installation folder when ran, and as you need FSUIPC running before starting LINDA, I can't see how you can get such a message... The FSUIPC6.ini file will be in your FSUIPC6 installation folder, which is not necessarily the same folder as your add-on.xml file, in fact I strongly recommend that you don't install FSUIPC6 in this folder. To check your installation location, use the Open Folder button in the FSUIPC6 logging tab. You have probably copied the Linda file to the wrong location, so check that. But for Linda issues, you should contact Linda support. John Later: I see you have also created another post for the same issue....