John Dowson

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....

Sorry, forgot to update the WASM - it is done now. Also, the latest WAPI version is 0.5.7, so you should update that. If using FSUIPC7, just download and install V7.3.3 which alsocontains the latest WASM. John

Sorry, but not having this aircraft I cannot really advise - maybe some other FSUIPC7 users who have this aircraft can help. All I can suggest is, first, try activating logging for events (and maybe later axis controls) to see if anything is logged when you change the state of the cut-off valve in the cockpit UI. if anything is logged, then you can try assigning to that. Otherwise, maybe try the Toggle Fuel Valve control or Fuelsystem Valve Toggle control, or list the lvars and see if any look relevant, and see if the value changes when you change the state via the UI. If there is an lvar that does this, you can then add that to an offset and assign to change the offset value (which will change the associated lvar). John

Please update to the latest version of FSUIPC7, which is v7.3.3. Only the latest version is supported. Your log shows FSUIPC7 exited normally as MSFS was no longer available, so it is MSFS that crashed not FSUIPC7. You will get an exception/fault (not a crash) in the Event viewer for FSUIPC7 if MSFS crashes - this is normal. You should see an event for the MSFS crash before that. If you have read through a fair amount of posts, then you should know that I cannot help with MSFS crashes. Check one of the many other posts on this for further information - I am not going to go into details any more on MSFS crashes. Try the Asobo forums and/or raise a bug report with Asobo. John

You are using windows 11, so so you need to set DisableMSFSMonitor=Enum in the [General] section of your FSUIPC7.ini file. Please see the provided README.txt (included in the FSUIPC zip file you downloaded) under Problems running FSUIPC7: John

Ok - MSFS seems to have support for up to 20 fuel tanks - see https://docs.flightsimulator.com/html/Programming_Tools/SimVars/Aircraft_SimVars/Aircraft_Fuel_Variables.htm#fuel-tank-selection You probably want to use either one of the indexed variables FUEL SELECTED QUANTITY or FUEL SELECTED QUANTITY PERCENT to get the percentage, and maybe FUELSYSTEM TANK CAPACITY for the capacity (see https://docs.flightsimulator.com/html/Programming_Tools/SimVars/Aircraft_SimVars/Aircraft_Fuel_Variables.htm). There is no way I can add these to FSUIPC offsets for all users as this would generate too many errors (logged to the MSFS console) when using a plane without that many tanks. If you require this information, you should look into adding the required simvar (indices) to free FSUIPC offsets and you would need to provide appropriate instructions to the users of your program. John

The simvars that are used to populate those offsets are not indexed but individually named. Ok, so there are 2 more fuel tanks, and you need the capacity and level for these two tanks. You first need to determine what, if anything, is holding this information. Does the aircraft provide additional simvars for these quantities, or are there any lvars available for these? I don't have this aircraft so I really can't help you with this. You need to determine what is holding these quantities before we can consider adding them to offsets. Maybe ask DC designs about this. Why is this a problem? It is only a matter of providing one additional file (myoffsets.txt) which they either install in the FSUIPC7 installation folder, or append to their existing one. Anyway, before you consider this, you need to find out where the information is held. John

Done.

You don't mention which offsets/simvars you are using for this, which would be helpful. Depends on how/where this information is held. If there are (indexed or not) simvars, then you can add these to FSUIPC offsets for both reading and writing (if the simvar is writable) - see the section entitled Adding Simulator variables (simvars) to FSUIPC offsets on page 34 of the Advanced User guide. Alternatively, if the values are held in lvars, then you can add the lvars to fsuipc offsets (also for reading and writing) using the Adding Lvars to Offsets functionality - see page 46 pf the same manual. John

Hi Matt, By default, hvars are loaded based upon a substring match to the aircraft title, as logged in the FSUIPC7.log file and also held in offset 0x3D00. Copy and rename your A320 hvar file to be a substring match to the tile of your Headwind A330. It is possible to switch to matching on the aircraft folder name by setting the WASM ini parameter UseAirLocForHvars, which can provide better matching when using different version/liveries of the same aircraft - see the Advanced User guide for details. John

Even though you haven't responded, this update has been included in the latest release, v7.3.3. John