Jump to content
krawhitham

controller.cfg for XBOX 360 controller (for MVP on the PC)

Recommended Posts

I just came back to this today thinking the passing of a few months would make me figure it out but still no luck. My wireless 360 controller that works EVERYwhere else completely fails at reading the button assigning that I try to program it to do. Get into the game and the same sub menu and pause problems happen.

Is there ANYthing anyone can tell me that I might be missing?

Share this post


Link to post
Share on other sites

This is frustrating. So I've been using the configs posted in here. I had it working, but I was just have a problem with my guys always diving wether it be fielding or baserunning. I was just about to attemp to fix that when all the sudden the actual controls just changed by themselves. What would normally be pitch 1, just turned into the analysis. I try changing it in game, but to no avail, and I literally have no pitch one. Also a bunch of other stuff got changed. I check it once I exit the game and it's still how I left it in the config file. Wth is going on?

Share this post


Link to post
Share on other sites

Anybody have a configuration for a PS4 controller or have an explanation of how to make a configuration from scratch for all controls? Running windows 7 with MVP 15 TC and 2017 rosters.

Share this post


Link to post
Share on other sites

Maybe some of you guys are running into total incompatibility with new and old technology.  You may simply need to purchase an inexpensive, but good controller for a PC, like the Saitek 990 or 2500.  Even used they are durable and fit well in your hands.  Very programmable.

Share this post


Link to post
Share on other sites
On 2/16/2006 at 4:34 AM, krawhitham said:

you have to install the MS drivers 1st then the new ones, just like I said in the walk through

Does anyone have any idea where we can get these MS and XBOX drivers now? Those "total-classics" links kraw is referring to are dead.

Edited by tinpanalley

Share this post


Link to post
Share on other sites

Took a long time to update this thread, but here are the definitive button mappings for the XBOX 360 Controller on Windows 10. Please be sure to copy and paste this into your controller.cfg file:

Quote

profile= Controller_(XBOX_360_For_Windows)
device= Controller_(XBOX_360_For_Windows)
player= 1
number_of_buttons= 10
number_of_povs= 1
number_of_axis= 5
VPAD_VIRTUAL_BUTTON_START= button 8
VPAD_VIRTUAL_BUTTON_SELECT= button 7
VPAD_VIRTUAL_BUTTON_CROSS= button 1
VPAD_VIRTUAL_BUTTON_CIRCLE= button 2
VPAD_VIRTUAL_BUTTON_SQUARE= button 4
VPAD_VIRTUAL_BUTTON_TRIANGLE= button 5
VPAD_VIRTUAL_BUTTON_L1= button 5
VPAD_VIRTUAL_BUTTON_R1= button 6
VPAD_VIRTUAL_BUTTON_L2= axis- 3
VPAD_VIRTUAL_BUTTON_R2= axis+ 3
VPAD_VIRTUAL_BUTTON_L3= button 9
VPAD_VIRTUAL_BUTTON_R3= button 10
VPAD_VIRTUAL_BUTTON_DPAD_UP= pov0 1
VPAD_VIRTUAL_BUTTON_DPAD_DOWN= pov180 1
VPAD_VIRTUAL_BUTTON_DPAD_LEFT= pov270 1
VPAD_VIRTUAL_BUTTON_DPAD_RIGHT= pov90 1
VPAD_VIRTUAL_BUTTON_L_STICK_RIGHT= axis- 1
VPAD_VIRTUAL_BUTTON_L_STICK_LEFT= axis+ 1
VPAD_VIRTUAL_BUTTON_L_STICK_UP= axis+ 2
VPAD_VIRTUAL_BUTTON_L_STICK_DOWN= axis- 2
VPAD_VIRTUAL_BUTTON_R_STICK_RIGHT= axis- 4
VPAD_VIRTUAL_BUTTON_R_STICK_LEFT= axis+ 4
VPAD_VIRTUAL_BUTTON_R_STICK_UP= axis+ 5
VPAD_VIRTUAL_BUTTON_R_STICK_DOWN= axis- 5
VPAD_PITCH_1= button 1
VPAD_PITCH_2= button 2
VPAD_PITCH_3= button 3
VPAD_PITCH_4= button 4
VPAD_PITCH_5= button 6
VPAD_FIELD_PICK_OFF_THROW_FIRST= button 2
VPAD_FIELD_PICK_OFF_THROW_SECOND= button 4
VPAD_FIELD_PICK_OFF_THROW_THIRD= button 3
VPAD_PITCH_OUT= button 1
VPAD_THROW_BALL= not_assigned -1
VPAD_INTENTIONAL_WALK= button 10
VPAD_INTENTIONAL_HITBATTER= button 9
VPAD_PITCH_HISTORY_OPEN= button 9
VPAD_SWING_NORMAL= button 1
VPAD_SWING_BUNT= button 10
VPAD_CHARGE_MOUND= button 4
VPAD_FIELD_THROW_FIRST= button 2
VPAD_FIELD_THROW_SECOND= button 4
VPAD_FIELD_THROW_THIRD= button 3
VPAD_FIELD_THROW_HOME= button 1
VPAD_FIELD_SWITCH= button 5
VPAD_FIELD_RELAY_THROW= axis+ 3
VPAD_FIELD_CUTOFF_THROW= axis+ 3
VPAD_FIELD_FAKE_RUNDOWN_THROW= button 6
VPAD_RUNNER_FIRST_SELECT= button 2
VPAD_RUNNER_SECOND_SELECT= button 4
VPAD_RUNNER_THIRD_SELECT= button 3
VPAD_RUNNER_RUNFIRST= pov90 1
VPAD_RUNNER_RUNSECOND= pov0 1
VPAD_RUNNER_RUNTHIRD= pov270 1
VPAD_RUNNER_RUNHOME2SCORE= pov180 1
VPAD_BASERUNNER_ADVANCEALL= button 5
VPAD_BASERUNNER_RETREATALL= button 6

Let me know if you run into issues.

Share this post


Link to post
Share on other sites

Running Kccitystar's posted config on an Xbox One For Windows in wired mode. No vibration. But everything else appears to be working as it should. Things start to go off the rails if I go wireless with it, though.

profile= Controller_(Xbox_One_For_Windows)
device= Controller_(Xbox_One_For_Windows)
player= 1
number_of_buttons= 10
number_of_povs= 1
number_of_axis= 5
VPAD_VIRTUAL_BUTTON_START= button 8
VPAD_VIRTUAL_BUTTON_SELECT= button 7
VPAD_VIRTUAL_BUTTON_CROSS= button 1
VPAD_VIRTUAL_BUTTON_CIRCLE= button 2
VPAD_VIRTUAL_BUTTON_SQUARE= button 4
VPAD_VIRTUAL_BUTTON_TRIANGLE= button 5
VPAD_VIRTUAL_BUTTON_L1= button 5
VPAD_VIRTUAL_BUTTON_R1= button 6
VPAD_VIRTUAL_BUTTON_L2= axis- 3
VPAD_VIRTUAL_BUTTON_R2= axis+ 3
VPAD_VIRTUAL_BUTTON_L3= button 9
VPAD_VIRTUAL_BUTTON_R3= button 10
VPAD_VIRTUAL_BUTTON_DPAD_UP= pov0 1
VPAD_VIRTUAL_BUTTON_DPAD_DOWN= pov180 1
VPAD_VIRTUAL_BUTTON_DPAD_LEFT= pov270 1
VPAD_VIRTUAL_BUTTON_DPAD_RIGHT= pov90 1
VPAD_VIRTUAL_BUTTON_L_STICK_RIGHT= axis- 1
VPAD_VIRTUAL_BUTTON_L_STICK_LEFT= axis+ 1
VPAD_VIRTUAL_BUTTON_L_STICK_UP= axis+ 2
VPAD_VIRTUAL_BUTTON_L_STICK_DOWN= axis- 2
VPAD_VIRTUAL_BUTTON_R_STICK_RIGHT= axis- 4
VPAD_VIRTUAL_BUTTON_R_STICK_LEFT= axis+ 4
VPAD_VIRTUAL_BUTTON_R_STICK_UP= axis+ 5
VPAD_VIRTUAL_BUTTON_R_STICK_DOWN= axis- 5
VPAD_PITCH_1= button 1
VPAD_PITCH_2= button 2
VPAD_PITCH_3= button 3
VPAD_PITCH_4= button 4
VPAD_PITCH_5= button 6
VPAD_FIELD_PICK_OFF_THROW_FIRST= button 2
VPAD_FIELD_PICK_OFF_THROW_SECOND= button 4
VPAD_FIELD_PICK_OFF_THROW_THIRD= button 3
VPAD_PITCH_OUT= button 1
VPAD_THROW_BALL= not_assigned -1
VPAD_INTENTIONAL_WALK= button 10
VPAD_INTENTIONAL_HITBATTER= button 9
VPAD_PITCH_HISTORY_OPEN= button 9
VPAD_SWING_NORMAL= button 1
VPAD_SWING_BUNT= button 10
VPAD_CHARGE_MOUND= button 4
VPAD_FIELD_THROW_FIRST= button 2
VPAD_FIELD_THROW_SECOND= button 4
VPAD_FIELD_THROW_THIRD= button 3
VPAD_FIELD_THROW_HOME= button 1
VPAD_FIELD_SWITCH= button 5
VPAD_FIELD_RELAY_THROW= axis+ 3
VPAD_FIELD_CUTOFF_THROW= axis+ 3
VPAD_FIELD_FAKE_RUNDOWN_THROW= button 6
VPAD_RUNNER_FIRST_SELECT= button 2
VPAD_RUNNER_SECOND_SELECT= button 4
VPAD_RUNNER_THIRD_SELECT= button 3
VPAD_RUNNER_RUNFIRST= pov90 1
VPAD_RUNNER_RUNSECOND= pov0 1
VPAD_RUNNER_RUNTHIRD= pov270 1
VPAD_RUNNER_RUNHOME2SCORE= pov180 1
VPAD_BASERUNNER_ADVANCEALL= button 5
VPAD_BASERUNNER_RETREATALL= button 6

 

Edited by Cap'n Butole

Share this post


Link to post
Share on other sites
16 hours ago, Cap'n Butole said:

Running Kccitystar's posted config on an Xbox One For Windows in wired mode. No vibration. But everything else appears to be working as it should. Things start to go off the rails if I go wireless with it, though.

profile= Controller_(Xbox_One_For_Windows)
device= Controller_(Xbox_One_For_Windows)
player= 1
number_of_buttons= 10
number_of_povs= 1
number_of_axis= 5
VPAD_VIRTUAL_BUTTON_START= button 8
VPAD_VIRTUAL_BUTTON_SELECT= button 7
VPAD_VIRTUAL_BUTTON_CROSS= button 1
VPAD_VIRTUAL_BUTTON_CIRCLE= button 2
VPAD_VIRTUAL_BUTTON_SQUARE= button 4
VPAD_VIRTUAL_BUTTON_TRIANGLE= button 5
VPAD_VIRTUAL_BUTTON_L1= button 5
VPAD_VIRTUAL_BUTTON_R1= button 6
VPAD_VIRTUAL_BUTTON_L2= axis- 3
VPAD_VIRTUAL_BUTTON_R2= axis+ 3
VPAD_VIRTUAL_BUTTON_L3= button 9
VPAD_VIRTUAL_BUTTON_R3= button 10
VPAD_VIRTUAL_BUTTON_DPAD_UP= pov0 1
VPAD_VIRTUAL_BUTTON_DPAD_DOWN= pov180 1
VPAD_VIRTUAL_BUTTON_DPAD_LEFT= pov270 1
VPAD_VIRTUAL_BUTTON_DPAD_RIGHT= pov90 1
VPAD_VIRTUAL_BUTTON_L_STICK_RIGHT= axis- 1
VPAD_VIRTUAL_BUTTON_L_STICK_LEFT= axis+ 1
VPAD_VIRTUAL_BUTTON_L_STICK_UP= axis+ 2
VPAD_VIRTUAL_BUTTON_L_STICK_DOWN= axis- 2
VPAD_VIRTUAL_BUTTON_R_STICK_RIGHT= axis- 4
VPAD_VIRTUAL_BUTTON_R_STICK_LEFT= axis+ 4
VPAD_VIRTUAL_BUTTON_R_STICK_UP= axis+ 5
VPAD_VIRTUAL_BUTTON_R_STICK_DOWN= axis- 5
VPAD_PITCH_1= button 1
VPAD_PITCH_2= button 2
VPAD_PITCH_3= button 3
VPAD_PITCH_4= button 4
VPAD_PITCH_5= button 6
VPAD_FIELD_PICK_OFF_THROW_FIRST= button 2
VPAD_FIELD_PICK_OFF_THROW_SECOND= button 4
VPAD_FIELD_PICK_OFF_THROW_THIRD= button 3
VPAD_PITCH_OUT= button 1
VPAD_THROW_BALL= not_assigned -1
VPAD_INTENTIONAL_WALK= button 10
VPAD_INTENTIONAL_HITBATTER= button 9
VPAD_PITCH_HISTORY_OPEN= button 9
VPAD_SWING_NORMAL= button 1
VPAD_SWING_BUNT= button 10
VPAD_CHARGE_MOUND= button 4
VPAD_FIELD_THROW_FIRST= button 2
VPAD_FIELD_THROW_SECOND= button 4
VPAD_FIELD_THROW_THIRD= button 3
VPAD_FIELD_THROW_HOME= button 1
VPAD_FIELD_SWITCH= button 5
VPAD_FIELD_RELAY_THROW= axis+ 3
VPAD_FIELD_CUTOFF_THROW= axis+ 3
VPAD_FIELD_FAKE_RUNDOWN_THROW= button 6
VPAD_RUNNER_FIRST_SELECT= button 2
VPAD_RUNNER_SECOND_SELECT= button 4
VPAD_RUNNER_THIRD_SELECT= button 3
VPAD_RUNNER_RUNFIRST= pov90 1
VPAD_RUNNER_RUNSECOND= pov0 1
VPAD_RUNNER_RUNTHIRD= pov270 1
VPAD_RUNNER_RUNHOME2SCORE= pov180 1
VPAD_BASERUNNER_ADVANCEALL= button 5
VPAD_BASERUNNER_RETREATALL= button 6

 

I don't have the wireless dongle for the XONE controller but do you know if it gets detected as a different device?

Share this post


Link to post
Share on other sites
On 2/24/2018 at 11:50 AM, Kccitystar said:

I don't have the wireless dongle for the XONE controller but do you know if it gets detected as a different device?

Yes it does recognize it as a XBONE for me.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×