This are the (new) Support Forums for FSUIPC and related products.

These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, and are still available (until the end of the year) for read-only here.

At the moment these new forums are quite empty – I will be updating the FAQ section and copying across the User Contributions from the old forums in the next few months.

Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.

Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE

Notifications

Clear all

Help with Black Square B36TP Condition Lever using B:Event Presets

Posts: 14

fabiojmf

Registered

Topic starter

November 16, 2025 2:49 pm

(@fabiojmf)

Joined: 2 months ago

Hello,

I am trying to configure the condition lever for the Black Square B36TP using FSUIPC7 but cannot get it to work. I am following the aircraft manual, which specifies using B:Events.

The manual states the following:

Primary Control Variables

Description Variable / Event

Condition Lever B:FUEL_1_Condition_Lever_High_Idle, B:FUEL_1_Condition_Lever_Cut_Off, L:BKSQ_ConditionLever_1

What I have tried:

Assigning buttons to standard FS controls (CONDITION_LEVER_1_…). This did not work.

Creating presets to write to L:BKSQ_ConditionLever_1. This did not work.

My current attempt is using presets to execute the B:Events, which also does not work.

Here is my current configuration.

1. myevents.txt file:

B36TP_Condition_Lever_ON#(>B:FUEL_1_Condition_Lever_High_Idle)

B36TP_Condition_Lever_OFF#(>B:FUEL_1_Condition_Lever_Cut_Off)

2. Relevant FSUIPC7.ini section:

[Buttons.Bonanza B36TP]

25=PA,11,PB36TP_Condition_Lever_ON,0

26=PA,12,PB36TP_Condition_Lever_OFF,0

(Note: I’ve observed that FSUIPC automatically changes the P for preset to C in the .ini file after loading, resulting in CPB36TP_…)

3. FSUIPC Log snippet when pressing the “ON” button:

165422 Button changed: bRef=0, Joy=0 (A), Btn=11, Pressed

165422 [Buttons.Black Square B36TP Bonanza Professional N6060E] 25=PA,11,CPB36TP_Condition_Lever_ON,0

165594 Button changed: bRef=0, Joy=0 (A), Btn=11, Released

The log shows it’s trying to send a Control (C) instead of executing the Preset (P). I must be missing a step. Any help would be appreciated.

Thank you.

1 Reply

Posts: 173

FSUIPC Support

Moderator

November 16, 2025 7:19 pm

(@fsuipc-support)

Joined: 3 months ago

What version of MSFS are you using?
B-events.variables are only useable in MSFS2024 and will now work in MSFS2020.
Look into the available ‘Input Events’. i.e. list the available Input Events, and if this one appears, then assign to that.
Input events relate to B-events, but via a different API. You can only use b-events in calculator code for MSFS2024, as these don’t function correctly in MSFS2020.

Posted by: @fabiojmf
↑
2. Relevant FSUIPC7.ini section:
[Buttons.Bonanza B36TP]
25=PA,11,PB36TP_Condition_Lever_ON,0
26=PA,12,PB36TP_Condition_Lever_OFF,0
(Note: I’ve observed that FSUIPC automatically changes the P for preset to C in the .ini file after loading, resulting in CPB36TP_…)

Are you adding this manually? And if so why? Assign to presets via the GUI. Do not attempt to add these manually unless you really have an understanding on how these ini sections work. All preset controls will have a prefix of ‘CP’ [Control, Preset). If you are manually adding these incorrectly, FSUIPC will re-write the section as to how it was interpreted, and this can have unwanted consequences.

John