John Dowson

Ok, good - as you image showed you were selecting for a key assignment, and you need to set 'Select for FS control'. Doing what I said, don't you get faster movement for the second (i.e. when assigned on press and release) button? Did you try logging the press/release events of these buttons? Repeat should work, but as it is continually repeating it seems that the device isn't sending a button release code. This is why I asked you to activate logging to see what your buttons are emitting. It is difficult for me to advise when I don't have such a device and I cannot tell how its configured and what press/release codes it is emitting. Also, as its a GF device, do you have the additional GF software running? Does this not let you assign and configure the trim wheel? Or are you just using the GFdev64.64.dll? If you cannot get the movement you require via standard assignments, maybe you should look into using lua scripts. You can do something based upon the scripts in this post (although they are originally for Saitek trim wheels , but if using buttons to control trim, it shouldn't make a difference) - but you only want the button functions, and can remove the axes ones (and make sure that you update the joystick and button numbers used to match those of your device): You can also use that as a basis to write a script to control with 2 buttons for slow up/fast up & slow down/fast down.

Yes, but as noted above, no need for calling cmd.exe, calling start shell:AppsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App -FastLaunch is sufficient.

Btw, thanks for this pointer - very useful for me! Done.

Yes, a new profile will initially be empty - don't forget to save it/them. When you restart MSFS, it should default to the previous profiles assigned. One user did report that they needed to add at least one assignment to the profile for it to be enaled (by which I think they meant loaded on start-up), but I don't find this to be the case - maybe that was in an earlier version of MSFS.

Which saitek throttles are you using? (I ask as I didn't know that some models have a reverser) Could you attach your FSUIPC5.ini please and I'll take a look, as well as your FSUIPC5.log and FSUIPC5.JoyScan.csv files. That is strange.... Do you have controls enabled or disabled in PD3v4? If enabled, check the assignments. Otherwise, are you running any additional software for the throttles that could be interfering? That's rather worrying...I'm still on 1909 but was thinking of upgrading this afternoon.

Ah, ok. So one up button should be for fast trim down and one to slow trim down, and similarly for the down buttons gpr trim up. Can you check if/when the trim wheel "button" are sending release codes (by activating 'logging for 'Buttons & Switches'). You could try assigning the first up-button (on trim wheel), to "trim down" on press only. For the second up-button, assign to "trim down" on press and release. And similarly for the down buttons.

Thats interesting - and strange! The units for offset 0x07F2 are ft/min. What are the units you are using for the parameter of the AP VS SET command? I could automatically do this in FSUIPC7 maybe. Presumably it needs to be sent on each change of aircraft or new flight, no?

What do you mean by this? FSUIPC7 does not recognise an axis on one of your devices? Are you assigning to a switch or 'sticky' button? If it continues, then its not receiving a release event. You can check what events your buttons/switches are sending by logging 'Buttons & Switches'.

Are you sure its not in the system tray? Also try the default hot key - Alt-F. If its not in the tray and Alt-F doesn't show the UI, please attach your FSUIPC7.log file.

Yes, unfortunately. An alternative solution would be if I mapped the received numpad 0-9 keys to their num lock off equivalent. This would allow you to assign in FSUIPC7 with the num lock off, but then use those assignments (when MSFS has the focus) with numlock on. This would be a temporary fix that I would revert once the problem has been fixed by Asobo. Yes, of course. I will raise a zendesk bug report.

Did you try this? This would be a work-around. Doing this, the keys should function when both MSFS and FSUIPC7 have the focus - and numlock is off. That's not quite true! It should work when MSFS has the focus and the num lock is off and you assign in FSUIPC7 with the num lock on (i.e. assign to the num0-9 keys) .If you want it to work when FSUIPC7 has the focus as well, then you can also assign to the keys with no num lock (End, Down, etc). This is because MSFS/SimConnect only sends the numpad keys when num lock is off, but FSUIPC7 receives them via SimConnect and then sends them to itself as if the num lock was on. I'll report the issue tomorrow.

As I said, the issue is that simconnect is sending the numpad keys when num lock is off (when it should be sending them when numlock is on), and FSUIPC7 is receiving these as the 'num lock off' keys (End, Down, PgDn, etc). Did you try this? This would be a work-around. Doing this, the keys should function when both MSFS and FSUIPC7 have the focus - and numlock is off. I don't have a numlock light on my keyboard, so I can't tell when its on or off. I'm presuming its MSFS that has this wrong at the moment, not FSUIPC7, but once confirmed I'll raise this with Asobo. John

It seems that MSFS only sends these keys when numlock is off, rather than on. And when numlock is off, FSUIPC sees these keys as Ins (0), End (1), Down (2), PgDn (3), Left (4), Clr (5), Right (6), Home (7), Up (8). PgUp (9). So, to have these keys working, try with Num-Lock off, and assign in FSUIPC to those keyboard input strings. EDIT: I also have a non-standard (ie. not windows specific) keyboard. I'll try and dig out another keyboard tomorrow and test with that as well.

I've just done some more tests and I think this is an FSUIPC issue.There seems to be a discrepancy between the vk codes between MSFS and FSUIPC. I'll investigate more tomorrow and let you know.

No response that I'm aware of, but its difficult to track these things - or at least I have not found a way. I don't seem many responses from Asobo on the forums, and all I get when I raise a zendesk ticket is, eventually, a 'thank you for your feedback message' saying that it has been submitted. Checking the status of these, they all say 'Solved' but I don't think this means anything - they have that status as soon as they are raised! I'm not sure I included the numpad keys in my initial zendesk bug, I'll check and add if not. FSUIPC7 is trapping them when it has focus, and acting on them if assigned in FSUIPC7. If not, it forwards the keypresses to the sim. The problem is when the sim has focus - its not forwarding certain keypresses (including the numpad keys) via SimConnect evn though requested. John

Please post in the specific sub-forum for FSUIPC7/MSFS for questions relating to this - I have moved your post for you. No, unfortunately not. For xbox, you have to use the WASM interface, and unfortunately this currently does not have the required features to enable FSUIPC7 to be ported to such a platform. We may look at a WASM module at some point, if facilities are provided, but more for enabling specif functionality and to communicate to an external FSUIPC process. But even then, it won't be usable on the xbox platform.

Many of the buttons on the G1000 are currently not controllable via SimConnect. This has already been reported to MSFS/Aspbp amd we are waiting for an update for this to be fixed.

I don't use or have this, so maybe someone else can help you with that. But, I assume its an earlier version of the GFDevP3Dv4.exe, to which Pete commented: So if you use that, you shouldn't use the GFDev64.dll, which is the one you need if you want to use FSUIPC with your device.

Ah, ok - thanks for reporting. Later...although I think the question on VNAV was about the 'Display Vertical Navigation Page' button, not the lateral hold.... ...or about the VNAV in the G1000, which doesn't seem to be controllable either

Ok. You can also try offset 0x0BE8 - Gear Handle Position (4 Bytes), writing 16383 for down and 0 for up.

Ok, thats good to know, thanks. I'll leave them in for the next build release. For FLC, I've added a new offset at 0x0B49, 1 byte, for sim variable 'AUTOPILOT FLIGHT LEVEL CHANGE'. However, this only appears to be read-only and not settable. I've already asked about this over on the Asobo forums (as well as VNAV/VNV) No, probably not at the moment. There seem to be quite a few functions of the garmins (especially the G1000) which are not available via SimConnect at the moment. Actually, looking at the older controls list (not yet added to MSFS or in their documentation), I can see these GPS_VNAV_BUTTON GPS_SETUP_BUTTON GPS_BUTTON1 (also 2,3,4,5) I'll add these back to see if they are recognized and do anything when I get a chance...

Ok, that's good. Make sure you are using the latest version I posted earlier in this thread.

Is that an add-on? I didn't think there was a Mooney included with any version of MSFS. Maybe try a default aircraft. I can't really help with add-on aircraft (that I don't have!).

Its probably sending a press on the up, and a release on the down. Try adding the Gear Down control on the release, under 'Control Sent when button released'. Did you try the checkbox 'control to repeat while held' in the buttons/switches assignment dialog? Yes, in axes assignments. Sorry, I can't help with that as I don't have or know this device. Is there anything in the driver you use for this? Otherwise, you could try looking at the lua Go-Flight Device (gfd) library. See the FSUIPC Lua Library document, from p35 onwards. You will need to GFDev64.dll to use this. There is also a test program called gfdDisplay.lua provided in the lua examples which you could try, although I have recently had a report of some issues with this (relating to BlankAll), which I've not had time to look at (and won't for the foreseeable future unfortunately).

I've added them back and they don't give any 'unrecognized' errors, which is a good sign. Not sure if they work or not though. Could you try the attached build and let me know. I've added back the following controls: AP Panel VS Hold AP Panel VS Off AP Panel VS On AP Panel VS Set AP VS Hold AP VS Off AP VS On AP VS Set FSUIPC7.exe