Brook Universal Fighting Board Thread

[Key_Loc]

I can maybe help you with some initial probs I ran into from my own mistakes.

When you first plug the board in, windows automatically tries to install the drivers for all of the different console modes.

If you exit out or unplug the cable you can mess up the installation of the drivers (I exited out of all the installations out of my own impatience).

So what I did was open the device manager while having the stick plugged in and manually uninstalled the drivers for each console mode (I replugged in the stick in each different mode).

Then I plugged in the stick for each mode and allowed it to automatically install the drivers for each console mode. Now my stick works fine for all modes.

My problem was the PC wouldn’t even allow me to plug it in w/o crashing. 2.0 or 3.0 ports.

My bad, I edited my post to show who I was replying to.

I tried it w/o drivers with drivers, hold down p1 - p4, tried 2.0 ports 3.0 ports and still BSOD.

This is the same problem I have now, Updated the firmware and now I can’t use any USB ports without an immediate crash. Now receiving the BSOD with lusb3hub.sys error.

[rablack97]

[quote=“Key_Loc, post:881, topic:177444”]

I can maybe help you with some initial probs I ran into from my own mistakes.

When you first plug the board in, windows automatically tries to install the drivers for all of the different console modes.

If you exit out or unplug the cable you can mess up the installation of the drivers (I exited out of all the installations out of my own impatience).

So what I did was open the device manager while having the stick plugged in and manually uninstalled the drivers for each console mode (I replugged in the stick in each different mode).

Then I plugged in the stick for each mode and allowed it to automatically install the drivers for each console mode. Now my stick works fine for all modes.

This is the same problem I have now, Updated the firmware and now I can’t use any USB ports without an immediate crash. Now receiving the BSOD with lusb3hub.sys error.

Yep thats its man, i even called the mobo manuf. , no dice. That’s the exact same error i was getting. Its immediate, you cant do anything with the board plugged into the PC.

[Dubon]

3rd person reporting this… I hope Brook are working on this…

[GOGO.Zippy]

3rd person reporting this… I hope Brook are working on this…

@Dubon
We will purchase a M/B of Gigabyte GA-Z87X-D3H ATX LGA1150 to look.

[Dubon]

I can maybe help you with some initial probs I ran into from my own mistakes.

When you first plug the board in, windows automatically tries to install the drivers for all of the different console modes.

If you exit out or unplug the cable you can mess up the installation of the drivers (I exited out of all the installations out of my own impatience).

So what I did was open the device manager while having the stick plugged in and manually uninstalled the drivers for each console mode (I replugged in the stick in each different mode).

Then I plugged in the stick for each mode and allowed it to automatically install the drivers for each console mode. Now my stick works fine for all modes.

My problem was the PC wouldn’t even allow me to plug it in w/o crashing. 2.0 or 3.0 ports.

My bad, I edited my post to show who I was replying to.

I tried it w/o drivers with drivers, hold down p1 - p4, tried 2.0 ports 3.0 ports and still BSOD.

This is the same problem I have now, Updated the firmware and now I can’t use any USB ports without an immediate crash. Now receiving the BSOD with lusb3hub.sys error.

So it ran fine before you updated it?

[chaos3two]

Hey @GOGO.Zippy i’m beta testing the new PS4 3.50 firmware & i noticed after 8 mins the universal board cuts off (its fine of course when used on the current 3.15 fw), just a forewarning before 3.50 fw drops

[GOGO.Zippy]

Hey @GOGO.Zippy i’m beta testing the new PS4 3.50 firmware & i noticed after 8 mins the universal board cuts off (its fine of course when used on the current 3.15 fw), just a forewarning before 3.50 fw drops

@chaos3two
Could you download 3.50 beta fw on PC and share to our for looking ?
Thanks

[eightbitminiboss]

Hey @GOGO.Zippy i’m beta testing the new PS4 3.50 firmware & i noticed after 8 mins the universal board cuts off (its fine of course when used on the current 3.15 fw), just a forewarning before 3.50 fw drops

@chaos3two
Could you download 3.50 beta fw on PC and share to our for looking ?
Thanks

If it’s anything like the last beta, it’s locked down to one-time use codes sent out to people who signed up for beta.

[Vicko]

Not sure if its been posted here already but my start/select buttons aren’t working even though they are screwed into the terminal in the correct ports.

Has anyone here had this issue as well and would this be considered a hardware or software issue?

Not sure what stick or if you have wires going directly from the buttons to the UFB, but is your lock switch on? No reason they wouldn’t work besides that or no ground going to the buttons.

Or if you’re testing on a PS4, make sure your button assignments aren’t funky.

[Key_Loc]

I can maybe help you with some initial probs I ran into from my own mistakes.

When you first plug the board in, windows automatically tries to install the drivers for all of the different console modes.

If you exit out or unplug the cable you can mess up the installation of the drivers (I exited out of all the installations out of my own impatience).

So what I did was open the device manager while having the stick plugged in and manually uninstalled the drivers for each console mode (I replugged in the stick in each different mode).

Then I plugged in the stick for each mode and allowed it to automatically install the drivers for each console mode. Now my stick works fine for all modes.

My problem was the PC wouldn’t even allow me to plug it in w/o crashing. 2.0 or 3.0 ports.

I can maybe help you with some initial probs I ran into from my own mistakes.

When you first plug the board in, windows automatically tries to install the drivers for all of the different console modes.

If you exit out or unplug the cable you can mess up the installation of the drivers (I exited out of all the installations out of my own impatience).

So what I did was open the device manager while having the stick plugged in and manually uninstalled the drivers for each console mode (I replugged in the stick in each different mode).

Then I plugged in the stick for each mode and allowed it to automatically install the drivers for each console mode. Now my stick works fine for all modes.

My problem was the PC wouldn’t even allow me to plug it in w/o crashing. 2.0 or 3.0 ports.

My bad, I edited my post to show who I was replying to.

I tried it w/o drivers with drivers, hold down p1 - p4, tried 2.0 ports 3.0 ports and still BSOD.

This is the same problem I have now, Updated the firmware and now I can’t use any USB ports without an immediate crash. Now receiving the BSOD with lusb3hub.sys error.

So it ran fine before you updated it?

No, unfortunately. Before the firmware update it would crash if plugged into a USB 3.0 input but would do nothing/not be detected if plugged into a normal USB even with trying the forced 3P method that was posted here. Also the Board works great when tested on my PS3 before/after the update. Hope this helps clear up any confusion.

[rablack97]

I can maybe help you with some initial probs I ran into from my own mistakes.

When you first plug the board in, windows automatically tries to install the drivers for all of the different console modes.

If you exit out or unplug the cable you can mess up the installation of the drivers (I exited out of all the installations out of my own impatience).

So what I did was open the device manager while having the stick plugged in and manually uninstalled the drivers for each console mode (I replugged in the stick in each different mode).

Then I plugged in the stick for each mode and allowed it to automatically install the drivers for each console mode. Now my stick works fine for all modes.

My problem was the PC wouldn’t even allow me to plug it in w/o crashing. 2.0 or 3.0 ports.

I can maybe help you with some initial probs I ran into from my own mistakes.

When you first plug the board in, windows automatically tries to install the drivers for all of the different console modes.

If you exit out or unplug the cable you can mess up the installation of the drivers (I exited out of all the installations out of my own impatience).

So what I did was open the device manager while having the stick plugged in and manually uninstalled the drivers for each console mode (I replugged in the stick in each different mode).

Then I plugged in the stick for each mode and allowed it to automatically install the drivers for each console mode. Now my stick works fine for all modes.

My problem was the PC wouldn’t even allow me to plug it in w/o crashing. 2.0 or 3.0 ports.

My bad, I edited my post to show who I was replying to.

I tried it w/o drivers with drivers, hold down p1 - p4, tried 2.0 ports 3.0 ports and still BSOD.

This is the same problem I have now, Updated the firmware and now I can’t use any USB ports without an immediate crash. Now receiving the BSOD with lusb3hub.sys error.

So it ran fine before you updated it?

No, unfortunately. Before the firmware update it would crash if plugged into a USB 3.0 input but would do nothing/not be detected if plugged into a normal USB even with trying the forced 3P method that was posted here. Also the Board works great when tested on my PS3 before/after the update. Hope this helps clear up any confusion.

Same here, works perfect with my XBoxone, just not this particular Win7 PC. Although it cant be an OS issue, as it worked on a win8 PC and a different Win7 PC. So this has to be something with our motherboard drivers thats causing the crash.

[chaos3two]

Hey @GOGO.Zippy i’m beta testing the new PS4 3.50 firmware & i noticed after 8 mins the universal board cuts off (its fine of course when used on the current 3.15 fw), just a forewarning before 3.50 fw drops

@chaos3two
Could you download 3.50 beta fw on PC and share to our for looking ?
Thanks

Unfortunately i can’t as @eightbitminiboss said the beta is on PS4. Again it’s mainly a forewarning to let you know before people have the same problem next month when it officially releases

[GOGO.Zippy]

Hey @GOGO.Zippy i’m beta testing the new PS4 3.50 firmware & i noticed after 8 mins the universal board cuts off (its fine of course when used on the current 3.15 fw), just a forewarning before 3.50 fw drops

@chaos3two
Could you download 3.50 beta fw on PC and share to our for looking ?
Thanks

Unfortunately i can’t as @eightbitminiboss said the beta is on PS4. Again it’s mainly a forewarning to let you know before people have the same problem next month when it officially releases

@chaos3two
Thanks your reminder, I got this news in Feb and kept looking…
Unfortunately, We don’t receive a mail from SONY on beta FW.

[Biggz]

I’ve just made my first fight stick hitbox with the UFB and it was a breeze. It’s a delight working with solder-less boards and quick connects on the buttons.

I would have loved for the turbo, LEDs & stick mode to be solder-less too. Any reason why they weren’t?

Thanks for a great board!

This is what I made, boring yes but that box was £2 and it’s very sturdy I need to find something more permanent B)

http://i.imgur.com/VNPZ3kf.jpg

[theanimefan101]

Not sure if its been posted here already but my start/select buttons aren’t working even though they are screwed into the terminal in the correct ports.

Has anyone here had this issue as well and would this be considered a hardware or software issue?

Not sure what stick or if you have wires going directly from the buttons to the UFB, but is your lock switch on? No reason they wouldn’t work besides that or no ground going to the buttons.

Or if you’re testing on a PS4, make sure your button assignments aren’t funky.

its a SFxT versus stick, i had a person help me out with the wiring and they all went to the correct terminal, my home button works just fine and it can lock and unlock fine as well, its just my start and select button wont register at all even though they are connected

[teleute]

Hey @GOGO.Zippy i’m beta testing the new PS4 3.50 firmware & i noticed after 8 mins the universal board cuts off (its fine of course when used on the current 3.15 fw), just a forewarning before 3.50 fw drops

Could you still avoid the time out by forcing PS3 mode and utilizing the legacy driver for SFV, MKX, Skullgirls, etc?

[Smashbro29]

Hey @GOGO.Zippy i’m beta testing the new PS4 3.50 firmware & i noticed after 8 mins the universal board cuts off (its fine of course when used on the current 3.15 fw), just a forewarning before 3.50 fw drops

Could you still avoid the time out by forcing PS3 mode and utilizing the legacy driver for SFV, MKX, Skullgirls, etc?

Maybe but SFV’s implementation is pretty iffy.

[GOGO.Zippy]

Hey @GOGO.Zippy i’m beta testing the new PS4 3.50 firmware & i noticed after 8 mins the universal board cuts off (its fine of course when used on the current 3.15 fw), just a forewarning before 3.50 fw drops

Could you still avoid the time out by forcing PS3 mode and utilizing the legacy driver for SFV, MKX, Skullgirls, etc?

@teleute
Yes. Brook UFB can work well and no timeout issue on PS4 for SFV, when it ran on the force PS3 mode(Press 1P then plugged).

[chaos3two]

Hey @GOGO.Zippy i’m beta testing the new PS4 3.50 firmware & i noticed after 8 mins the universal board cuts off (its fine of course when used on the current 3.15 fw), just a forewarning before 3.50 fw drops

Could you still avoid the time out by forcing PS3 mode and utilizing the legacy driver for SFV, MKX, Skullgirls, etc?

Apparently there is added lag if you use legacy drivers with SF5, either way i’m sure the Brook team will have the problem sorted when the next firmware drops. They did with the 3.15 firmware update so i have complete faith in the team

[fluffhead]

I wired up a pele 5V RGB LED from paradise arcade to the Brook board. I wanted Red for player 1, green for player 2, blue for player 3, and mix all 3 for white on Xbox one. unfortunately it seemed that the voltage coming out is less than 3 volts measured my multimeter. only red lights up. Why is the voltage so low? what can I do to fix this?