Ray Proudfoot

Thanks John. That one worked and the macro is visible. Thanks very much! 👍

Thanks John. It's a pity they used such long names. Daft really. No hurry. I have plenty of other things to do.

Hi John, After installing that dll I loaded P3D and brought up FSUIPC. Selected the Profile Specific option and moved the switch. When I clicked on the dropdown box it was initially blank and then a second later P3D crashed. This is the report... Faulting application name: Prepar3D.exe, version: 4.5.12.30293, time stamp: 0x5cd47aad Faulting module name: FSUIPC5.dll, version: 5.1.5.2, time stamp: 0x5d77e0cb Exception code: 0xc0000409 Fault offset: 0x00000000000e41b4 Faulting process ID: 0x439c Faulting application start time: 0x01d568846fd5556d Faulting application path: D:\P3Dv4\Prepar3D.exe Faulting module path: D:\P3Dv4\Modules\FSUIPC5.dll Report ID: 29bc8d44-65d0-446d-a3a0-df73b6cb208f Faulting package full name: Faulting package-relative application ID:

Many thanks John. I’ll try it tomorrow and report back.

HI John, I cannot get a macro to be displayed in the button drop-down list in FSUIPC5. This relates to Xtreme Prototypes Learjet 25 where they use their own Yaw Damper code and not the default. I want to assign the macro to a GoFlight T8 switch for convenience. There are two buttons on the aircraft’s centre pedestal – Yaw Damper On and Yaw Damper Off. Pressing one also changes the other. The company uses LVar variables which should be accessible to the user for manipulation in FSUIPC. From that I searched for Yaw and there are 6 entries. I suspect that I need to use L:PedestalAutopilotYawDamperOnButtonPosition and L:PedestalAutopilotYawDamperOffButtonPosition. I can’t see anything wrong with my macro but it isn’t listed in the dropdown for Buttons & Switches under “Control sent when button pressed”. Any ideas?

Hans, it will be once the other changes in this release have been formalised.

It’s 5151d you need Hans. Scroll to the last page.

Hans, There is another command for zapping you might want to check. It might have a wider kill area. Check the documentation. Regarding P3D crashing when running Radar Contact that has been identified as a long-standing bug in FSUIPC5. Scroll to the end of this topic and download a new FSUIPC5 which will fix the problem. Rename the txt extension to dll. Hope you're still enjoying RC4 and thanks for your voice set! 👍

Hans, the Ai you wish to zap has to be right in front of you. For example an Ai approaching you head-on on a taxiway can be zapped and also one on the runway as you come into land. But an Ai more than 20 degrees from a straight-on view won't be. That is by design.

Thanks John. Does that version include Ai counts on ground and airborne?

Ah so it’s dormant until called upon by another app. Gotcha. 👍

Well done Pete. 👍 I suppose it took the huge number of Ai injected into P3D to create the conditions for the crash. Funny that it only happened for me with RC running. I suppose different things happen when it is.

Hi John, Two test departures from EGLL 27L. One in a default aircraft, the other in the PMDG737. Both fine with no crashes using 5.5.1.c. Logs available if required. Ai count was around 255 at EGLL. I flew to FL150 and 25nm from Heathrow towards Schiphol before terminating the flight. I will try a full flight to Schiphol in the next few days.

Thanks John. I shall try my EGLL 27L departure using RC4 probably tomorrow now and report back. Hope you’re feeling better. 👍

No worries. You'll see from my earlier post I ran my test with 5.1.5.0 and no crash on two separate tests.