Just a small Q:

Is there a limit to the number of buttons VO recognizes in joystick configuration? On my Saitek X52, counting the mode switch (recognized as 3 buttons) and two of the three POV Hatswitches (4 buttons each), there are a total of 34 buttons. Inside VO they are labeled as JOYBUTTON0 through JOYBUTTON31. There should be a JOYBUTTON32 and a JOYBUTTON33, right? Just to note, not all of these are assignable in the config menu, but are assignable from the config.ini. For instance, the POV Hatswitch in the top center of the joystick is not counted in the 34 as it is recognized in the config.ini as JOYPOV0UP, -RIGHT, -DOWN, and -LEFT, but can only be assigned manually in the config.ini and not in the config menu.
Anywho, with my digression and roundabout way of writing, the real question again is: is the reason that JOYBUTTON32 and JOYBUTTON33 don't show up in the config.ini (all other buttons have, even those I haven't assigned or couldn't assign in the menu) the fact that VO has a limit to the number of buttons it can have assigned per controller?

Hope that was all understood.

EDIT: I am going to manually add them in and assign them to some binds and see if they work, as a test.

Just to confirm: I entered them into config.ini and assigned them, and they do not work. Some buttons that I can't assign in the controller config menu I can assign in the config.ini or I can bind them, but for the two buttons that would be JOYBUTTON32 and -33, they do nothing when entered into config.ini, and when entering a bind for them in VO on the command line I get "The input 'JOYBUTTON32' doesn't exist," or The input 'JOYBUTTON33' doesn't exist."

Eh. Oh well. Not like I need them all, huh? Those two were just in a convenient place (for reference, scrolling in two different directions with the wheel on the front of the throttle, just under my fingers). Pressing the wheel as a button works (JOYBUTTON31, as it happens to be).

EDIT: Going through the error.log, I see that as VO initializes the joystick, for those last two I show this coming up:
"Ray says this usagePage is not supported."

VO currently supports a maximum of 32 buttons.

I'll take a look at it and see how easy it is to support more.

Are you using the Mac version?

The X52 has its own profiling software that is very easy to use. I recommend using that and creating a profile for Vendetta that maps the joystick buttons to the equivalent in-game keystrokes. Using the profiler, you can set up advanced macros and also double up on all commands by binding capital and lowercase keystrokes to seperate commands in-game and using the shift switch on the stick (for a total of 66 possible commands)

Yes, raybondo, the Mac version. No, Cunjo, there is not Saitek software for Mac.

A.

Have a look at either USBOverdrive or Gamepad Companion. Both are pretty good mouse/joystick profiling apps for OS X. USBOverdrive has more of a focus on mouse customization for normal computer work, Gamepad Companion is more gaming oriented.

USBOverdrive does not work with Vendetta, as far as I know. GamePad Companion I have installed, but I haven't gone through the trouble to configure it. We'll see, there's a lot of steps to it.

USBOverdrive works fine with Vendetta. The tricky part is that if you want to set up specific settings for VO, you have to point it at the actual game, not the Vendetta.app in your Applications folder, as that is the Updater. The easiest way to do this is to navigate inside the Vendetta application bundle, and create an alias to the actual game application (rather than the updater). You then put the alias in an easy location like the Desktop. Then you select the alias in USBOverdrive as the application you want to make custom settings for. Once you've saved the settings at least once, you can delete the alias. This is probably also necessary for Gamepad Companion as well, if it uses the same method to determine which application is running.

I'll edit this post with proper instructions when I'm back in front of my Mac.

If they are all different joystick devices, then you can have 32 buttons per device.

VO should support 9 axes for a single device if it has proper DirectInput drivers, I think. However, I don't have any device that has that many axes so I don't know for sure.

Is there an update on the 32-button limit, and to whether we'll be able to use more buttons in the future?

thanks,
A.

No update at this time. Adding support for more buttons is really low priority on my list.

Understood. :)

A.