MobiFlight Community Support

Welcome to the forum for MobiFlight! Feel free to reach out to the community in case you have questions, issues or just want to share great ideas or details about your latest home cockpit project.

You like MobiFlight? Donate via PayPal and support the MobiFlight development. Thanks! 

05/03/2024 - This forum is read-only

The community support for MobiFlight has moved exclusively over to our Discord server. Register for free and enjoy more interactive functions like image and video upload, voice chat. More than 7,000 registered users around the world make it a great experience!

See you on our MobiFlight Community Discord server.

A HUGE Thank You to everyone who participated in the forum, especially obviously to Pizman and Stephan who did an outstanding job over so many years providing an incredible service to the MobiFlight community.

The forum is still providing a lot of good content, hence we keep this information accessible.

icon
Avatar
Julesta
Posts: 129
Hello.

I´m happy with MB, until version 6.0. Why?, because all my programming for: Autopilot, Lights & buttons, 2 LCD displays and 2 encoders, etc, with a lot of values are erratic. Values impossibles, and moving the encoders I have impossibles values. I do not why, because that I have had to come back to MB 9.2.0. No problems with it. I can´t read any other gay with the same problems, buy if anyone has an idea I´m ready to buy it.

Thanks
2022-12-14 20:49
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Hi

I expect your effected of a bigger problem we got with 9.6.0
We implment there already a big new feature in the back (Modifier) but its not already vissible and useable in the front ( will come with 10.0)

The big disadvantage we not understand and prevent is that now Values that are Float (decimals) get pushed above the Transform field.
In the past there was a automatic truncate there. In the future there is a option to do the truncate (within the modifier tool)

That means.... Badly for now ( post 9.6 but pre 10.0 ) we have a periode where floats can get problematic but there is no GUI Feature to avoid this.


Solution:
You must simply avoid this situation in configs where you get in trouble by a little rework.
(Mostly only P3D Users ar effected.... FS2020 work way better and thats why our testings not show these problems for us)

So.... Use the "Truncate" or the "Round" !

Lets say for example a Config that occure in trouble got the Value 12,34567 But the Display get struggle cause it can not already handle floats.....
Simply say: Round($,0) in transform ..... Or ..... Truncate($)
Then 12,34567 is once again 12 like in the past and all work like before.
Good Luck !
2022-12-29 16:18
Avatar
Julesta
Posts: 129
Thank you this answer. I´ll try it until the new version 10

Happy New Year, and many thanks for all your help until now. It´s a great pleasure.:) :) :) :) :) :) :) :)
2023-01-03 21:53
Avatar
Julesta
Posts: 129
Hi.

I just TRUNCATE all the values that gave me problems and now all is Ok.

Thank you very much. Your help is nice and clever.:thumbup: :thumbup: :thumbup: :thumbup:
2023-01-03 22:15
icon