I really hope there is a solution, cause Iāve really tried everything I could find on the web, but since nobody has the same problem, itās quite difficultā¦
you play it on PC?
i agree what Dubon said, find another PC to try, Windows 10 would be ideal, you donāt need to install Xbox one driver with Windows 10.
it is true that some āunexpectedā problem may happen with Windows 7ā¦
What Iāve found on the forum didnāt work for meā¦ See below:
It works until point 10 where I have to unplug and replug where Iām stuck with the same problem stated in my previous messages.
Just for a recap, Iām on Windows 7, BIOS is updated, Iāve installed the latest Xbox One controller driver for W7 x64, same for Xbox 360 controller driver and the brook update process works fine. Whenever I unplug the stick, I have to do the update process again to make it work and be recognized properly.
Like I said, I have no possibility to try on another computer this week, and canāt try on a Windows 10 computerā¦
I donāt have more money or more time to lose to find a windows 10 licence, official or cracked, to install it on a partition or with Virtual Box, just to figure out that the PCB is working correctly on windows 10.
Modding my stick and upgrading it with this PCB already took me a lot of time and money, as well as trying to solve my problem alone by searching on internet.
Thatās why I came here to ask for a concrete help since there are some brook employees/devs/engineers answering on the forums.
Iām asking for a solution on windows 7, and you keep on asking me to do stuff with windows 10.
From what Iāve read on the forums, nobody had problems with the PCB they have not been able to solve on windows 10, and only a few had problems on windows 7, but not the same as mine.
I think my problem is tied to a driver detection bug similar to people trying to plug an Xbox 360 wireless controller with a āPlug and charge usb kitā when itās not designed for it.
They have the same āHid Transferā detected in āNon specifiedā when they try to plug it without a dongle.
To me, the PCB is maybe sending a signal saying āHey Iām a wireless controller without a dongle!ā, or my computer thinks this is the case.
Maybe the fact that I first plugged it on a 3.0 USB port by mistake is the root of the problem or that could help you find why I keep getting this weird problem?
By I still donāt understand why the stick would be working just by doing the brook update process and would stop being detected correctly just by unplugging itā¦
I understand this, but I already said I have NOT the option to do it and I donāt want to deal with windows 10 on my own computer in any way.
People keeps on suggesting me to put windows 10 on my computer in a way or another, and itās becoming annoying to repeat myself.
Thank you all though for trying to help me in a way or another, but please donāt suggest me a windows 10 alternative again in a way or another to solve my problem.
I almost feel like Iām dealing with Microsoft support, and Iām sure you know what I mean.
Iāll just wait for @Brook_Engineer to post here again, hoping heās found what could be the problem by discussing with Zippy.
that would probably be best. This isnt a support forum. People here give you their opinions on possible solutions on a volontary basis. Noone here is obligated to give you support on anything, unlike microsoft when they sell you something. Just contact brook. Their support is on their website.
does the Brook have any official drivers for Linux? if not, the creator can dm thru here or somewhere else. i have experience with drivers and Linux, i contributed to many open source projects, especially the project of implementing the Rez vibrator to work on as an official game-pad.