John Dowson

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

Note FSUIPCv7.3.3 has been released so please download and try that before reporting back. Note, however, that this also contains no changes that would affect the auto-start, but contains a few updates that may have caused FSUIPC7 to not start certain threads in certain conditions. If you still get your issue with this version, please show me your FSUIPC7.log file as well as providing information as to whether FSUIPC was auto-started or not, and if auto-started when did you actually start FSUIPC7. Also, you find FSUIPC7 'doesn't work', please try disconnecting and re-connecting from the MSFS menu. John

Hi Leo, The WASM has ben updated and released with v7.3.3 so please download and use that version before reporting back.

Possibly, but not having this aircraft I do not know - the OP should certainly try the condition lever controls. Thanks for the hint, John

I will update the trial license tomorrow (or maybe this evening if I get a chance)...

Was this test with the new WASM module I poste above? I forgot to update the version number so it is difficult for me to tell. Please try the attached version where I have update the version number - I have also added an extra logging statement to log the value of UseAirLocForHvars being used. I would like to get to the bottom of this issue if possible, so please ret with the attached and report back, including your FSUIPC_WASM.log file. Thanks, John FSUIPC7_WASM.wasm

If you mean FSUIPC7 does not auto-start with MSFS, please see item 3 under Problems running FSUIPC7 in the README.txt file. For any further issues if that does not solve your problem, please show/attach your EXE.xml file. Presume this is a separate issue...if this occurs, exit FSUIPC7 and then show me/attach your FSUIPC7.log file. John

What are you finding baffling? Just create a macro file (e.g. QW787.mcro) in your FSUIPC6 installation folder. Add the following entry: 1=L:QW_OH_LDG_LEFT_SWITCH=Toggle You will then see that entry in the assignments control drop-down where you can assign to a button. It really isn't that difficult... John

No, sorry - that resource is for MSFS2020, and not relevant to P3D aircraft. Try activating logging and flip the switch to Auto in the UI to see if any controls/event are logged. Maybe you need to use an event in conjunction with setting the lvar value. And check what the lvar value is when the switch is in the auto position. Other than that I can't really advise as I don't have this add-on. John

Quite a few add-on aircraft don't use the standard controls...For such aircraft, you need to look into custom control, if provided (although I don't think there are any for the QW 787), lvars or mouse macros. The easiest way to assign to change/set/toggle an lvar is to use a macro file. See section Gauge local variable access (L:vars), by macro on page 39 of the Advanced User guide. You should try lvars first for the functions you want to implement, if there are suitably named lvars. Otherwise, you can try with a mouse macro. John

I don't have a copy or know where you could get hold of a copy, sorry. Maybe better to also ask over on Avsim for this. John

There should be 3 presets for the FBW HDG push/pull button: HDG_Pull#(>K:A32NX.FCU_HDG_PULL) HDG_Push#(>K:A32NX.FCU_HDG_PUSH) HDG_Push_Pull_Toggle#(A:AUTOPILOT HEADING SLOT INDEX, Number) 1 == if{ (>K:A32NX.FCU_HDG_PUSH) } els{ (>K:A32NX.FCU_HDG_PULL) } They should all be included in the events.txt file that comes with the latest version of FSUIPC7, and so assignable in the controls drop down menu. If they don't work, then they are either broken or not applicable to the version (experimental) of the FBW A32NX that you are using. Either way, I can't help with this and you should ask about this on the MF support/discord channel. John

Btw, this is not cached values... This is the location for your preferences/files that will not be affected by FSUIPC updates. If you want to preserve your hvar files and ini settings, you should use this location. Anything you change in the Community\fsuipc-lvar-module folder could change on an update. John

Just checked the code, and it looks like I forgot to initialise the default value for the new ini paramater UseAirLocForHvars to false... Sorry about that. Please try with the attached WASM - use it to replace the one in your Community\fsuipc-lvar-module\modules folder: FSUIPC7_WASM.wasm If you get the same problem with that one, please attach your FSUIPC_WASM.log file (preferably with Debug enabled) and I will take a look. John

The load flight function has been broken in MSFS since inception. I'm not sure of the current status as I haven't checked this for a while. From the current documentation, this function is now working. However, there still seem to be issues in the Flight Save MSFS SimConnect function (as well as the Flight Plan Load function), so the problem may be in the flight save file. I will look into this further (next week now) and maybe raise another bug report with Msfs/Asobo. Not much I can do about this in FSUIPC7 I'm afraid, as FSUIPC relies on the corresponding SimConnect functions to do this. John

You could also add your own preset to do this, which maybe easier. For example, for the run/stop toggle, create a file called myevents.txt in your FSUIPC7 installation folder, and add the following line: CRJ Engine1 Run-StopToggle# 0 (>K:MIXTURE1_RICH) 0 (>K:TOGGLE_FUEL_VALVE_ENG1) 0 (>K:TURBINE_IGNITION_SWITCH_SET1) You can then assign to 'Preset: CRJ Engine1 Run'. You can add similar presets for engine 2 and also for off. Note that presets are only loaded when FSUIPC starts, so if you make any changes, restart FSUIPC7 to take affect. John