MobiFlight Community Support

Hello all,

I notice that debug logging mode made MobiFlight Software response to switches and rotary encoders slower and slower after 10 -15 minutes that I started connection to FSX. Debug logging mode is good for detect ON/OFF switches and push buttons. For the rotary encoders, it is good when first start the connection but from time to time it response slower and slower. I must exit the program and re-open to make the rotary encoders working good again.

Here is the link of video. https://www.youtube.com/watch?v=TKiUzmvDVfE&index=1&list=UUDMdeKW-BtIT9vIk3o7YSVA

Does anyone having experience this problem and how do you solve it?

Thank you in advance.

Do you have the "Missing Input" Problem..... Only then Logging Debug is temporary needed..... If your system not have this issue then simply not use Logging Mode !

Do you have the "Missing Input" Problem..... Only then Logging Debug is temporary needed..... If your system not have this issue then simply not use Logging Mode !

Yes, I have "Missing Input" problem. That's why I activated Debug Logging but it slowed down input reading from rotary encoders. It would be great if encoders can work with Debug Logging like toggle switches and push buttons.

Hi again.
My appology for that !

I know how bad this is, cause i got also the logging Debug Problem on my Computer....
I not know if there is a encoder Issue cause i not have a full cockpit and i not make testruns while flying long stints..... So my experience is low there.

The MAIN Problem:
Sebastian NOT have this bug (like 90% of Users, too) ... So only a small group got this and it is not possible to detect the issue until now.
Wo spent lots of hours with testing Beta Releases on my PC but nothing was succesfull.

Solution.
I know thats not perfect and you not want hear it.... But myself i decide to realise my final Project in a DUAL System with a EXTERNAL solution for maby 30-40% of Inputs.

The "missing Commands" are only problematic at "Switches" and "Rotary Switches" ....
A Momentary Push button is not critical. Whatever the command works in 90% of trys..... If not we can simply push again.... there is no issue if a Command is not reach the sim.
ONLY the Rotary Switches and NonMomenatry Switches like ON/OFF Light Switches are problematic cause when missing a command the REAL Switch is in WRONG Position in Homecockpit.

So my planing: I will NOT use Logging Mode to prevent all this Problems like you reported..... And i will only set Momentary Buttons via Mobiflight ( And Encoders ) ..... The problematic Switches and Rotary Switches i looking forward to set with Joystick Controllers direct in FSUIPC.

Summary.... Then i got already the bug... But i not care about cause the problematic parts are out of System.

************
I realy Hope we get the solution to SOLVE this bug in the future.... But i can not garantee we can do this ever.

Hi again.
My appology for that !

I know how bad this is, cause i got also the logging Debug Problem on my Computer....
I not know if there is a encoder Issue cause i not have a full cockpit and i not make testruns while flying long stints..... So my experience is low there.

The MAIN Problem:
Sebastian NOT have this bug (like 90% of Users, too) ... So only a small group got this and it is not possible to detect the issue until now.
Wo spent lots of hours with testing Beta Releases on my PC but nothing was succesfull.

Solution.
I know thats not perfect and you not want hear it.... But myself i decide to realise my final Project in a DUAL System with a EXTERNAL solution for maby 30-40% of Inputs.

The "missing Commands" are only problematic at "Switches" and "Rotary Switches" ....
A Momentary Push button is not critical. Whatever the command works in 90% of trys..... If not we can simply push again.... there is no issue if a Command is not reach the sim.
ONLY the Rotary Switches and NonMomenatry Switches like ON/OFF Light Switches are problematic cause when missing a command the REAL Switch is in WRONG Position in Homecockpit.

So my planing: I will NOT use Logging Mode to prevent all this Problems like you reported..... And i will only set Momentary Buttons via Mobiflight ( And Encoders ) ..... The problematic Switches and Rotary Switches i looking forward to set with Joystick Controllers direct in FSUIPC.

Summary.... Then i got already the bug... But i not care about cause the problematic parts are out of System.

************
I realy Hope we get the solution to SOLVE this bug in the future.... But i can not garantee we can do this ever.

Hi pizman82,

Thanks for sharing your experience. As you said the "Missing Input" is problematic for ON/OFF Switch. I use MobiFlight only for MCP of 737NGX. I did my own solution by adding some offset to the ouput page for checking the position of the switch in simulator eg., F/D switch. If my physical switch is ON but it missing detected, that is not the problem. I just switch my physical switch OFF and ON again. But I just noticed the problem of rotary encoders in Debug Logging Mode 2 days ago. Normally, I never enable the debug logging mode. Before I start this topic, I searched in this forum and found peoples talking about "Missing Input" of push buttons and ON/OFF switches and they enable debug logging mode to solve the problem. But no one talking about rotary encoders in debug logging mode. That' s why I start this topic and may be someone can share experience or solution that I never know before.

This is the best donated software I ever see in the world of flightsim. Thank you to Sebastien for keeping up good work and you (pizman82) that jumping in almost every topics in this forum and sharing your experience.

Thank you for your praising words

Your encoderproblem was still reported by 1 or 2 users in the past....
But same Problem. Sebastian NOT got this problem.... We are not be able to find out the reason.
The Code looks perfect.... and additional the "Logging Mode" does nothing different ( Only create a text Output of 1 line you see in the Debug Window).
Its shameful but we not know WHY the Debug Mode solve the Missing Input problem... or Why it slowdown encoders after a while.... Cause it basicly do the 100% same like the normal mode. THATS a real tricky problem !

About the improvisional solution.

I agree.
We can simply turn the Switches On/OFF/ON again if a command is not recive by the simulator..... The Real problem is if we get no indication for that ( In some cases)

For example:
FlightDirector Switch : here it´s like you say.... If FD Axis not in Display or the LED is not lightup then we simple "reset" ist and everything is fine.
BUT
LogoLights.... There we have no indication if it´s rely ON in the Sim.... Or for example AutoBrake for Landing.... there is no Display or LED that show us the status of Auto Brakes.
Or for example the Presserusation switches of Packs.... You only see if switch is working correct if you check the gauge .

Summary.... Some switches can be used cause you "see" the status somewhere else or you realise the issue same moment..... But lots of other switches have no usefull indication..... THERE we need to "trust" in the Switch position to confirm if System is ON or OFF.