Hey,
having issues with my gunfighter mk3 and SCG premium grip (R) unfortunately. The base isn't recognised as a gunfighter base (been fine for over a year). Nothing shows up in the blue window at all. I've tried reflashing with both the firmware I had and the latest firmware. I can get the bootloader to show "device connected" by reconnecting USB port whilst holding button on BB but once I've flashed it still nothing shows up in the blue window in vkbdevcfg. The grip is showing a blue light and the BB looks normal (blue light and green light). I've read about shorting the boot pins but not sure if that's necessary as the BB has a button which seems to be picking up the device? I've cancelled all razer processes and disconnected most usb devices - tried multiple USB ports (2 and 3) and holding F1 and F2 when reconnecting. Is there anything to else to try?
If I try the shorting method then are we talking about pins labelled boot on the pcb in the gunfighter base? What would the steps be? - edit - won't be trying this!!!
This is pretty frustrating as it was working perfectly fine - I just went to change profiles and it bricked...
Thanks in advance for any advice!
Cheers,
Harry
Gunfighter mk3 no longer recognized in vkbconfig
Moderator: AdminGroup
- fallout9
- Posts: 5461
- Joined: Wed Oct 03, 2018 20:37
- Has thanked: 222 times
- Been thanked: 1268 times
Re: Gunfighter mk3 no longer recognized in vkbconfig
Are you using the latest version of VKBDevCfg?
Do not, I repeat - DO NOT try to short any pins inside the base!!! The white button on the Black Box does what the pins were doing on the older model.
Does Windows recognizes the device? Any other computer available?
Do not, I repeat - DO NOT try to short any pins inside the base!!! The white button on the Black Box does what the pins were doing on the older model.
Does Windows recognizes the device? Any other computer available?
Re: Gunfighter mk3 no longer recognized in vkbdevcfg
Hi,
Yeah I've tried downloading the latest vkbdevcfg, bootloader and firmware. Same thing - it's just not showing anything in the blue window unless I hold the white button when reconnecting USB cable to bb/USB port to cable in which case it identifies VKB Boot NJoy32 platform v00.56 : HID-Compliant vendor-defined device. So then I reflash via bootloader which seems successful but it still doesn't show up in vkbdevcfg after. I won't try anything with the pcb - I wasn't sure that seemed right given the button was there so glad I asked! It does appear to show up in windows but even just connecting the blackbox (not connected to base) makes a device called VKB-sim gunfighter show up. The only other computers in the house are macs. What do you suggest? I could try removing the windows device?
Thanks for the quick reply.
Cheers,
Harry
Yeah I've tried downloading the latest vkbdevcfg, bootloader and firmware. Same thing - it's just not showing anything in the blue window unless I hold the white button when reconnecting USB cable to bb/USB port to cable in which case it identifies VKB Boot NJoy32 platform v00.56 : HID-Compliant vendor-defined device. So then I reflash via bootloader which seems successful but it still doesn't show up in vkbdevcfg after. I won't try anything with the pcb - I wasn't sure that seemed right given the button was there so glad I asked! It does appear to show up in windows but even just connecting the blackbox (not connected to base) makes a device called VKB-sim gunfighter show up. The only other computers in the house are macs. What do you suggest? I could try removing the windows device?
Thanks for the quick reply.
Cheers,
Harry
- fallout9
- Posts: 5461
- Joined: Wed Oct 03, 2018 20:37
- Has thanked: 222 times
- Been thanked: 1268 times
Re: Gunfighter mk3 no longer recognized in vkbconfig
Load again the bootloader in VKBDevCfg and instead of flashing it again, disconnect the BB from USB and plug it back.
Re: Gunfighter mk3 no longer recognized in vkbconfig
I tried - first it said I was using very old firmware, need to update (or similar), I press ok and then it said "error read CPUID" seemingly when trying to initialise - it did look like the blue boxes appeared very briefly before the old firmware msg came up. I've tried reconnecting a couple of times with the bootloader up and it gives it a new address but still not showing in the blue window - other times the bootloader window just closes and I'm back where I was to begin with. Also worth mentioning the only way I can get the bootloader to appear in vkbdevcfg is if I reconnect USB to BB with button pressed in.
Last time I tried it said access violation at address "hexaddress bla" module of vkbcfg-c.exe - read of address at 00000280 - it hasn't done that before.
edit - I added vkbdevcfg and bootloader to the list of exception programs for access violations. Hasn't helped.
Harry
Last time I tried it said access violation at address "hexaddress bla" module of vkbcfg-c.exe - read of address at 00000280 - it hasn't done that before.
edit - I added vkbdevcfg and bootloader to the list of exception programs for access violations. Hasn't helped.
Harry
Who is online
Users browsing this forum: No registered users and 36 guests