MobiFlight Community Support

OK,

I'm trying to add some controls for the "autopilot" of the Asobo JU-52. The Autopilot system consists of 3 elements:

HEADING SELECTOR
HEADING HOLD
AUTOPILOT ON/OFF SWITCH

It is supposed to work if you switch on the autopilot system, selected de desired heading and then press the heading hold button. In the FSUIPC log I've observed that switching off or pressing the heading hold (to hold the heading) produces an RUDDER_CENTER(0) output while releasing the hold with the autopilot on leads to a continuous feed of RUDDER_SET plus a parameter which depends somehow on the difference between current and desired heading.

So long I've been able to monitor desired and current headings by using SimConnect/(A: AUTOPILOT HEADING LOCK DIR,Degrees) and FSUIPC Offset 0x0580, so I think I could end figuring how to transform that to the RUDDER_SET magic number.

However, for the HEADING HOLD and the AUTOPILOT ON/OFF SWITCH I'm completely stuck. I've discovered some items selecting SIMConnect and then Get Item From List. There are variables for something called SWITCH_Autopilot_Notaus, XMLVAR_AP_DISENGAGED, XMLVAR_AUTOPILOT_ACTIVE, XMLVAR_AP_HEADING_HOLD and similar ones which sound me OK, but I haven't been able to interact with them in any way.

I think I may be on the track, but I'm absolutely lost, can anyblody help me?

Hi

Basically..... For FS2020 i would stop thinking about FSUIPC Data.....
We NOW have our WASM Tool.... So we can Read the same ( and many more) Data as FSUIPC will do.

Means in easy words.... Our system is sometimes deeper then FSUIPC..... But its never below FSUIPC ( Cause FSUIPC simply use the same data source).
So..... Using FSUIPC is ( for FS2020) no longer a good option anymore.

About Problem.

Badly Mobiflight currently have no access to all Variables ( e.g. the B:Vars or O:Vars ) are still blocked by Asobo.....
Badly speccialy in Asobo Stock and AddOn Aircrafts these guys use many of this "secret" Variables......
Irronical AddOns like FBW Airbus use now the Lvars, KVars and AVars we still be able to read.


********************
Solution:
May your Problem is in case the used Variable is currently not readable...... But then fir sure also FSUIPC is not be able to read it !!!!
OR
You make just a mistake.... and Var is available but you simply use the wrong one.


To Solve:
I can not help ( Not use/own the JU52)
Please join our DISCORD Server https://discord.gg/99vHbK7
Request in the FS2020 subsection.
Then a advanced User ( with Ju52) can simply check your situation ( may via Shared Screen) and can tell you if there is a way or currently not and you have to wait until Assobo "open" then Vars also to 3rd Party Software like MF.

Hi,

Yesterday after reading your reply to my post I tried to translate my FSUIPC-based to Simconnect variables and I was quite successful. However, while with FSUIPC I could action the controls in the sim and watch in the FSUIPC console which OFFSETs where triggered, with Simconnect I'm absolutely blind. Is there any way to monitor those or at least any documentation?

Also, I've never worked with these vars, so all that Lvars, KVars, AVars, OVars, etc. sound at me like Chinese, what are those? And more important are all of them R/W or are they Read Only?

Thank you very much.

Best regards,

Jorge

To explane it in a easy way.....
(Hopefully all correct... Thats the Info i learned myself years ago)

FSUIPC build ( in the past) a PlugIn ( DLL file) that was impliment into the Sim itself
Basically they do nothing else like Read hudge Data Areas and "split" this raw Informations into there "Offset" List.
So for example they read a 100 Number long Value and say... The number from point 8 is the status of the Parking Brake LED ..... So the say in there Code "Write" this data to our own Offset Range Slot number 0BC8 Fil it with 16 Zeros 0000.0000 0000.0000 in case of "0" Raw .... Or Fill it with "1111.1111 1111.1111" if "1" Raw.
Thats why the Offset not show "0/1" it show "0/32767"

In the Past this was the only way for Mobiflight ( we not have our own DLL and we not comunicate to Simconnect)..... So we also use this FSUIPC Interface !

With FS2020 we have WASM ..... Now we can check the Internal Data ( Read and Write) Directly. There no longer exist a "Offset List" ..... We simply call the needed Variable by it´s name.....

How to Observe
You use the DEV Mode of FS2020. ....: There you open the "logging" Window from FS2020 and you can check every single Variable that is currently in use.
Whatever this Vid is outdated and the new VErsion looks a little different..... This will show you what i mean !
https://www.youtube.com/watch?v=PKBjEl9E5A4

NOTE: Please NOT follow the second part of this Video..... We no longer need to enter this stuff by hand..... Thats what is outdated, too.

Now we have "HubHop" .... A large List of available Variables in FS2020..... Build by our Users.
Simply come on Discord.... There you find a lot of informations and you find people who know all variables and can help !

Hi,

I've doing a little research setting the Dev mode, and unfortunately I discovered that the VARs affecting the JU-52 autopilot system apparently are O vars and B vars, so I assume I will not be able to manage it.

Let's wait and see if ASOBO finally unblock those (is there any sign that they will eventually do so?)

Anyway I will try to ask in the Discord, just in case (although I don't know if my English will be enough for a technical conversation)

Your English pretty sure will be enough.
Most of us ( expect the users from US and GB ) just speak english as second language..... Thats no big deal ! In worst case we still have google translator !

About Asobo....
Vote for our request...... https://forums.flightsimulator.com/t/enhanced-api-to-access-all-aircraft-state-and-trigger-all-cockpit-functions/454608
As more people push this , as bigger is the chance the devs see a benefit and impliment this a.s.a.p.

Didn't know there was an ongoing initiative!! I have just voted it

EDIT: Wow, I've just seen that our proposal is Top20 and with the strongest up trend. Let's hope ASOBO will listen to us. In the end, I think they're the first interested, the more enjoyable the sim gets, the longer life it will have...

Badly here i´m not so optimistic......

For sure.... Cockpitbuilders, homesimmers and flight/aviation enthusitatic people like wa all together keep FSX/P3D alive..... And we all order FS2020 on the release Date.
BUT
Ask yourself why Asobo/Microsoft spent so many energy and time into the XBOX 360 Compatibility.......
They want to earn money from the "Casual" Users..... The Hardcore Users (we are a part of) are NOT the main customer group !

I also hope they will change opinion in the future.... and hope they see the cockpitbuilders will pay 10$ permonth for the sim..... Same time when Xbox user already delete FS2020 and play another trash game like "Drug Dealer Simuator".
But my first impression of the Asobo Policy..... We are not important enought..... If we would be the target group, then rthe requested API would be available on first day...... And things like "Console Game Pads Controlls" would not be on the ToDo List of Asobo...... Ask yourself.... What professional Sim Flyer use a "Gamepad" for the Sim ??


Whatever.... I be hopefull that Asobo hear our request!...... Lets wait !

play another trash game like "Drug Dealer Simuator"

Well, let's cross fingers... I think that XBox users will abandon the game soon. Harcore simmers may stay and continue spending money, but just if the experience offered by the sim is really "harcore".

Maybe not first priority, but if it doesn't take many hours it could become reality eventually