Dead or Alive 5 Last Round

Dead or Alive 5 Last Round

View Stats:
MasterZoen Nov 22, 2018 @ 2:46am
Mayflash F500 Fightstick weirdness...
Just recieved a Mayflash F500 Fightstick as an early birthday present and thought I would test it with this game. Strangely, it almost works perfectly in X-input mode, except the Start button is rcognized as RT and Back is recognized as LT... and the LT and RT buttons don't register. According to the manual and Windows 10 Controller Properties the Start button is button 8 and the Back button is button 7. Meanwhile the LT and RT buttons are working the Z-axis.

This causes a slight problem, in that the game does not detect a Back or Start button, but still detects the Joystick as an Xbox 360 controller.

Anyone know how to help?
< >
Showing 1-8 of 8 comments
Zloth Nov 22, 2018 @ 7:46am 
Have you checked the guides section?
MasterZoen Nov 22, 2018 @ 8:16am 
Originally posted by Zloth:
Have you checked the guides section?
Yeah, they talk about using 3rd party software. I'm hoping to avoid installing more stuff to run in the background, but if no one has any other solutions then I'll try those.
Djokevvi Nov 24, 2018 @ 5:45pm 
Just switch it to D-Input/PS3, it migth work. Because this game work well with direct input type controller!
MasterZoen Nov 28, 2018 @ 8:03pm 
Originally posted by sugarPARK:
Just switch it to D-Input/PS3, it migth work. Because this game work well with direct input type controller!
This didn't work. It registered Triangle, Square, Cross, and Circle, but it didn't register the R1/2 or L1/2 buttons buttons and definitely did not register the Start or Select button.

I'm going to try updating the firmware and see if that helps.
Skiptro Nov 28, 2018 @ 10:21pm 
right click on the game in steam and say "edit controller configuration"
MasterZoen Nov 29, 2018 @ 12:39am 
Originally posted by GungZA:
right click on the game in steam and say "edit controller configuration"
When I right click the game it doesn't show "Edit Controller Configuration."

Anyway, updating the firmware did have some effect. While X-input is still screwed the same way as I originally mentioned, D-input now recognizes the RT/R2, RB/R1 and LB/L1 buttons of my Fightstick. However, It's recognizing RT/R2 as Start, and RB/R1 as RT and LB/L1 as LT. Something I hadn't noticed until now is that X/Square is being recognized as A, while A/Cross is recognized as B, and B/Circle is recognized as X. Y/Triangle is being correctly recognized as Y. On a hunch I switched my Logitech F510 controller to D-input and the game had the same confusion with the X/Square, B/Circle, and A/Cross buttons but correctly identifed the RB/R1, LB/L1, Start, and Select buttons. It still didn't recognize the R or L trigger/2 buttons. Clearly, the issue is in the F500 Fightstick control board, but I can remap the fighting inputs in the Options. At least I can actually access the menu when in a fight now...
Skiptro Nov 29, 2018 @ 10:48am 
nah i had the same problem with my razer atrox and teamninja did release a steam controller config for this game so i doubt we are alone. Go into big picture mode then go to controller settings and register your mayflash as a controller under steam. Then you should have the controller setting in the context menu.
MasterZoen Dec 5, 2018 @ 8:34pm 
Originally posted by GungZA:
nah i had the same problem with my razer atrox and teamninja did release a steam controller config for this game so i doubt we are alone. Go into big picture mode then go to controller settings and register your mayflash as a controller under steam. Then you should have the controller setting in the context menu.
Sorry for the late response, but what kind of controller am I suppose to be registering it as? A Steam Controller?

Edit: Nevermind, I found a simple solution. Steam detects this controller as a Xbox 360 controller; the PS/Home button opens Big Picture mode, but the game doesn't. Go into Big Picture mode, go to the game, go to "Manage Game," go to "Controller Options," and then under "Steam Input Per-Game Setting" and set it to "Forced on." It works fine now. I wonder if this will also fix the controller issues that all the others have used Xpadder and what-not for solutions as well?
Last edited by MasterZoen; Dec 5, 2018 @ 9:10pm
< >
Showing 1-8 of 8 comments
Per page: 1530 50

Date Posted: Nov 22, 2018 @ 2:46am
Posts: 8