roarkr

I believe "Is MSFS using updated data but not applying this to the sceneries?" could be the cause of this problem. If that is the case then MakeRwys can't be used to get the correct airport info by reading the BGLs. Anyway, thanks for your reply. Data from Little NavMap also give different Heading values for airport runways than those found using MakeRwys. They are the same as found with SimConnect. Conclusion: MakeRwws data is not correct. and time to skip it.

I do have issues when reading the correct heading of runways with MakeRwys 5.13. Example: KSEA runway 16L,16C and 16R Headings of runways when reading from Runways.csv( the other Runway formats have the same issue) KSEA 161 47.46379 -122.308 433 161 11890 110.3 KSEA 162 47.46383 -122.318 415 161 8493 110.75 KSEA 163 47.46381 -122.311 430 161 9418 111.7 MagVar for KSEA is 16, so it is 177 compared to 180 via SimConnect. When I read the heading via MSFS's SimConnect FacilityRequest i get 180 I am not saying that MakeRwys gives faulty data, but why do I get different results. When I use the data from MakeRwys in my app, my airplane is not alighed correctly with the runway heading, but with a offset of 3 degrees. When I use the data from SimConnect in my app, the airplane is correcly align with the runway heading in MSFS. It is not only KSEA, I just used it as an example. This issue was not there before. Could it be something in the latest MakeRwys version?

The free MSJOY from rksoftware can bind any PMDG Event MSFSJoy is the ultimate joystick button utility for the PMDG 737 for MSFS airplane in MSFS. Bind any PMDG 737 for MSFS airplane switch, knob or button to a joystick button. Now includes "Test Events" for more easy and correct bindings. If you want, you can bind the complete airplanes setup from Cold and Dark to Takeoff to only one joystick button.

I can bind the new Custom Events to both Buttons and Keypresses with FSUIPC. In my own WASM I can send HVars e.g. command = "(>H:A32NX_RMP_L_VHF2_BUTTON_PRESSED)"; execute_calculator_code(command.c_str(), nullptr, nullptr, nullptr); and it will trigger the VHF2 Button But, when I try to use the same code for one of the Custom Events in the list above, e.g. A32NX.FCU_AP_1_PUSH command = "(>H:A32NX.FCU_AP_1_PUSH)"; execute_calculator_code(command.c_str(), nullptr, nullptr, nullptr); it will not trigger the FCU button I must miss something. Are these A320NX flybywire Custom Events not H Vars?

Got it working, my fault

After several months away from MSFS and FSUIPC and just started up again. I have FSUIPC v7.2.8 installed with the WASM module active in MSFS's Community folder and fly the A32NX(flybywire v6.3) I can't get the binding of H:Vars(Events) to work. I have a fbw.evt file in the FSUIPC7 folder [Events] 0 = A32NX.FCU_AP_1_PUSH 1 = A32NX.FCU_AP_2_PUSH 2 = A32NX.FCU_AP_DISCONNECT_PUSH 3 = A32NX.FCU_ATHR_PUSH 4 = A32NX.FCU_ATHR_DISCONNECT_PUSH 5 = A32NX.FCU_SPD_INC 6 = A32NX.FCU_SPD_DEC 7 = A32NX.FCU_SPD_SET 8 = A32NX.FCU_SPD_PUSH 9 = A32NX.FCU_SPD_PULL 10 = A32NX.FCU_SPD_MACH_TOGGLE_PUSH 11 = A32NX.FCU_HDG_INC 12 = A32NX.FCU_HDG_DEC 13 = A32NX.FCU_HDG_SET 14 = A32NX.FCU_HDG_PUSH 15 = A32NX.FCU_HDG_PULL 16 = A32NX.FCU_TRK_FPA_TOGGLE_PUSH 17 = A32NX_FCU_ALT_INC 18 = A32NX.FCU_ALT_DEC 19 = A32NX.FCU_ALT_SET 20 = A32NX.FCU_ALT_PUSH 21 = A32NX.FCU_ALT_PULL 22 = A32NX.FCU_ALT_INCREMENT_TOGGLE 23 = A32NX.FCU_ALT_INCREMENT_SET 24 = A32NX.FCU_VS_INC 25 = A32NX.FCU_VS_DEC 26 = A32NX.FCU_VS_SET 27 = A32NX.FCU_VS_PUSH 28 = A32NX.FCU_VS_PULL 29 = A32NX.FCU_LOC_PUSH 30 = A32NX.FCU_APPR_PUSH 31 = A32NX.FCU_EXPED_PUSH I can't get any of these Events to trigger any FCU activity when I bind them to either Buttons or Keypresses See attached image. Anyone knows what I am doing wrong here? flybywire-aircraft-a320-neo

Not working for me. As soon as I click File/Start it connects, but freezes. Not able to get into any of the menus. Then after a while it closes. I am running latest MSFS version released yesterday.

Does anyone know if there is any offset to check if the A320 is in MANAGED or SELECTED mode for IAS, HDG and ALT? I need this to display correct info in the corresponding displays on my hardware.

I am maybe dumb today, but logging events in FSUIPC with the A320 running gives me continues logging of the same events over and over. It is impossible to trace anything. Something looks weird. Is there a filter option to set? You said: "swapping the COM1 in the UI". What do you mean?

When binding a COM1 Radio Swap to a key it works fine with the default airplanes in MSFS , but not when using the A320 and B787 airplanes. It is the same problem with the INC and DEC controls. It seems to me that these airplanes(A320 and B787) use some other logic than the standard SimConnect Events / FSUIPC Controls. Is there other Events / Controls to be used for these airplanes?

I am a little confused. Can someone enlighten me to understand. With these new events in the lists above. Do I need an updated WASM module? Where can I find that? Or is the already released WASM compatible with this new events?

Hi, Thanks for replying. I will try it.

Hi, I am using P3Dv4 with FSUIPC 5 and have a PMDG B737NGX home cockpit based on Opencockpits hardware modules and my OC4BAv4 home cockpit program. This is my controller that should all be connected all the time. 1. Saitek x52 2. Saitek Rudder 3. Opencockpits B737 Yoke 4. CFY Throttle When I use my home cockpit and fly the B737NGX, I use the Opencockpits Yoke, Saitek Rudder and CFY Throttle. When I just fly in P3Dv4 using my 4K monitor (not my home cockpit setup) I only want to use my Saitek X52 for both PMDG B737NGX and other airplanes. Now my question: How do I set up the controllers to have a working controller scenario that let my use them as described above?

Thanks, I have tried with this SimConnect variable, but can't get any values when moving the throttle lever. In FSUIPC the offset is S16 type, shouldn't it then in SImConnect be a INT32 datatype? It also says unit is Precent over 100. Are you doing any calculation of the SImConnect variable from precent to the -4096 tp 16384 value range before adding to the offset 088C?

Looking in the "FSUIPC4 Status of IPC Offsets for FSX" list you state that the offset 088C for TQ Lever position is a "Ok-SimC works okay using SimVars". Does this means that it is a variable that is defined and can be used directly with SimConnect without FSUIPC? If so, can you tell med the name of the SimConnect variable you are using to get the value to the FSUIPC offset 088C? I can't find it in the SimConnect documentation, that's the reason for my question.