John Dowson

Try the offset status document, installed with the rest of the FSUIPC documentation under your documents folder. John

You have to determine if there is a simvar (a simulator A type variable, most held in FSUIPC offsets), or an lvar that holds the current which position. Its most probably the latter - try listing lvars to see if there is anything appropriate. If there is, you can read that in lua. John

First, can you download and try with the latest FSUIPC7 release, v7.3.5, released earlier today. The WASM & WAPI have also both been updated to 0.5.9 in this release, so you will also have to recompile your plugin with the latest version. Once that is done, if you still experience the same issue, can you activate Debug level logging in both the WAPI and the WASM and show me both your FSUIPC7.log and FSUIPC_WASM.log files. A WAPI log file from your StreamDeck plugin would also be useful, if you could also generate that with Debug level logging. I think your issue may be to do with having multiple WASM clients... John

Of course - I used 82 (R) so that I could test with Win+R that opens the windows 'run' command window - I did tell you this earlier on: Anyway, glad you finally figured it out.

Really? You should show me what you tried...I need to see your FSUIPC7.ini and an FSUIPC7.log file with Buttons & Keys logging activated. It should be sending the assigned key press if done properly, as in the screenshot I posted (but using 89+512, as indicated. If that is not working I would like to understand why... But there may be no change...you should test this now, before I release, if you want this working... No idea what this is supposed to mean...

I will look to see if I can add anything to help with this in a couple of weeks or so...I will let you know. I'm not too familiar with the windows API for mouse control so I need to investigate...I will report back if/when I find anything. John

Thinking about this a bit more, it may be possible to allow this to be sent as a key press assignment...I will implement and check before I release to see if I can enable, but in the version I posted you will have to use the key press controls. John

What is this? As I said, you have to assign to the Key Press & Release control, right hand side of the assignments dialog, not send as a keypress on the left. That cannot be used as windows hijacks the key press and it won't register.

Can you explain what you are doing...this is the assignment I tested with, Win+R (win+Y doesn't trigger anything I can test...):

I think your problem is almost certainly related to the Fenix A320. A lot of people are having issues using FSUiPC to control the main flight axes (check this forum!), and they currently only seem to be able to assign via MSFS assignments. As MSFS doesn't support PFC hardware (as far as I am aware) then this is not an option for you. Maybe also check the Fenix support forum (I assume there is one...!) for this... John

I can't see how that can be related to the auto-start issue - those installation components only install files (the MF events.txt file and the MF events file) into your FSUIPC7 installation folder. The pop-up dialog doesn't appear when you don't install the MF events.txt file. Strange!

The general method of determining what controls/events to use is to activate the appropriate logging (Events or axis controls) and then operate the function in the cockpit UI and see what events are logged. Otherwise, ask in the support forum for the aircraft you are using, if available. What pdfs are you referring to? Those for FSUIPC3 or for your aircraft? If the latter, then I still suggest that you need support from the aircraft provider. If the former, tell me what pdfs you are referring to and I will see if I can find them and take a look so I know what you are talking about... John

There is no control/offset to do this directly. However, you could possibly write a lua script to achieve this - in the lua you need to determine the current local or zulu time (I am guessing there should be a way to do this in lua but don't know off-hand - try google) and then set the time via the local and/or zulu time offsets (see the Offset status document). Probably better to do this in zulu time, as the local time for your PC is most probably a different time-zone to the local time in the FS. John

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