John Dowson

What do you mean by this?

Maybe if you give your post an appropriate title, including the words 'Fenix A320' and 'PFC Avionics Radio Shack' (sic. Stack?)' then other users who use this aircraft and use PFC hardware may be able to help. I doubt anybody will read your post (apart from me!) with a title like 'Some Help Required'. U cannot help you, not having this add-on aircraft or any PFC hardware. And as your equipment is working with all other aircraft, it must be specific to this add-on aircraft. If you want help from people then you should always give your post a clear an appropriate title that could attract users that may be able to help... John

@NAX I have put together a pre-release if you would like to try it - available from: http://www.fsuipc.com/download/Install_FSUIPC735.zip - copy and paste that link into a new browser tab to download as clicking (probably) it won't work To send Win+Y, assign your button to Key Press and Release with a parameter of 89+512 (where 89 is the virtual key code for the Y key, and 512 is the shifts code for the Win key). This will hopefully be the same version I will be releasing on Sunday 29th, although I will update the MF events.txt file again before release. John

Yes - you failed to check/read the documentation.... In the README.txt (included in the zip file you downloaded) under Problems running FSUIPC7: Btw, the log file you attached ends after 16s and is not complete. Please make sure that FSUIPC7 is closed before you attach a log file, and make sure you attach one that was generated when your issue occurs.

I don't know...what exactly is your issue? If you clicked-on enable, then the WASM menu must be visible, so why do you say think that this applies to you? Please explain your issue - do you gave the WASM menu? Is the WASM enabled? Remember that once enabled, you need to disconnect/reconnect from MSFS (or restart FSUIPC7), and the other entries in the WASM menu will not be available until an aircraft is loaded and you are ready-to-fly.

They come with FSUIPC7 and are directly assignable from the controls drop-down menus (prefixed by 'Preset'). Make sure you are using the latest version (v7.3.3) and have the WASM installed and enabled. You can enable it from the Add-ons->WASM menu item (you only need to do this once). Once enabled, disconnect and re-connect to MSFS (if it is running) or restart FSUIPC7. Documentation on using presets. lvars & hvars is included in the WASM section in the Advanced User guide. Yes, most probably. Check to see if there is an MSFS option to prevent this. i did take a quick look to see if there is anything I can do about this (e.g. a windows call to return the pointer visibility), but I couldn't see anything that looked suitable. I can take another look when I get more time.

I've updated this now and have also allowed for use of the win key with the FSUIPC-added controls for sending keys. I'll test tomorrow, and if all is ok I will release this at the weekend (Sunday). John

To clarify, I suggest that you first disable the WASM (+ any additional logging) and fly like that for a while. If it crashes again, we know it isn't related to the WASM (and you can uninstall as not using, but up to you), and I can provide some additional logging flags to help track this down. If you are happy that its not crashing any more, I would like you to re-enable the WASM once again, and set Debug (or maybe Trace) level logging in the WAPI, and see if we can get more information from the log. I will also perform some tests here...

You again posted in the wrong support forum (what has your issue got to do with FSUIPC7, which is where you posted?) - I have moved your post for you. FSUIPC4 is not compatible with FS9 - you must be using FSUIPC3, no? Please note that this is no longer supported, although I can maybe try to help...you would attract other users that could possibly help if you had given your post an appropriate title... What is 'flightsimpm'? Have you tried their support? I don't really know what this means - what are those offsets? Why are you using those? Are you using Project Magenta? They are in the offset area for Project Magenta... I am also totally lost by your post, sorry. Please try and explain your issue more clearly, and attach your FSUIPC log and ini files. However, I think you need support for flightsimpm...or maybe Project Magenta if using that...

Yes, you are using the MobiFlight WASM module, not the FSUIPC one. You may as well disable the FSUIPC WASM - you can even uninstall it (i.e. opt not to install it the next time you re-install). But I would like to know why its crashing, so maybe keep it active for now... I would prefer the latter...but if we find something that avoids the crash, that should also help in identifying what is causing it...

Did you check the USB hubs? That is usually where the problem lies... Logging should certainly not affect anything...\ Looking at your initial crash log again, are you sure it crashed when returning to the main menu, not when starting another flight? I ask as this is where you stop the flight/return to main menu: and then around 5 minutes later a new flight is started: Maybe try with Extras logging only (turn off event logging), and set this ini option: StopWAPIInMenu=No If you still get a crash, you could try disabling the WASM to see if its related (if not using it) or activate Debug level logging in the WAPI if you are. Ok, but I don't think its a simconnect issue if FSUIPC is crashing... Lets see how it goes with this...if the problem persists, I may need to get a crash dump file from you to see what is happening... John

I've looked into this further and I don't think this is going to be possible... The problem with the win key shortcuts is that windows interprets them first and if there is a windows assignment then that is performed and the key press used is not passed on to FSUIPC, so it is not possible to assign a button press to this key press combination. However, you can assign to win+? key presses if there is no windows assignment to such a key press - but then, what is the point? However, it may be possible by assigning to the FSUIPC control Key Press & Release. I've just realized that I haven't updated these yet to use the updated shifts to handle the left/right modifiers for the shift, alt and control keys. I will look into and correct this, hopefully next week, and see if I can add another shift code there to allow the win key to be used as a modifier using that control (as well as the individual press/release controls).

I am not going to look into this further until that is done... FSUIPC receives controller input directly from windows, and then sends this to the sim as controls. It should report an error if there is a problem with simconnect. You could try activating the simconnect log file , and see if any errors are reported there. Are you using any other simconnect clients? Have you tried with those changes mentioned previously?

Why are you asking questions about SPAD.next in the FSUIPC support forums? Why not try the SPAD.next support forums? If you are using FSUIPC7 and have questions on that, please use the FSUIPC7 sub-forum. If using GF devices with FSUIPC7, you need the GFDev64.dll (available from www.fsuipc.com and the download section if this forum) in your FSUIPC7 installation folder. I will move this post to the FSUIPC7 support sub-forum. John

Use of the win key causes issues as it is reserved for use by windows. You cannot currently use this as a modifier for assigning key presses to buttons (or in key assignments). I surprised you need win+Y for this - according to the Microsoft documentation (see https://support.microsoft.com/en-us/windows/keyboard-shortcuts-in-windows-dcc61a57-8ff0-cffe-9796-cb9706c75eec), that is: Windows logo key + Y Switch input between Windows Mixed Reality and your desktop. You should be able to change this in windows, most probably with a registry edit. Try google... I could possibly allow this as a modifier for button assignments to key presses - I will check this. John

And it still displays the warning the next time you start FSX? If so, you should try the registry fix for this (in the FAQ section): John

Any available simvar can now be added to an FSUIPC offset - see the section Adding Simulator variables (simvars) to FSUIPC offsets on page 34 of the Advanced User manual. John

Strange - this works fine here and for many people, without issues. You have to do this BEFORE you start MSFS (of course...). Have you tried the MSFS Add-on linker - many people use this to manage the contents of their Community folder - seems to work well - I also use it occasionally but more often I do this manually. I find that it loads lvars for some aircraft just with having the aircraft in my Community folder (e.g. the FBW A320). I can get > 3000 lvars when I have several add-ons in my Community folder... But whatever works for you... Nor am I, very strange...

This issue has been reported hundreds of times now...please see one of the previous responses:

Then you must have installed the WASM 0.5.9 as well - this is installed with FSUIPC7, unless you manually uncheck this component during installation, in which case the log would report a WASM mismatch...

I can't see any indication of SimConnect issues in your log. When controls become unresponsive, this is usually due to windows putting the controller to sleep. Check the USB hub and device properties and make sure 'Allow the computer to turn off this device to save power' (under Power Management in device properties of Device Manager). Windows has a habit of resetting these settings on occasion.

Strange - I have no issues here...You did have an aircraft loaded and ready-to-fly (i.e. not in the MSFS menu) I presume... It seems that FSUIPC7 isn't receiving the lvar/hvar config data (which is why the menu items are disabled). You could try disconnecting and reconnecting yo see if that triggers the config data (do not enable/disable!). Could you activate Debug level logging in the WAPI and WASM and show me your FSUIPC7.log file again, and also show me your FSUIPC_WASM.log. Maybe also try with a different aircraft - although this shouldn't make any difference. I have done several tests here with various aircraft, starting FSUIPC7 with MSFS and also starting it after an aircraft is loaded and it is working every time.... John

Its John - Pete retired several years ago. Thanks for reporting back - as I said, you need the WASM enabled for the script as it is using an lvar. John

I will create a FAQ topic on this issue (when I have time) and put all relevant information there - there have been too many posts on this issue, which is why I am always repeating myself... John

It won't auto-start if you set it to admin. As I have said many many times now, if MSFS is not obeying the EXE.xml it is a problem for Asobo, I cannot do anything about this. You can switch to using the MSFS.bat method - see the previous posy I referenced. I really have nothing more to say on this issue that I have not said 10 times before...I am not going to repeat myself again, read the other posts.