John Dowson

I don't know - what exactly is your problem? If its an installation issue, please show me your InstallFSUIPC6.log file. As indicated in this post, do not try and install under your Windows Documents folder (or any Windows-protected folder).

I'm sorry but not having this aircraft I cannot really advise any further... maybe try the FenixSim support forums...

I don't think this is currently possible I'm afraid...I can/will look into this (it will take a while before I have time) but cannot guarantee that I can do anything about this. Have you looked into other more direct methods of controlling this, such as using lvars, hvars or presets (assuming no standard controls are available)? This would be more reliable, if anything exists. Try looking at the HubHop preset list (https://hubhop.mobiflight.com/presets/) to see if anything is available. If you let me know what aircraft you are using I can also take a look. John

If you re-installed windows, did you install the latest combined VC++ redistributable package? If not, do that (from https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist) - uninstall any of the 2015, 2017, 2019 & 2022 packages first if already installed. There is plenty of information about this issue in the README.txt and in many forum posts already. The problem will most probably be with your EXE.xml file (C:\Users\timsi\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml) - check that. For further information on this issue, see this thread: Follow the advice there. If you still can't get it to auto-start, show me your EXE.xml. John

I suggest you look at what you posted: These assignments will be sending both an inc and a dec control on both a button press and a button release on the same button (button 0 on joy Id 64), so the result will be no change. Isn't that obvious? Again, sending both inc and dec controls on the same button. Highlighted entries again sending both inc and dec controls on the same button. The non-highlighted entries are ok, as you have inc on button 1 (press and release) and dec on button 2 (on press and release). To help you see what is happening, use logging. Activate logging for Buttons & Keys as well as Events. Open the logging console window (Log -> Open Console) and see what is being sent when you press your buttons. This should tell you what is happening. You are also sending your controls on both press and release. This is ok, but you may want to consider sending the control on repeat, i.e. the control keeps being sent when you hold the button press. You can also adjust the button repeat rate as needed.

Ok, thanks for the update. Regards, John

No problem. However, there was a bug in the previous version I posted related to the use of the esc key - the key press was received but no key release (as the FS goes into the menu and stops sending data), which caused the esc key press to repeat indefinitely. This has now also been fixed.

Yes, it does look like its crashing... Can you enable logging for Extras please, as well as Events and resend the log the next time it crashes. You can also try setting/changing the following ini parameters in your [General] section: TrafficStallTime=-1 InitialStallTime=45 NormalStallTime=-1 StopWAPIInMenu=No This will reduce the number of simconnect connections used, which can sometimes cause issues. You also seem to be using the MF event files (and thus the MF event WASM) and are not using the FSUIPC WASM/WAPI for much of anything, that I can tell - unless in your KAP140.mcro file, so you can also try disabling the WASM module as a test. Regards, John

The options should be enabled once you have a plane loaded and ready-to-fly. If that is not the case, first check that you are using the latest version of FSUIPC7, which is v7.3.4, and if you are and the options are not active when you have an aircraft loaded then show me your FSUIPC7.log file. Note that you only have to enable once, nut when you enable you may have to disconnect and reconnect to MSFS to get the WASM data. John

@NovemberUniform The attached version accepts two new ini parameters: InitialKeyRepeatRate - default value of 250ms SubsequentKeyRepeatRate - default value of 100ms These ini parameters go in the [Keys] or profile-specific [Keys.xxx] sections. FSUIPC7.exe John

Could you also activate logging for Events (non-axis controls) and show me another log file.

Peter retired several years ago now. Your post is very difficult to read....in future please post as standard text.... Your assignments and log look ok and as expected. One thing that is strange is the parameter you are using - 512. I don't thibk the flaps inc/dec controls take a parameter, so this should be ignored, but you could try changing that to 0 or 1. Other than that, I am not sure why this is not working as expected. What do you see logged if you move the flaps down one notch using the cockpit UI? I will take a look at FSX later today to check this... John

Can you please attach your FSUIPC7.log and FSUIPC7.ini files. Also, try opening the FSUIPC logging console (Log -> Open Console) and see what, if anything, is logged when this occurs. Also check that you have disabled/unchecked 'Allow the computer to turn off this device to save power' on your USB hubs and devices. @mariofsx Apologies for not seeing your post from 14th October 2020 - not sure why I missed this.... However, as that is now over 1.5 years old, I presume this issue is now solved or has gone away.

It is available in the first post in this topic... I am not going to respond to support requests not related to this topic... BUT FSUIPC7 does not support the use of the mouse in MSFS2020 - never has, never will. John

I have verified your details for your FSUIPC7 license and they validate just fine here. The WideFS order number doesn't exist, and I cannot see a WideFS order/purchase with your email (only FSUIPC6 and FSUIPC7 orders are associated to your email address). There are only two reasons why your key won't validate: 1. you are entering them incorrectly 2. your VC++ redistributables are not installed or are out-of-date. For 2., please see the provided Installing and Registering FSUIPC7 document, under Invalid Key Problems. For the WideFS license, please verify the order number. You can also PM me your purchase email (please do not post your key details!).

Please read the documentation before posting. This has also been reported many times before - always try searching for similar posts before posting. From the README.txt included in the zip file, under section Problems running FSUIPC7: John

Do you understand how it is working for the FBW A320? If you can do that , you should be able to work out how to set things up for the Fenix A320. If its working for the FBW A320, it will just be a matter of copying that profile and then changing it to use the controls that work for the Fenix A320. As I don't have this aircraft, I cannot really advise any further, especially for such a general question. You should at least try to do this yourself, and ask questions if you get into difficulties. Start by trying to understand how it is working for the FBW A320, it will be pretty much the same, but using different controls/events/presets... John

You don't need to do anything except activate the WASM and restart. The MF events.txt file is installed with FSUIPC7 since version 7.3.0 (or maybe earlier). Check you are using the latest version, which is 7.3.4. All presets will be in the drop-down assignment menus, prefixed by 'Preset:'. Please don't post again until you have read the documentation, as previously advised - WASM section starting page 46 of the Advanced User guide, and presets and the MF events.txt on page 48.

You don't need to download or use MobiFlight connector to use lvars/hvars/presets with FSUIPC7 - it comes with the MF presets. But I do not know what your issue is, and it certainly isn't related to this topic. Please create a new topic and describe your issue. However, if it is related to using MF presets, please first make sure that you have enabled the WASM module and have read about the WASM and how to use presets - you can find this information in the Advanced User manual, starting on page 46. Also, before requesting support, check that you are using the latest version which is v7.3.4. John

You need to disconnect and re-connect to MSFS after you have enabled the WASM. That would also do it! No problem!

Do you have the WASM installed and enabled? Check the Add-ons->WASM menu - you can enable from there if not enabled. You can also check that the WASM is connected by selecting List Lvars. Also check that you are using the latest version of FSUIPC7, v7.3.4. Any further issues, please attach your FSUIPC7.log and FSUIPC7.ini file rather than attaching screenshots. John

Yes, I also think 50ms is probably too fast. I will make the default 100ms, and stick with 250ms for the first repeat. I will make both of these adjustable via ini parameters. I think I can make both of these parameters profile specific, but whether you use profiles in separate files or not wouldn't make a difference.

Still waiting I'm afraid - I did get an acknowledgement from PMDG but am still waiting for one of their technical guys to contact me...I will ping them again as a reminder. John

Try activating logging for Axis Controls and Events. Open the logging condole (Log -> Open Console) and see what (if any) events are logged when you move the throttle/flaps in the cockpit UI. If you see any events logged, you can try assigning to those. John

Or maybe better to wait 250ms (for example) for the first key repeat, and then 50ms for subsequent repeats? I think it is necessary to have a longer repeat interval for the first repeat as this will affect all current key assignments (when 'no repeats' has not been selected). This is implemented in the attached version, v7.3.5b: FSUIPC7.exe John