SkyCamel

Good to know, I'm used to use these // from the FSX.cfg times so I thought what the heck 😉 I started without Specific Profiles in FSUIPC but once I got the FBW a32nx I decided to switch to Specific profiles but I wanted to keep certain things just as "reference" I already decided once I'm finished with the C208 I'm going to clear all of this out, it's getting way to messy. Cheers, Luc

That works perfect, thanks John! Up to the next hurdle 😃

Attached the requested files Cheers, Luc FSUIPC7.ini FSUIPC7.log

I just can't figure out why this is not working with FSUIPC7. Attached is a screenshot of the FSUIPC console output. I programmed one axis in MSFS as Condition lever and another axis with the same function but in FSUIPC. The MSFS axis is working properly but the FSUIPC is not. The top half of the console screen is what I get when I move the MSFS axis the bottom half is the console output when I move the FSUIPC axis. The controls look the same to me assuming that the lines starting with *** is the feedback from MSFS. Any help would be appreciated. Cheers, Luc condition_lever.pdf

It look's John that your search capabilities are better than Google as I used Google to see if I can find anything about this issue but it didn't 🙂 I've been using FSUIPC4 with FSX for years and I never experienced this problem, so I thought. And just to be sure (not that I didn't believe you 😉 ) I started up my FSX and yes, same thing happens with my MCP. And then it came to me, I always used LINDA for my MCP because they had a module for my PMDG 737 so I only used FSUIPC for my joysticks and axes. So I'm guessing that in the Lua script (or whatever) that LINDA is using they do exactly like you proposed as solution, putting the same command in the Press and Release so it's working as expected. If my understanding is correct, the push buttons on the MCP trigger a bi-stable flip-flop so to speak and FSUIPC see's either 1 be set or in the next press 0 been set. This has kind of an interesting side effect. When some functions only have either an ON of OFF but no TOGGLE you could create a toggle yourself by just putting the ON in the PRESS and the OFF in the release so it would just toggle every press cycle. That of course only in the VRI MCP as for joystick buttons that would not make sense at all 😀 As always John, thanks for your insight (and good memory) Cheers, Luc

I'm using the A32nx-DEV but I have the exact same problem with the default C208. Actually when I started this thread it was about the C208, I even didn't have the FBW installed yet. I was thinking that maybe it had to do with LINDA so I took everything from LINDA out and the buttons I used for testing were actually setup in FSUIPC. Please see the attached ini and log without LINDA Cheers, Luc PS Also, when I go into FSUIPC7 assignments/Buttons&keys to program a MCP button also there I have to press the button twice before it will show up in the "PRESS" and "Button" input FSUIPC7-2.zip

Sorry about the late reply, have been trying to figure out so many other things .... So attached is the log file. I noticed that there's a lot of "jitter?" with Throttle_1_set so it's kind of annoying in the log, I've to see how to get rid of that. It look like the problem only occurs with the VRInsight MCP v1. First I manipulated switches on my Saitek Flight Yoke with first entry beginning at 396515 Button changed: bRef=0, Joy=1 (E), Btn=15, Pressed 396515 [Buttons.Airbus A320neo FlyByWire] 6=PE,15,CPA32NX_OVHD_FUELSYSTEM_LTKPUMP1_TOGGLE,0 An every push will change the state so that's ok. When you jump to this line; 422187 Button changed: bRef=0, Joy=258, Btn=16, Pressed 422187 [Buttons.Airbus A320neo FlyByWire] 19=P258,16,CPBEACON_LIGHT_SWITCH_TOGGLE,0 there the problem manifests itself both with the Beacon light and NAV light toggle. Every time I have to press the button twice for it to be "executed". (this is on the MCP v1) Any idea what the cause might be ? Cheers, Luc FSUIPC7.zip

Sorry, I feel stupid, but I can't find how to register my key 😞 I checked the user guide and googled the only thing I found was that I should uninstall/reinstall? But I don't want to loose the work I did so far. Your advice would be welcome, Cheers, Luc

I've been playing around with FSUIPC for a while and got great support so I will now get my own license key. But in future, after I finish all the programming with FSUIPC7 (which is still a lot) I would like to do some testing of the WideFS. If I have my own key, can I still revert back to a trial key just to test out the WideFS client? Cheers, Luc

@John Dowson@bobsk8 Success! So, PF3 automatically registers the Hotkeys when connecting to FS and with version 7.3.20a everything is working fine now. Thanks so much for the support Cheers, Luc

Thanks John for the info, I thought that it would work with the latest official version 7.3.19 but I read over your comment to then install the .exe from 7.3.20a 😞 I will do that. How to get these hotkeys registered also puzzled me as I saw that in @bobsk8 log file that those hotkeys where registered/declared. Reason why addressed my question to him, but good thing you answered too because I would not have used the 7.3.20a 😉 Cheers, Luc

@bobsk8 I'm struggling with the same issue. I want to send hotkey "0" and hotkey "ctrl+shft+T" to PF3 but it doesn't work at all. Could you please give me your insight on how to get this working? Thanks, Luc

I have this strange behavior on my MCP. The first time after starting FSUIPC7 the button press is directly detected with the first press. But once I used a button, next time I have to press twice for the button to be detected. This for all buttons. Even the rotary encoders will only be detected after the second "click". Also when I pressed a button and then go on pressing other buttons, when going back to this first button pressed it will "remember" that I pressed it before so only one press is needed then. Any idea what creates this behavior? Cheers, Luc

These are recognized by FSUIPC7 as buttons, P256,21 slow clockwise, P256,20 fast clockwise and than P256, 23 or P256,22 counter clockwise. I could use the push button of the encoder to set a flag to change the function of the encoder, but I would like to find a way so that it will automatically revert back to the initial function, basically automatically resetting the flag, hence the timer condition. I looked into the Lua programming and examples but I fear that will be way over my pay grade 😉 On top of it, the function I need is a "Preset Control" which I'm not very clear if that would even be possible with Lua. Anyhow, I will try to figure something out Cheers Luc

I'm trying to program my VRInsight MCP v1 buttons and rotary encoders without the use of LINDA. What I want to achieve is that I can use one rotary encoder for different function by setting a timed flag. In LINDA they use a button on the MCP to switch to different modes (1,2,3) by pressing repeatedly one button. The MCP will stay in the selected mode as long as you're operating a button or rotary encoder and will reverse to mode 1 after a preset delay if nothing is happening on the MCP. I found in Advanced User Guide that it is possible to set a flag by pressing a button and make this a condition for another button's function, but it's not clear how to do that for rotary encoders and how to have a timer as condition. Does anyone know/can help me to achieve what I described above? Cheers, Luc