Gladiator Pro Button Re-Mapping
Moderator: AdminGroup
Re: Gladiator Pro Button Re-Mapping
Aren't the button numbers hard coded to the physical button? So pinky on the Gladiator handle is always #47, or am I misunderstanding how the VJoy32 works with button assignments?
Re: Gladiator Pro Button Re-Mapping
Yes they are. Physical layer tab shows line numbers hard linked to buttons. If you have standalone controller with extension panels you can change line numbers replacing connectors. By default physical numbers correspond to logical ones. When you run VKBJoytester or Windows tool you see just logical numbers. You can remap physical line numbers to desired logical ones using Logical layer tab or Button Mapping Wizarg.
Руководство пользователя по контроллерам VKB (VKB controllers User Guide) Ru&En
https://disk.yandex.ru/d/LlqiYtIrIetBOQ
https://disk.yandex.ru/d/LlqiYtIrIetBOQ
Re: Gladiator Pro Button Re-Mapping
Try another PC. Yesterday captured screenshots with Glad at home PC. Today tried to help - using Mamba controller. COULD NOT set keyboard! Came home with the same settings and the same controller everything OK ![Shocked :shock:](./images/smilies/icon_eek.gif)
![Shocked :shock:](./images/smilies/icon_eek.gif)
Руководство пользователя по контроллерам VKB (VKB controllers User Guide) Ru&En
https://disk.yandex.ru/d/LlqiYtIrIetBOQ
https://disk.yandex.ru/d/LlqiYtIrIetBOQ
Re: Gladiator Pro Button Re-Mapping
Thanks heaps for the help guys. I'm happy to help share the knowledge in the English section as you sell more devices into the Western market you'll probably get a lot more questions.
I have a couple of different PCs here that I'll try today when I get a chance. So you could replicate the problem Victorus?
I have a couple of different PCs here that I'll try today when I get a chance. So you could replicate the problem Victorus?
Re: Gladiator Pro Button Re-Mapping
Ok, I tried setting the buttons to 128, but this didn't help at all. I also tried doing the configuration on a MacBook Pro computer and got the exact same results as my desktop PC.
It's worth noting that both PCs are running Windows 10. Desktop PC is running the 1607 Anniversary update, and the Macbook Pro is running on 1511. Unfortunately I don't have access to a Windows 7 or Windows 8/8.1 machine to test.
It's worth noting that both PCs are running Windows 10. Desktop PC is running the 1607 Anniversary update, and the Macbook Pro is running on 1511. Unfortunately I don't have access to a Windows 7 or Windows 8/8.1 machine to test.
Re: Gladiator Pro Button Re-Mapping
Please try newer version of VKBDevCfg.exe. https://drive.google.com/file/d/0B1WRiD1czmcHRmhBRDhIVzVwTGc/view?usp=sharing
Руководство пользователя по контроллерам VKB (VKB controllers User Guide) Ru&En
https://disk.yandex.ru/d/LlqiYtIrIetBOQ
https://disk.yandex.ru/d/LlqiYtIrIetBOQ
Re: Gladiator Pro Button Re-Mapping
Sorry Victorus, same results on 0.77.66.
Just to make sure there is no misunderstanding, I followed the following procedure after running 0.77.66:
Went to Global, and set Keyboard to Classic
Set on joystick to write to joystick memory
Go to Profile, Physical, Button 47
Change dropdown to Button, click on Key field and choose Keyboard (no HID Keyboard showing, just Keyboard).
Select Key_********* and then press the left Shift button
This then shows B 47 2 in the dialogue box which I then close.
Click Set, then go into Test tab and press pinky button. Joystick log still shows "Button 2" when pinky is pressed.
Just to make sure there is no misunderstanding, I followed the following procedure after running 0.77.66:
Went to Global, and set Keyboard to Classic
Set on joystick to write to joystick memory
Go to Profile, Physical, Button 47
Change dropdown to Button, click on Key field and choose Keyboard (no HID Keyboard showing, just Keyboard).
Select Key_********* and then press the left Shift button
This then shows B 47 2 in the dialogue box which I then close.
Click Set, then go into Test tab and press pinky button. Joystick log still shows "Button 2" when pinky is pressed.
Re: Gladiator Pro Button Re-Mapping
The main issue - no virtual keyboard((( Thinking... ![Rolling Eyes :roll:](./images/smilies/icon_rolleyes.gif)
![Rolling Eyes :roll:](./images/smilies/icon_rolleyes.gif)
Руководство пользователя по контроллерам VKB (VKB controllers User Guide) Ru&En
https://disk.yandex.ru/d/LlqiYtIrIetBOQ
https://disk.yandex.ru/d/LlqiYtIrIetBOQ
Re: Gladiator Pro Button Re-Mapping
I think I've found. Windows issue.
Download and unpack usbdeview tool. https://yadi.sk/d/uAaW4_hSvmvW2
Run. Sort list of ever connected usb devices by VendorID. Select all devices with 231d (VKB ID). Execute File - Uninstall Selected Devices. Reconnect Joy. I suggest you will see two devices.
I connected controller to my PC at work - no virtual keyboard. At home everything was OK. After mentionув above procedure was completed I saw my lovely kbd)))
Try!
Download and unpack usbdeview tool. https://yadi.sk/d/uAaW4_hSvmvW2
Run. Sort list of ever connected usb devices by VendorID. Select all devices with 231d (VKB ID). Execute File - Uninstall Selected Devices. Reconnect Joy. I suggest you will see two devices.
I connected controller to my PC at work - no virtual keyboard. At home everything was OK. After mentionув above procedure was completed I saw my lovely kbd)))
Try!
Руководство пользователя по контроллерам VKB (VKB controllers User Guide) Ru&En
https://disk.yandex.ru/d/LlqiYtIrIetBOQ
https://disk.yandex.ru/d/LlqiYtIrIetBOQ
Re: Gladiator Pro Button Re-Mapping
Victorus, when I went into USBDeview, I could only see one instance of 231d, coloured green meaning it was actively connected. I selected it, and uninstalled the device. I waited for it to refresh to make sure it was gone. Once confirmed, I unplugged the USB, and plugged back in again. Windows came up with the "Found new hardware" window and started installing the drivers again for the VKB joystick. Once finished, the 231d was back again and coloured green like before. However there was never more than one entry for VKB and vendor ID 231d, so didn't get the two devices showing like you did on your work computer unfortunately.
Here is the line item if you can see if anything look out of place:
Here is the line item if you can see if anything look out of place:
Re: Gladiator Pro Button Re-Mapping
Yes! USBDeview and OS sees only one device. I suggest you will find virtual keyboard in VKBDevCfg list! This means you can map Glad buttons to keys, including "pure" Shift!
USBDeview refreshes Windows usb devices list only. Sometimes this is the only way to clean unexpected errors.
USBDeview refreshes Windows usb devices list only. Sometimes this is the only way to clean unexpected errors.
Руководство пользователя по контроллерам VKB (VKB controllers User Guide) Ru&En
https://disk.yandex.ru/d/LlqiYtIrIetBOQ
https://disk.yandex.ru/d/LlqiYtIrIetBOQ
Re: Gladiator Pro Button Re-Mapping
Let's try to enable mouse functions. Test of other virtual devices connection.
Unpack zconfig.ini to the same folder with VKBDevCfg.exe. Run VKBDevCfg.exe. Set Mouse to Relative and Active to Alays On. Set. Will you see at least HID compilant mouse in the list of HID Composite device components?
Unpack zconfig.ini to the same folder with VKBDevCfg.exe. Run VKBDevCfg.exe. Set Mouse to Relative and Active to Alays On. Set. Will you see at least HID compilant mouse in the list of HID Composite device components?
Руководство пользователя по контроллерам VKB (VKB controllers User Guide) Ru&En
https://disk.yandex.ru/d/LlqiYtIrIetBOQ
https://disk.yandex.ru/d/LlqiYtIrIetBOQ
Re: Gladiator Pro Button Re-Mapping
Copied the new Zconfig.ini. When launching VKBDeviceConfig, it definitely looks more like your screenshots. However, when I choose to set the mouse to relative mode, and always on, when I hit set I get these dialogue boxes:
If choose to Select All, and set, it says no new data, and if I get the profile from the joystick again, it sets mouse back to off.
If choose to Select All, and set, it says no new data, and if I get the profile from the joystick again, it sets mouse back to off.
Who is online
Users browsing this forum: Google [Bot] and 49 guests