John Dowson

@VENOMous Still waiting to see your FSUIPC7.JoyScan.csv file so that I can correct your assignments...please also attach your latest FSUIPC7.ini and FSUIPC7.log files.

You can use the FSUIPC SDK to create such a file. Using the SDK, you can write to FSUIPC offsets to trigger events/controls, presets, etc. There are also quite a few wrappers to the SDK for various languages, the most popular and advanced being Paul Henty's .Net client dll. There is a sub-forum for this here: https://forum.simflight.com/forum/167-fsuipc-client-dll-for-net/ Otherwise, take a look in the SDK folder of your FSUIPC installation. John

I do not know of any such control - as far as I understand, there is only the throttle... Do you have an aircraft where it is possible to control this (in the virtual cockpit)? If so, then it may be possible in that aircraft, but there is no generic FS control/event for this.

You can read the name of the current aircraft in offset 0x3D00.

You have NOT installed the MF events.txt file - from you installation log: and from you FSUIPC7.log file: Please re-run the installer and select to install the MF events.txt file, or download it from the MF HubHop site (https://hubhop.mobiflight.com/presets/) and copy it to your FSUIPC7 installation folder.

I don't know as you do not provide enough information. Did you install the FSUIPC WASM module? Did you install the MobiFlight events.txt file (which holds the MF presets)? Please show me/attach your FSUIPC7.log file and also your InstallFSUIPC7.log file and I will take a look.

No! Why do you think that? For example, 0x0D70 is the area for Macro and Lua requests, as it states in the FSUIPC6 Offset Status document: Please see that document, and you can use offsets in areas designated as Free for general use. Thats fine and will store the value of the lvar in the offset (for reading ONLY), except that offset 0x8804 is NOT free for general use. Please DO NOT use offsets that are not documented as free for use as this may cause issues. What is a 'raid folder'? All lua scripts should go in your FSUIPC6 installation folder, or the folder specified by LuaPath if using that. Entries with indices 1m11,12,13 & 14 are ALL incorrect. Lua scripts in this section MUST be preceded by Lua, as are the entries with indices 2,3,4,5,6,7,8,9. You can interrogate (i.e. read) the offset to get the status of the LED, but you cannot control it as the offset will be read-only, as you have not added any lua code to handle a write/update. Please do not attach images, especially of MobiFlight which I do not support. I will remove that.

No yet - I am rather busy in support issues at the moment, and my time is rather limited at the moment due to health issues. Don't worry, I haven't forgotten, and will hopefully find time to look into this next week.

Looks good now! No, I don't think a repeat assignment would effect fps that much....but you could add it back to see if the fps decreases if you want to check this. John

Many of the camera controls in MSFS are not working when assigned externally, including the zoom controls. There are also some MF presets for zoom, but these also don't seem to work. Therefore to control zoom, you can either assign in MSFS, or assign in FSUIPC7 to the default key assignments. So, for example, to assign to cockpit zoom-in, assign your button to send the equals key ('='), and for zoom-out, assign to the hyphen/dash key ('-').

You still have not changed the preset assignments on repeat in your [Buttons.PMDG 777] section - change these as well, as I said in my last comment:: 15=RF,4,CPPMDG_B737_FD_Switch_Capt_On,0 -{Preset Control}- 17=RF,31,CPPMDG_B737_FD_Switch_FO_On,0 -{Preset Control}- 21=RE,4,CPPMDG_B737-7_GEAR_DOWN,0 -{Preset Control}-

That log file you attached ends after 94 seconds before you even had the 777 loaded and ready to fly, and so is useless. You also have other presets sent on repeat - please also change these: 15=RF,4,CPPMDG_B737_FD_Switch_Capt_On,0 -{Preset Control}- 17=RF,31,CPPMDG_B737_FD_Switch_FO_On,0 -{Preset Control}- 21=RE,4,CPPMDG_B737-7_GEAR_DOWN,0 -{Preset Control}-

For all auto-start issues, see Sorry to hear that. No idea wht your issue was as I never saw your files. There does seem to be an occasional issue with the WASM when using the 777 which I am investigating.

This issue is usually caused by flaps calibration. If flaps assigned in FSUIPC, make sure it is assigned with 'Direct to FSUIPC calibration'. If not assigned in FSUIPC, check that you are not post calibrating. You can attach your FSUIPC7.log and FSUIPC7.ini files and I can take a look.

II need to see your FSUIPC7.log file as well please. I always need that. I have now experienced a WASM crash switching between the PMDG 737 and 777, so there is definitely an issue there. But your WASM log shows that it ran ok for you, so it must be something else. I am investigating the WASM crash and will get back to you once I have found anything.

Yes, that looks correct. Check the FSUIPC Offset status document for a free offset, e.g. there are 512 bytes free starting at 0xA000 No. Your lua script is only for reading at the moment. If you want to update the lvar when you update the offset, you have to have that as well. So you need to add an event.offset call (on the offset you use) and in the handling function you can set the lvar value. Before you set the value, check it was not the value received and written to the offset, e.g. store the lvar value in a local script variable when received and check its different from the offset value when that changes before you use it to set the lvar value.

First, what version of FSUIPC and what simulator are you using? For information on offsets, please see the FSUIPC Offset status document for your version of FSUIPC. However, there will be no offset holding that lvar value. FSUIPC does not hold any lvar values in offsets by default. If you want to add an lvar to an FSUIPC offset, you can do that but it doesn't happen by default. In FSUIPC7, you can use an [LvarOffsets] section of the FSUIPC ini file - see the Advanced user guide for details. For other versions of FSUIPC you would have to use a lua script. The script should wait for the lvar value to change (event.lvar) and in the handling function, write the value to a free/spare FSUIPC offset. But if using MobiFlight, doesn't that have access to lvars without using FSUIPC? John

I noticed this was missing in the ini file you attached, which I thought was strange... Not sure what could cause this. Anyway, please keep an eye on things and send me the files again if you get a problem, as there may be an issue somewhere as others are having similar problems.

First, get you stop all these errors: These are from preset FNX320_LIGHT_LANDING_BOTH_ON which you have assigned on repeat, so this is getting sent 20 times a second, causing those errors. Please change the assignment line in your [Buttons.Fenix A320] section: 14=RE,17,CPFNX320_LIGHT_LANDING_BOTH_ON,0 -{Preset Control}- Change that R to a P: 14=PE,17,CPFNX320_LIGHT_LANDING_BOTH_ON,0 -{Preset Control}- You are also using the same assignment in your TBM 930 profile - change there, or maybe just remove those assignment to Fenix presets. Other than that, it looks like WASM connection wasn't working, which is why the presets weren't working. Can you make that correction please and test again and show me the new FSUIPC7.log file and the FSUIPC_WASM.log file. The location of the latter is:

Also, please add TestOptions=x800 to the [General] section of your FSUIPC7.ini file. This will add extra logging on when/why FSUIPC7 is starting, or not..

Sorry, but your log file again shows that you were trying to use presets before FSUIPC was ready. Did you actually load an aircraft and get ready-to-fly? Looks like you got to the main MSFS menu after 76 seconds, then exited MSFS 5 minutes later, and FSUIPC7 did not detect you having an aircraft loaded and ready-to-fly. Can you please explain what you did. Also, please try another aircraft. Maybe this is an issue with the Fenix.

This is because you are not using substrings for your aircraft names in the [Profile.xxx] section of your FSUIPC7.ini. You need to edit the names there to be a substring of the aircraft name that matches the aircraft regardless of livery. Otherwise, you can switch to using UseAirLocForProfiles instead (see Advanced User guide on this parameter), but if you do this you will have to add each aircraft to your profiles again, and remove the current entries under your [Profile.xxx] sections as these will no longer be relevant.

Ok. Please also set Debug logging in the WAPI (Log ->WAPI -> Debug) and show me your FSUIPC7.log, FSUIPC7.ini and FSUIPC_WASM.log file if/when this happens again, and attach after exiting FSUIPC7. Also worth checking the MSFS debug console (you need devmode activated to see this) to see if any errors (related to FSUIPC) are reported there, especially if there is a message relating to the FSUIPC WASM crashing.

Also change your profile aircraft names to use substrings - if you don't do this, your assignments will not load when you use an aircraft with a different livery. Change to and to and to etc. i.e. You should change the aircraft names added to a profile section to a substring that catches ALL variants. If you leave the name as it is, you will have to add the aircraft again when you use a different version/livery. You should get into the habit of doing this each time you add an aircraft to a profile.

Are you manually starting FSUIPC7 or is it auto-started? The log file you attached shows that FSUIPC7 was manually started. You tried to start using presets 5 seconds after starting FSUIPC7, which gave errors: However, FSUIPC7 only became ready for use after 11.422 seconds: Any assignments will not work until after the 'Starting everything now' line is logged, and presets are not available for use until the '[INFO]: Connected to MSFS' line is logged, and generally you should wait until initial lvars have been received and any lua autos have been loaded, which is after this line: 11422 Lvars/Hvars received - checking aircraft autos.... Your ini file also does not contain the DetectToConnectDelay or DetectToConnectDelayAuto ini parameter - did you remove these? Please add the following to the [General] section of your FSUIPC7.ini file: DetectToConnectDelayAuto=60 DetectToConnectDelay=1 StartUpTuningActive=Yes and change the following (currently set to 45): InitialStallTime=15 Well, it would have be useful to see your FSUIPC7.log file generated when FSUIPC7 was auto-started and you had this behavior - the log you attached was from when you manually started. Make the changes I mentioned above, then run MSFS, let FSUIPC7 get auto-started, and then exit MSFS. This will allow FSUIPC7 to auto-tune those start-up parameters. Then run MSFS again and let FSUIPC7 get auto-started. If you have any issues after this, exit FSUIPC7 and show me your FSUIPC7.log and FSUIPC7.ini files again.