I don’t know about that but did you try to lunch at the same time both of them and tried to make sure IF was the only tab open on your device ? This is what I do when connecting state stay on my laptop.
I had an odd issue recently: the joystick motion is sensed in settings, but the aircraft control surfaces don’t respond to joystick motion, it only responds to buttons being clicked. Anyone happen to know a fix to this?
After the configuration of your axis on map connect, you may have to go on IF settings, click on axis you want to set and then move the joystick in regard to the axis.
That’s what I did, that’s why the joystick motion is sensed in IF settings, but when I spawn an aircraft the control surfaces just don’t move.
If you launch Map Connect and connect to IF before spawning into a flight, I believe you may need to refresh the manifest in Map Connect after spawning. Otherwise Map Connect may not be able to send the correct commands for the aircraft that has spawned in.
Is refreshing manifest after spawning something I’m supposed to be doing? For the longest time I didn’t do that and there was no issue up until recently.
I’m not sure - it’s just a suggestion as if you haven’t spawned there could in theory be a mismatch between the initial manifest Map Connect fetches and the manifest after you spawn. But I am neither a heavy user of Map Connect nor one of its devs.
I am just suggesting it based on the way the IF Connect API works in theory.
So would you say by connecting to map connect after spawning, I can avoid that issue and having to refresh manifest?
I’m just suggesting that might be the case. It’s just a theory for you to try.
1 Like
Hey I was wondering winwing joysticks work with map connect v2
Well I tried both, still the same issue, joystick motion sensed in settings but no control surfaces response. I even tried using another device and still the same issue.
I guess you’ll need help from the application developer.