Jump to content
The simFlight Network Forums

FSUIPC6 Beta release v6.0.14: Native support for up to 128 buttons


Recommended Posts

8 hours ago, John Dowson said:

If nobody wants/needs the access to the additional buttons, I can drop this update for FSUIPC6.

Don't Honeycomb and some Saitek devices have more than 32 buttons? I assume they would also be used with P3D?

And of course a proper test would be for its proper use even on 32-bit only devices, to make sure no errors have been introduced. So maybe the beta test was seen as aiming only at >32 button users, so others didn't bother. Or perhaps, like on most Forums, lack of problem reports may just be because there haven't been any.

Not sure there's any justification at present for removing the changes. If you're worried about making it the main release. Maybe keep the previous one available for folks to revert to if they think they need to, on the (hopeful?) assumption they report the problem, of course.

I'm use it here and I have no problems, but apart from testing with vJoy I don't have any devices with >32 buttons.

Pete

 

Link to comment
Share on other sites

Hi John

Just tried this dll version on P3Dv5, and got some weird results off my thrustmaster hatswitch left button. Looking at the button under the FSUIPC "Buttons and Switches" tab, when I press the button, the display shows it as Joy A button 38 with the correct sim function showing, but when I release the button, the display reverts to button no 255, no allocation! As a result I get a weird response in the sim. I stopped there to post this message. I've attached my ini file (Extra Buttons disabled) and the log file for that session. In the meantime going back to version 13.

Regards

Dave Nash

FSUIPC6.ini FSUIPC6.log

Link to comment
Share on other sites

18 hours ago, dafyddp3d said:

thrustmaster hatswitch left button. Looking at the button under the FSUIPC "Buttons and Switches" tab, when I press the button, the display shows it as Joy A button 38 with the correct sim function showing, but when I release the button, the display reverts to button no 255, no allocation!

Buttons 32-39 represent the 8 possible switches of a POV (Point of view) control, one of which is also seen as an axis. So, not true buttons, just the way FSUIPC interprets the angle of pressure. However, when released it should revert to "unpressed" (which is signalled internally as -1, so could be interpreted as 255 in 8 bits). I'll check this.

18 hours ago, dafyddp3d said:

As a result I get a weird response in the sim.

If there's no allocation, how did you get a weird response? Sorry, I don't understand that.  How would you describe this "weird response". As there's no allocation why would you get any response?

[LATER]

Yes, I can reproduce this. I'll look at the code later today -- it's evidently taking the -1 from Windows literally. Thanks for the report.

I see also that the POV is assigned to the 4 main PAN controls, with Repeat enabled. So with no release I can understand why the repeat is causing a problem for you.

Isn't this POV control recognised in the Axis assignments tab (it should be)?  If so, for panning, you'd be better off assigning there and to 2PAN VIEW".

You have two other POV's assigned as well. on Joys A and C, and many of those assignments are also with repeat enabled.

Pete

 

Link to comment
Share on other sites

"Isn't this POV control recognised in the Axis assignments tab (it should be)?  If so, for panning, you'd be better off assigning there and to 2PAN VIEW".

You have two other POV's assigned as well. on Joys A and C, and many of those assignments are also with repeat enabled."

Hi Pete, thanks for the reply

The weird response was that the POV button worked once to switch the view, but subsequent presses resulted in it panning the view, which shouldn't happen, once the view had been switched, subsequent presses of the same POV button should have no effect. Glad you were able to confirm the behaviour!

Just my personal preference, I use the POV positions for switching views and moving the eyepoint. Button 38 is allocated to "View Camera Select 2" and works perfectly under version 13.

Regards

Dave Nash

Link to comment
Share on other sites

1 minute ago, dafyddp3d said:

The weird response was that the POV button worked once to switch the view, but subsequent presses resulted in it panning the view, which shouldn't happen, once the view had been switched, subsequent presses of the same POV button should have no effect

But that's certainly not what I would expect with it being assigned to "Pan Left". Panning goes a little at a time (which is why you have it set to repeat I assume). It won't change its behaviour after being pressed once. It can't change from a View Left to a Pan Left when it is assigned to Pan Left. Please check again, with version 13 if you like.

These are your assignments to that POV:

19=RB,32,C65734,0     -{PAN_UP}-
21=RB,34,C65672,0     -{PAN_RIGHT}-
16=RB,36,C65735,0     -{PAN_DOWN}-
22=RB,38,C65671,0     -{PAN_LEFT}-

Basically you can achieve the same, only smoother, assigning the POV as an axis to Pan View. The 4 panning controls you are using are all embodied in the Pan View axis assignment.

The only problem with this in build 14 is the signalling of a button press 255 when it's released. I'll work out why and fix that.

Pete

 

 

Link to comment
Share on other sites

25 minutes ago, Pete Dowson said:

The only problem with this in build 14 is the signalling of a button press 255 when it's released. I'll work out why and fix that.

Okay, found it and fixed it.  Simple change, daft error on my part. i've sent the fix to John for him to incorporate in another Beta release (or maybe full release, soon). It will be needed in FSUIPC7 as well.

Pete

 

Link to comment
Share on other sites

Working perfectly now, thank you.

Pete - just to clarify, Button 38 on joystick A is the hat on the flight stick and this hat switch was not being used for panning, and button 38 was not set to repeat (see my earlier post). Sorry for any confusion

Dave Nash

Link to comment
Share on other sites

  • 3 weeks later...

Hello everyone!


I use FSUIPC for a long time, this month I finally transferred from FSX to Prepar3D v5 (with a brand new PC, of course) and now I registered to forum because I saw this topic where maybe I can contribute.


I downloaded version 6.0.14c today and tested it with my hardware configuration that includes four Leo Bodnar's input cards: one BBI-32 and three BBI-64s. The 64 has 64 buttons, of course, but BBI-32 is even more interesting: it has 32 physical inputs, but when combined with special switches it represents itself as HID with up to 128 buttons.


I can confirm that FSUIPC 6.0.14c can see all of these buttons as expected. But with this version (downloaded from John’s post published on 30 March) I also have to confirm Dave's report that every button returns its number only when it is pressed. When it is released, FSUIPC says that button 255 is pressed now. It is similar with the switches: when the switch is on, FSUIPC register it’s number as it suppose to. But when I turn the switch off, FSUIPC shows that “button 255 is pressed”.

Then I tried previous version (from John’s post published on 20th March, it’s written there that this version is 6.0.14b, but options window says only 6.0.14) – it works perfectly, there is no “button 255” anymore. I also checked the file in edited first post of the topic – (it declares itself as version 6.0.14 again) – everything is ok too.


Long story short: versions 6.0.14 and 6.0.14b works fine to me, but 6.0.14c again reports button 225 when any button is released.


Maybe I didn’t understand well which file is the latest, but I thought that you would like to know that 6.0.14c also has the reported problem.


I use this opportunity to thank Pete & John for their marvellous tool!

Regards,

János

Link to comment
Share on other sites

3 minutes ago, Ruler said:

Long story short: versions 6.0.14 and 6.0.14b works fine to me, but 6.0.14c again reports button 225 when any button is released.

Hmm, strange - I will check.

7 minutes ago, Ruler said:

Maybe I didn’t understand well which file is the latest, but I thought that you would like to know that 6.0.14c also has the reported problem.

6.0.14c is the latest and it should be fixed in that version, but not in 6.0.14 or 6.0.14b! I'll take a look to see what is happening (tomorrow).

9 minutes ago, Ruler said:

I use this opportunity to thank Pete & John for their marvellous tool!

Thank you!

Link to comment
Share on other sites

Sorry, I should clarify....
The letters after the release indicate its a beta release. I release 6.0.14a, then b, then c. It will be 6.0.14 when its officially released (not yet).

If you have a 6.0.14, its probably 6.0.14a. Sometimes I also forget to update the file properties, so best to check the version logged (or in the About page)
 

Link to comment
Share on other sites

In the meantime, just for case, I deleted all downloads and downloaded and checked once again, one by one file. Still the same: version c returns "button 255" on release, versions a & b works fine to me.

Maybe it is also important to say that I was wrong when I stated that every button has a problem: buttons 1-32 works as expected at all versions, the issue is only with larger numbers.

Link to comment
Share on other sites

The problem before it was fixed was with the POV buttons, 32-39.

The regular buttons are 0-31. The extra buttons now added are 132-227.

Where did you get 6.0.14c? What link?

Anyway, I'll test it here today with the very latest build.

Pete

 

Link to comment
Share on other sites

50 minutes ago, Pete Dowson said:

Anyway, I'll test it here today with the very latest build.

Okay, tested.  The latest version here does as you say, returning 255 for the release of buttons 132-227. I'll work on fixing that today.

Pete

 

Link to comment
Share on other sites

  • 4 weeks later...
Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.