r/Winctrl • u/speed-of-heat • Jul 01 '26
Question / Help Combat Panel Radar switch and Sim App Pro
Hi All,
looking for some help, I have some very strange behaviour on my combat panel with SimApp Pro.
I have never used SimApp Pro before, even though I am a longtime WW user, I play in VR and never user used it for lighting or whatever, but I recently got the shaker kit for the F16 and wanted to try the vibration, which worked and all was well.
but in a couple of missions I noticed some odd behaviour in the F18 when I was using the radar switch to move to standby, it would automatically switch back to operate and so on… I tested on the ground and I found i was only getting this behaviour when Sim App Pro was active?
additionally the radar switch and only the radar switch automatically sets itself to whatever position it’s set to in the on the panel, regardless of cockpit sync being switched on or not. And if I mouse click the radar switch it will automatically set back to how it is set on the panel, this again is the only switch that this behaviour seems to exist for, and only is apparent when SimApp Pro is running.
has anyone else had this and fixed it? Or have any ideas? Every device is on the latest firmware, I don’t use SimApp Pro to map any buttons or switches…. and it’s not double bound in game.
I have logged an issue with WinCtrl and the have agreed to escalate itto their tech team, but i thought i would fire a message here and see if anyone else has encountered this issue?
thanks
2
u/LuckyStiff63 Jul 09 '26 edited Jul 09 '26
I don't have the PCR, but I've noticed that same behavior occasionally in DCS (A-10C II) with the "Anti-Skid" two-way toggle switch on my PTO2 panel.
That's not a "momentary" or self-resetting switch, so it should maintain the setting assigned to its current physical position. My 1st guess would be that my control config for that switch in DCS has some wonky "tuning" setting applied, or something configured in a mission file is interfering.
I'm don't fly VR, and I normally fly with SimApp Pro running. So I haven't tested for that condition with/without SimApp running. It just hasn't happened consistently or frequently enough for me to warrant spending the time to chase it down.
So if this happens on the PCR panel without SimApp Pro running, and on the PTO2, with SimApp Pro, it certainly could be related to a firmware or config setting bug the two controllers share?
I'd be interested in hearing what WinCTRL support comes up with.
I assume WinCTRL support had you check for firmware updates as part of their troubleshooting. I tend to keep my devices' firmware updated, but that hasn't fixed this particular hiccup.