Hi guys! So I try to bind the encoder knob of honeycomb bravo on the alt setting of the autopilot.
The encoder is laggy though. I turn the knob and it registers a lot fewer "clicks" on the autopilot unit. It is like it doesn't register some of the clicks.
Is there any setting that affects that?
#Honeycomb Bravo Settings Knob Skipping Clicks
broken fable
Ok I just noticed that even turning it slow some clicks are not registered.
After testing a little I notice that even when I scan for input in the input configuration not all the cliks are registered. There is a pattern. it registers a few in row then skips one then registers a few more then skips 2 then registers one skips 4. something like that. the registers and skips are not exact as I mentioned them but they are repeatable. I mean after a hole circle the pattern repeats.
If I use the knob via the msfs setting in the simulator all clicks are registered normally
Honeycomb Bravo Settings Knob Skipping Clicks
wintry ginkgo
Always specify simulator, vendor and aircraft.
broken fable
I am using msfs2024 and piper dakota but I find that the issue is not related to the simulator but to the communication between the bravo quadrant and mobiflight.
When I configure an input, if I press scan input and rotate the encode one click, some times it registers and some times it doesn't register. I thought maybe there is an issue with the hardware but I notice that if I map the encoder directly in MSFS 2024 every click is registered and the alt setting moves a lot faster
and it doesnt matter the direction I turn it. it keeps a specific sequence on how many clicks it skips and how many it registers.
broken fable
So guys does anyone have any ideas?
molten tulip
It's just a button. However fast we can process the button events is how fast we'll send them
look in the log message and see what you see, it should show one log message per click
wintry ginkgo
He said Mobiflight skips clicks. Could this be an issue with the new UI?
teal falconBOT
To help diagnose your problem we need to see your MobiFlight logs. Follow this step-by-step guide to provide them: Providing logs from MobiFlight
broken fable
Sorry for late response. I have the latest mobiflight version. It is not a matter of how fast I turn the knob because this happens when I turn it very slow too. As I said it seems to be a certain pattern of how many clicks it logs and how many it skips, no matter the direction. For example I even try to move the knob one click right then one click left then one right then one left again and again and it stills follows a certain pattern of how many clicks it registers and how many it skips. I will check for the logs when I get back home and I will also try to note down the sequence of the skipped and missed clicks too if that may help.
broken fable
I did a series of encoder clicks and I was watching the log if it was registering. it wasn't registering every click. below is the series of clicks 0 for skipped and 1 for registered
00101111110111111001000001100000101011011101
brisk jackal
if you open windows joystick properties does it register every pulse there?
broken fable
give me a moment
No...
but if i bind the encoder to the simulator setting. it registers every single pusle
molten tulip
If you don't see every button click in windows joystick then it's a hardware issue. We get the same messages windows does
broken fable
ok. but how come does it work on msfs if I bind it directly? it seems very odd....
molten tulip
Not sure, but it is just a button hiding as an encoder. If we aren't getting the clicks from the hardware there's nothing we can do
broken fable
here is how well it works on msfs bound directly from settings
and this is a fast scroll which works correctly
molten tulip
I'm not sure what else I can add. I haven't had issues with my Bravo. If you aren't seeing all the turns in the windows joystick UI, then it seems hardware related
broken fable
I understand. The thing that confuses me is as I said the fact that on msfs24 if I bind it directly, it registers all clicks normally....
So maybe it is an issue with how windows communicates with it or something
broken fable
I just noticed that the exact same thing happens with the trim wheel too.
Windows joystick doesn't register every click of the wheel. but when I bind the wheel on msfs directly it works fine. and it also works fine when I use the trim wheel with vJoy. Anyone has any idea what to look for?
Could the fact that I have vjoy installed create the issues I see?
and I just tested something new..... I maped the button via vjoy as a virtual button and then created an input on mobiflight and added the virtual button from vjoy.
So when turning the knob It should have 2 inputs
what happens? it registers every vjoy input but skipps some of the normal inputs
here is a screenshot so you can see it
very odd
wintry ginkgo
Have you tried not loading Vjoy? There is a report of incompatibility with the latest version of Vjoy.
broken fable
I need to try to uninstall vjoy and see if the issue goes away probably
broken fable
I uninstalled vjoy and the issue still exists.
broken fable
I think I found some more evidence... So.... In the authentikit settings where you map a button to a virtual button to vjoy there is this setting
if I set the "hold output on After... (ms)" to 0 then the vjoy input skips in mobiflight light the normal input. So my guess is that sometimes the click is very fast and windows joystick settings don't register it. but when bound directly to msfs for some reason msfs registers it.
vast notch
hmm this is strange indeed. Does it make a difference if you unbind it on MSFS?
no wait, authentikit has some software of their own? Does the problem occur without that running?
@broken fable is that software downloadable somewhere btw?
broken fable
Sorry for late response. I was away.
So. If I don't run anything and bind the knob directly inside of msfs. It works without skipping any clicks.
If I run only mobiflight the knob skips clicks. Because as we said, windows controller skips the clicks already.
All these with vjoy and authentikit uninstalled/not running.
If I bind the button to a virtual button on Vjoy using authentikit, and using the hold output after 1ms and then configure that vjoy button as input in mobiflight. Every click is registered when I turn the knob one click at a time. If I keep rotating it it registers it as a hold* (asterisk because I found a cool function which I will explain later on this)
If I bind the button to a virtual button on Vjoy using authentikit again but using 0 in the hold output on after... (ms) and then configure that vjoy button as input in mobiflight, then it skips the same as the original input in mobiflight.