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

Hi, I got the W10 anniversary update by surprise. And the surprise swapped the GoFlight assignments of the two GF186 (NAV<->COM) and the two GF-RP48 units. Meanwhile I understand the basics about the USB mechanism. But I don’t understand how and where the unit numbers displayed in FSUIPC (Joy# 174, 175,…) are linked with the USB HW Port/Hub number and/or USB addresses? Registry? As I am using parallel to the W10 P3D also a W7 FSX system I really would like to keep the same assignment for both sims. How can I influence W10 to change back to the former unit order (174 <-> 175) assignments? Many thanks for help

Thanks for feedback and hints. And I am sorry for the miniscule script. To answer first the question: Yes, I did read the A2A forum topic. Triggered by Paul’s comment I did the following steps which solved the problem - Replacing the RealityXP(RXPGNS.ini) with the original empty file - Deleting the lately added two A2A assignments (via input configurator) - Starting FSX. Now FSUIPC and FSX accepted key commands - Shut down FSX - Entering the same 2 assignments again using the input configurator of A2A - Renaming the RealityXP ini files to get the former status - Restarting FSX and things work Difficult to say what it was but at least I could assign ruder trim to the buttons :) Again thanks for the help. Guido

Hi After installing A2A's C182 and assigning via FSUIPC some buttons and keys to GoFlight HW some days later I could not add new key codes to buttons. Even rolling back to the older FSUIPC.ini file version does not help. All buttons are inactive or blanked (attachment) independent if specific is tagged or not. Also changing to other airplanes has no effect. Compared to the FSX.cfg version without C182 the differences are the following lines: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll.rbcratezqkteollihqcneubobuntnccbtbnelcnc=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\A2A_Accusim.DLL.ihanbthaiabztoluzunklboizqttkazwciqrlbhh=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\A2A_C182\panel\C182.DLL.hekhcekicobbeznctihozwrunzwtilhoiqqazlho=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\A2A_C182\panel\C182_Illumination.DLL.aiqzikzhoanearrwbqerwwarlkanihahzitwkilw=2 C:\Program Files (x86)\GoFlight\GFDevFSX.exe.uzbqceeqtnqokbittcwwtlzrzahhanzkkkqqnhuw=1 I wonder what could block FSUIPC to accept new key/button inputs. Many thanks for the help. Rgds Guido FSUIPCBS.pdf

Hi Pete Thank you for the feedback. I will check and inform the supplier of the add-on. Rgds Guido

Hi "Every" time updating FSUIPC I run in to the issue to edit the dll.xml. As the FSUIPC update installs always at the end but before <simbase.document> <rwyadv> is not behind FSUIPC a). In this case I get a R6025 error when ending fsx. If I move FSUIPC before rwyadv the problem is solved b ). It is easy to fix when you know what to do but the reason is not clear to me. Thanks for your feedback. File: dll.xml a) </Launch.Addon> <Launch.Addon> <Name>RwyAdv</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Addon Modules\RwyAdv.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </SimBase.Document> b ) </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> <Launch.Addon> <Name>RwyAdv</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Addon Modules\RwyAdv.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </SimBase.Document>

Hi The problem is solved. I deleted FSUIPC.ini, rebuild and copy-past it. Now it works as expected. Thanks Guido