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!
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.
First of all I would like to say hi to all of you folks! I started using Mobiflight very recently and it's a great piece of software!
I have some issue with the key inputs in the MFConnector.
I configured some button to trigger an keystroke. It seems to be working fine because when in offline mode and pressing my button the keystroke actually is triggered (tested in notepad). However for some reason my Prepar3D V3 doesn't receive this keystroke.
Is there is some special step to be made or it's a bug?
Please get shure your P3D is ACTIVE ! ( Not shure if there are exceptions but normaly the target System must be ACTIVE Window to recive Keys.)
Additional you should run MOBIFLIGHT and P3D in ADMIN MODE....
I don´t know your Windows version.... Just rightclick the startsymbol and open "settings" and enable " Use Administrator mode"
Some people report that is enough if Mobiflight is in Admin Mode.... others say Simulator must be in Admin Mode .... Again others say BOTH must be in Admin Mode.
Myself i run ALL Programms on my Computer in Admin Mode and have no problems....
Do you use FSUIPC (Payware).
Status FSUIPC ok in Mobiflight?
Do you use a default aircraft or a 3rd party aircraft like PMDG or majestic?
I'm using the payed version of FSUIPC and it's connecting correctly.
Additional you should run MOBIFLIGHT and P3D in ADMIN MODE....
That was a problem! I always run P3D in admin mode but wasn't running mobiflight in admin mode! Thanks a lot!!
I have two more questions (and probably more later .
1. I'm trying to do an acceleration for the rotary encoder for the heading. In the rotate fast tab I set it to the FSUIPC type with offset 0x07CC (from the presets) and in the Set Value field I placed $+20 but it doesn't do anything. What I'm doing wrong?
2. Is it possible in the input preconditions use an pin state? I have an encoder and I would like have different funcionality when rotating with button pressed and different otherwise.
That was a problem! I always run P3D in admin mode but wasn't running mobiflight in admin mode! Thanks a lot!!
So the Key problem is solved ??? .... I will mark the topic als SOLVED....
On next time please open new topic for new questions .... then other people can find it, too !
About your 2 new requests.....
1. Your basic idea is correct.... But you use wrong value !
Please check the FSUIPC Offset List !
Offset : 07CC .... Size: 2 Byte Typ INT Autopilot heading value, as degrees*65536/360
that mean a value of 1 Degree is calculated 1*65536/360 =182,04 so roundabout 182
$+182 means +1° to get 20° Step ( Absolutly to much i think) you need $+3640 .
You also must find out if there is a "override protect" in this offset.....
If you are at 0 degrees ( Value 0) and say On Left $-182 THEN this can occure in problem if Simultor not solve this internal.... Cause after 0° on left must come 359 and NOT -1.
In that case you need a IF Condition to say.... IF Value is bigger then 1 Degree ( Maby exact 182) THEN $-182 ELSE Set Value to 359° ( Maby 65536) .
Same Problem "on Right" from 359--->000 Here a simple +182 can be problematic, too cause you reach end of Byte range !
(( But maby FSUIPC can handle this itself automaticly..... i don´t know cause i not use standard aircrafts or this offset))
Finaly.... I would recommend to use EVENT ID instead of Offset Inputs in that case....
For a simple ON/OFF Boolean 1/0 Offset this is easy.... But those decimal Values can be tricky.
Also for a Heading selector "normaly" a On Fast is not needed. (Only for Altitude selector)
BUT: Do it like you want..... Just try out and make the system you like much and that work perfect for you !
*****
2. This is not possible at the moment directly ( Maby in far future we will implement a "Real Button state" Readout.) Until then you can use a simple improvisional system to make those things possible..... You use a "Custom Offset" to write there the current state of a Button ( offset is write to "1" if button is pushed and write to "0" if button is released)
THIS offset then must be readout in a output Config and then you can use THIS output config for a precondition ( Sorry for that difficult workflow at the moment)
Supporter
.