Macro doesn't appear in FSUIPC drop-down

[Ray Proudfoot]

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?

[John Dowson]

Hi Ray,

please try the following dll (5.152c) - I've increased the max space for LVAR names from 32 to 64 characters.

I haven't tested this yet, so please let me know if there are any issues.

Cheers,

John

 

FSUIPC5.dll

[Ray Proudfoot]

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

[Ray Proudfoot]

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:

[John Dowson]

Hi Ray,

Ok, thanks - sorry I didn't have time to check this last night. I'll take a look and get back to you with a new version later today (hopefully!).

John

[John Dowson]

Hi Ray.

I just checked this and it worked for me, although I invented an LVAR name that didn't exist. This is what I got in my ini:
    11=PT,0,CM1:1,44     -{Macro longMacro: L:MyExtremelyLongLvarNameToCrashP3DWhenUsed set}-
The lvar name is truncated in the UI, but can still be selected and used. I'll need to investigate further.

John

 

[Ray Proudfoot]

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

[John Dowson]

Hi Ray,

looks like it was due to the size allocated to the drop-down entry (composing macro file name + lvar name) being too small. Please try the attached version.

Cheers,

John

 

FSUIPC5.dll

[Ray Proudfoot]

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