Guido

OK. The important click is heading and this works. Thanks for support.

Yes, it is the case. But as this does not reflect the real behavior I opted for an improved method to synch with the current altitude. But failed. GFC 500 Manual: 2) Select Altitude and use the Selection Knob to change the Selected Altitude. Syncing to the current altitude: Press the ALT SEL Knob on the GMC 507

Why not use the included preset XCub Ap Alt Push which uses INDICATED ALTITUDE instead of PLANE ALTITUDE? XCub Ap Alt Push: It has the same issue therefore I tested a different option. (Issue: With each push one 100ft step down/up until reaching the actual Alt by +/- 100ft)

Outcome of today’s tests: The following two LUA and Preset implementations work: -- LUA implementation 1 ipc.execCalcCode(" (A:PLANE HEADING DEGREES GYRO, degrees) (>K:HEADING_BUG_SET) ") -- LUA implementation 2 bearing = ipc.readUW(0x2FA8) ipc.control(66042, bearing); And Presets: SYNC_HDG_BUG_TO_HSI_HDG1#(A:PLANE HEADING DEGREES GYRO, degrees) (>K:HEADING_BUG_SET) SYNC_HDG_BUG_TO_HSI_HDG2#(A:PLANE HEADING DEGREES MAGNETIC, degrees) (>K:HEADING_BUG_SET) However, I struggle with the ALT command: SYNC_AP_ALT_TO_ACT_ALT0#(A:PLANE ALTITUDE, feet) (>K:AP_ALT_VAR_SET_ENGLISH) (real alt) As the Preset XCub Ap Alt Push (altimeter alt) Both work as strange as the mouse click implementation: Step down/up by 100ft until reaching the actual Alt by +/- 100ft.

Thank you very much for help. I appreciate it very much. AP GFC 500: The AP is part of the MSFS X Cub delivery (VC). About the source I think it is Asobo. Together with the G3x (Working Title Sim) and external GTN 650 (TDS Sim) it is an easy-to-use AP offering amazing system functionality. The APs two rotary knobs push functions synch the heading bug with the current heading and AP alt preset with current alt. Fast and less dialing. I will check the proposed two ways by adding it to myevents.txt by second half of next week (after 7th). Meanwhile I study the proposed implementations.

As I could not find an event/preset for synching the HSI heading bug to current heading, for use with the GFC 500 AP, I traced the event. It looks like this: 0000174861 Event: 066042 Event Data: 000263 Event Name: HEADING_BUG_SET I wonder if something like this is possible with a FSUIPC Macro: //Read actual heading const HSIDegree = SimVar.GetSimVarValue('HSI BEARING', 'degree'); //Set heading bug to actual heading SimVar.SetSimVarValue('HEADING_BUG_SET', ' HSIDegree ', '0'); Or how this could be implemented for us in FSUIPC. Appreciate advice how to or if the event already exists the link to the event. Rgds, Guido

OK, I identified the problem. When I assigned presets the aircraft specific was not set and when testing it was active. Now things are OK. 🙂 Thanks for help and sorry for the issue. Rgds Guido

OK, no problem. Thanks, enjoy lunch and weekend.

Hi John, Again, thank you very much for support. Meanwhile I followed your instructions and this is the outcome: 1. Activate FSUIPC logging for Events: When activating Log Events (MSFS C172) only Event: Control 67198 Fuel_System_Valve_Open was logged. I could not find other events in the log file. Is there a filter to hide continues active events? 2. Presets: Next I assigned the presets for AS430/530 to Menu, Clear, Direct to and enter buttons. No action. Please find attached the log file for the presets and FS control buttons. 3. List available lvars: I could only find AS530_CDI_Source as a relevant variable for my panel. Range and brightness, I have not implemented. VLOC/GPS toggles at addressed VOR as it works through FSUIPC FS controls. And now? Any other tracing possibility to track the events? Note: Pity, that no commands are included in the panel.cfg file of the GNS. Rgds Guido FSUIPC7FSContrlGPS.2.log FSUIPC7_PresetsAS530.6.log

Hi John, Thank you very much for introduction and advice. I will check and come back. Nice weekend. Rgds, Guido

Hello, As in P3D I wanted to control the MSFS Garmin GNS 530 / GNS 430 (@ MSFS from Working Title) via FSUIPC button and switches assignments with my panel. Therefore, I assigned GPS direct to, enter, clear, menu and more from the FSUIPC event list to the panel buttons. Unfortunately, only GPWS switch toggle (GPS/LOC) has an effect to the sim. Are the GPS control events not supported by MSFS or are other commands/events required? Thanks for feedback

Yes I did. Some months ago when switching off cockpit tips and user tips I switched message text also off. I did not know that message text is also used by FSUIPC. Sorry. Thank you very much for the help. 😊 Rgds Guido

Hi, today I wanted to record a macro and discovered that after a "VC button" click no window is pupping up to assign a functional name to the macro. Next I tested macro recording with the default F-35 unfortunately with the same result. I discovered this after installing P3Dv4.5.13.32097 and FSUIPC 5.152. With P3Dv4.4 and (I think) FSUIPC 5.132 I had no problems. Going back to client v4.4 does not help. I checked with full screen, window mode and recorded log data but I cannot find a hint what to do next to fix the issue. Attached the FSUIPC install and macro recording logs. Thanks for support to fix my problem. Rgds Guido System info: W10x64, P3Dv.v4.5.13.32097 , FSUIPC 5.152 FSUIPC5 Install.log FSUIPC5.4.log

Hi Thomas, Thanks for the help. As proposed I deleted the old assignment and renamed the new created IDs with the former joy letters. This did the job. Rgds Guido

Hi, When transiting from FSUIPC version 4959 to 4969 I got a missing joystick issue. With this behavior my assignments are “gone” and second some joysticks are now twice listed with new IDs. I don’t understand what is creating the <<MISSING JOYSTICK>> message (except for F=737YOKE) and why the detection after. Appreciate any help to fix the issue. Guido Attached: File compare and log file FSUIPC4.log missingjoystick.pdf