These are the 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, but are now no longer available.

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

Forums
WideFS
WideFS
Button 32 and above...
 
Notifications
Clear all

[Solved] Button 32 and above on ButtonScreen

 
Page 1 / 3
Posts: 7
 a320fly
Registered
Topic starter
March 11, 2026 4:15 pm
(@a320fly)
Joined: 4 weeks ago

The buttons from 0 to 31 are working perfect. But from 32 and above they don't work.

In FSUICP7.ini the entries are:

633=P64,32,C67198,2 -{FUELSYSTEM_VALVE_OPEN}-
634=P64,33,C67198,1 -{FUELSYSTEM_VALVE_OPEN}-

The log in WideFS show, that the buttons are pulled:

Preparing buttonkey block

Buttonkey block sent

The log in FSUICP show this

604328 EV_KEYDOWN received: 0x1B ()
604328 KEYDOWN: VK=27, Waiting=0, Repeat=N, lParam=0 (0x0), Shifts=0
604328 .. KeyDown received from FS but not programmed

I have no idea what's the problem.

Regards

Bernd


12 Replies
Posts: 236
 FSUIPC
Admin
March 11, 2026 4:22 pm
(@fsuipc)
Joined: 8 months ago

Button numbers 32-39 are reserved for POV buttons. Regular buttons have numbers 0-31 and then 132 upwards.

Did you add that those entries manually, or were the button numbers 32 & 33 registered in the FSUIPC button assignment UI?

Try using button numbers 132 and 133, although I am not sure if WideFS has been updated to handle more than 32 buttons.

Posted by: @a320fly
↑

The log in FSUICP show this

604328 EV_KEYDOWN received: 0x1B ()
604328 KEYDOWN: VK=27, Waiting=0, Repeat=N, lParam=0 (0x0), Shifts=0
604328 .. KeyDown received from FS but not programmed

That is an escape key press, not a button press...


This post was modified 3 weeks ago 2 times by FSUIPC
Reply
Posts: 236
 FSUIPC
Admin
March 11, 2026 4:32 pm
(@fsuipc)
Joined: 8 months ago

Looking at the WideFS documentation, it seems that there are only 32 buttons available for each virtual joystick, so I am not sure if WidFS has been updated to handle more than 32 buttons per virtual joystick. So, if button 132 doesn't work, try using joystick 65 and buttons 0 (for button 32) and button 1 (for button 33).

Cheers,

John


Reply
Posts: 7
 a320fly
Registered
Topic starter
March 11, 2026 6:07 pm
(@a320fly)
Joined: 4 weeks ago

Thank's for your information. I try as button 132/133 - it doesn't work.

A question for "jobstick 65". I need a second PC with WideFS, because I find no way to run WideFS a second time on same conected PC.

Regards 

Bernd


Reply
Posts: 236
 FSUIPC
Admin
March 11, 2026 6:17 pm
(@fsuipc)
Joined: 8 months ago

Posted by: @a320fly
↑

I try as button 132/133 - it doesn't work.

Then try joystick 65 buttons 0 and 1 (i.e. '633=P65,0...'. If you use the button assignment panel in FSUIPC, what do you see there when you trigger the virtual button?

Posted by: @a320fly
↑

A question for "jobstick 65". I need a second PC with WideFS, because I find no way to run WideFS a second time on same conected PC.

Why do you think you need a second PC with wideFS? As it says in the documentation, WideFS:

Button numbers are assigned in reference number order, from 0 (joy# 64, btn# 0) to 287 (joy# 72, btn# 31)

WideFS supports up to 9 virtual joysticks (64-72) each with 32 buttons (0-31)

 

 


This post was modified 3 weeks ago by FSUIPC
Reply
Page 1 / 3
Forum Jump: