• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSUIPC key map issue

I've posted over on the QW support forums (two months back) with no response to date so looking for some advice here related to FSUIPC.

In their 787 (v4) I am able to use the keyboard assignments to activate external lights (strobes, nav, turnoff, etc). However, if I use FSUIPC to map a switch to this very same assignment in the sim I can see the switch "jump" for a nanosecond, hear the sound, but the lights don't activate.

I've confirmed there is no repeat set to the keys, etc. A similar approach works on other complex aircraft (all PMDG planes for example) so it seems specific to something in the way QW has coded theirs.

Essentially, while it doesn't suggest anything wrong with their product has anyone been able to work around similar behavior? Thanks!
This is not a product support forum, it is a forum dedicated to developers interacting with developers be they freeware, payware, or personalware.
And this was not a product support request but a question related to FSUIPC's interaction with the simulator in an unexpected way, but thank you for your input nonetheless.