Custom Events not showing

[VERTSPD]

Hello all,

I placed an .evt file in my FSUIPC 7 installation folder and these events are not showing in the FSUIPC dropdown menus.
 

I’m sure I’m missing something but I couldn’t find much literature about this issue. Any help is appreciated. 

[John Dowson]

On 1/14/2022 at 6:02 PM, VERTSPD said:

I placed an .evt file in my FSUIPC 7 installation folder and these events are not showing in the FSUIPC dropdown menus.

I can't see how this can be... please double-check the file extension (as well as location), as it can also have another extension (usually .txt) that is hidden when you look at it in windows explorer. If that isn't the issue, please show me that file.

John

[Scotfleiger]

@VERTSPDmake sure your aircraft name includes a subset of the custom macro file name. If you are using a custom livery this may not be the case. For example, the "FlyByWire A32NX" matches the A32NX FBW.hvar file. Other liveries don't include A32NX.

[John Dowson]

12 hours ago, Scotfleiger said:

make sure your aircraft name includes a subset of the custom macro file name. If you are using a custom livery this may not be the case. For example, the "FlyByWire A32NX" matches the A32NX FBW.hvar file. Other liveries don't include A32NX.

The OP was referring to event files which are loaded by extension .evt and not matched to the aircraft name. Macro files are also loaded on extension .mcro and also not matched to the aircraft name.

John

[Rickard]

I think I'm having the same issue. I'm totally new with FSUIPC and don´t know if I'm doing something wrong or if there is something that's not working. 

I'm trying to bind buttons on my throttle (x-56) to custom events in the FlyByWire A32NX (MFSF). Should the custom events be found in the dropdown when selecting "for FS control"? I can't find any of the A32NX specific events in the dropdown like :

A32NX.FCU_AP_1_PUSH
A32NX.FCU_AP_2_PUSH
A32NX.FCU_AP_DISCONNECT_PUSH

 

Should they be shown there? Or am I missing something obvious? 
I can see in the console that it founds the aircraft: Aircraft="Airbus A320 Neo FlyByWire". 

[John Dowson]

Have you added the event file containing those events to your FSUIPC7 installation folder? If not, do that. The event file for those events is called flybywire-aircraft-a320-neo.evt and is located under the EventFiles folder of your FSUIPC7 installation. Move that file up one folder, to the main installation folder.

John

[Rickard]

On 1/23/2022 at 1:03 PM, John Dowson said:

Have you added the event file containing those events to your FSUIPC7 installation folder? If not, do that. The event file for those events is called flybywire-aircraft-a320-neo.evt and is located under the EventFiles folder of your FSUIPC7 installation. Move that file up one folder, to the main installation folder.

John

Yeah, that worked! Thanks! 

When I was browsing the file structure I also found the documentation folder.. might actually learn something from this. Read the manual 😅

[Hano]

Hi,

I've a similar problem.

I try to bind a joystick button to the "CALLS - ALL" button on the overhead panel of the A32NX.

I found the custom LVAR: PUSH_OVHD_CALLS_ALL in the A32NX documentation. I copied the flybywire-aircraft-a320-neo.evt file to the FSUIPC installation folder and added the following line: 30=PUSH_OVHD_CALLS_ALL

I find it in the dropdown, but when choosing nothing happend. What is going wrong?

Thx

Hano

[John Dowson]

3 minutes ago, Hano said:

I copied the flybywire-aircraft-a320-neo.evt file to the FSUIPC installation folder and added the following line: 30=PUSH_OVHD_CALLS_ALL

First, all custom events must contain a period (.). So, if it is an FBW A320 event, it should be:
    30=A32NX.PUSH_OVHD_CALLS_ALL

Check all the other events in that file, and you will see that they are all prefixed in this way.

Second, are you sure that those are actually existing FBW events? Checking the MobiFlight hubhop resource (https://hubhop.mobiflight.com/#/list), I can see the following MobiFlight events:
    PUSH_OVHD_CALLS_ALL_OFF
    PUSH_OVHD_CALLS_ALL_ON

These events are listed in the A32X-FBW2.evt file, so you need to use that if you want to use these MobiFlight presets.

Alternatively, those events just set/toggle the lvar L:PUSH_OVHD_CALLS_ALL. You can use the lvar directly in FSUIPC rather than using MobiFlight events, by either adding this lvar to an FSUIPC offset or using a macro file. Details of both techniques can be found in the User Guide and Advanced User guide.

John