Controller issues

[RedSoxFox7]

I started off using a Logitech Dual Action gamepad. As pretty much everyone knows, the thing is a POS. The left analog stick is always getting out of calibration, and mine never even gets full calibrated anymore when it gets unplugged/plugged back in.

So, in an attempt to get a decent controller I just went down to CompUSA. I decided I'd stay away from Logitech based on past experience, and went w/ a Seitek P2600 Rumble.

I've already had a laundry list of problems with it, and I haven't even made it through a full game yet.

No matter what I assign it to, I cannot get Pitch 5 to work.

I can't intentionally walk or hit batters, no matter what I change the control to be.

Quick pickoffs don't work at all.

The L3 and R3 "buttons" don't do a damn thing.

In short, I can't change many of the other options to make them work the way they're supposed it, AKA the way the Logitech worked out of the box and the way the PS2 version works.

Oh yeah, and the rumble doesn't work at all either. :roll:

I really want to return it for a Logitech Rumblepad 2, but I don't know if Logitech has bothered to fix the issues that were present with the Dual Action, or at least the first run of the Dual Action.

Is there any way to configure the P2600 properly, or are a lot of the controls just "hardwired" to be wrong? Did Logictech address the issues with the first run Dual Action in either later DAs or with the Rumblepad 2?

[PolishJoe]

First, sorry to hear about all the issues you've been having man. As you referenced, you're not alone in the Logitech issue. Though the Logitech Dual Gamepad 2 seems to have addressed all of the issues associated with the first version of the controller, the fact that Logitech never acknowledged nor offered some sort of trade-in program really pushed me away from them. I guess their desire for covering short-term costs outweighed their long-term concern for the consumer base. :roll:

Also, to add to my beef with Logitech, I myself am not exactly a fan of CompUSA. I can kind of relate to this. :evil:

That being said, I'd try two things before you even given any consideration to getting the Logitech 2 Gamepad, (and thereby put more mula in CompUSA's pocket in "restocking fees").

First, do you have a PlayStation 2 or Xbox? If you can't get your Saitek to function, I'd recommend just purchasing a PS2/Xbox to USB adapter for your computer. Not only would this option be cheaper than getting another gamepad, but they also offer a much more durable option.

But, before getting ahead of myself or if you just don't have a console controller, I'd make sure everything is okay with your controller first.

As it stands now, you might want to go into Add/Remove Hardware and search for any existing Saitek software. Unistall it if there's anything.

Then, download the latest drivers from here. It's roughly 50MB.

Next, remove your controller - physically - from your computer. Run the installation application you just downloaded. Once the installation has completed, plug your controller back in.

After that, go into your Control Panel > Printers & Other Hardware > Game Controllers and ensure that your controller is present. You'd also want to run the calibration wizard.

Finally, run MVP. Start an Exhibition and run a game. Though your controller probably won't be good-to-go at this point, you shouldn't have any "new" issues.

After you've run the game, exit it and go into My DocumentsMVP Baseball 2005 and locate the file called "Controller.cfg". Right-click it and choose to Sent To > Compressed (Zipped) Document.

Finally, upload the zipped file to this post.

Let me know if you have any questions!

[RedSoxFox7]

Thanks for the advice. I did a little searching, and it seems the P2600 needs some additional editing of the controller.cfg file to work even close to properly, but it still doesn't work the way a PS2 or Logitech controller would.

I just looked over the receipt, wary of potential restocking fees, and the receipt doesn't say anything about a fee. That's not to say they won't try to charge me one.

I thought about getting one of those PS2 to PC converters, but I'm not sure there's anywhere around here that I can get one. I know I could order from lik-sang, but I'd rather find a local brick & mortar place to get it.

I tried the controller just using whatever Windows got from Plug-n-play, and it didn't work at all in MotoGP2, and the controls were all screwed up in NHL06 (another EA title).

The L3 and R3 buttons don't even show up in the Game Controllers config panel in Windows, so I'm thinking they'll never actually do anything. I understand your beef w/ CompUSA, and I've got a beef with Logitech, but if I can just swap this and get the Rumblepad 2 and have it work easily, I'm just going to go that route.

I just wanted to make sure the Rumblepad 2 didn't suffer the same problem as the original Dual Action.

Would you happen to know if the current Dual Action controller has the same problems are the older one? It appears to be the same controller as far as Logitech is concerned, but they've had two versions. The one I have has 10 total buttons, excluding the D-pad and analog sticks. The one I saw at CompUSA today had 11 buttons, there was an additional "mode" button on it. I'm wondering if maybe they re-released the controller after fixing the calibration issues.

[PolishJoe]

Hey man,

To the best of my knowledge, the Logitech Rumblepad 2 fixed everything. However, I never purchased it just because I'm a ***** :wink: . Plus, I purchased one of the those PS2 to USB converters and love it! :yeah: But, all in all, a lot of players on these boards use the Logitech 2 with no major issues.

As for the PS2 to USB Adapter, I can understand what you're saying about wanting to go somewhere and get it. If you're near a RadioShack, they carry them for less than $15. Many here got their adapter either from there or eBay with a lot of luck.

Regardless of your decision, I did notice that the controller is $23 here as compared to $30 from CompUSA.

And lastly, no matter what controller you purchase, you will have to manually open your config file, (I think), and change some values. However, it's no where near as intimidating as it may sound.

Oh, and just for curiosity's sake, if you could, would you upload your config file, (My Documents > MVP Baseball 2005 > Controller.config). I'm just curious to see what MVP calls your controller. If you're interested, I'd be willing to modify the config file and give it back - no later than today. But please don't feel obligated! Do what works for you!

- Good Luck!

[RedSoxFox7]

Here's the CFG section for the P2600, this is after I messed around in-game a bit trying to get it to work properly:

profile= Saitek_P2600_Rumble_Force_Pad

device= Saitek_P2600_Rumble_Force_Pad

player= 1

number_of_buttons= 12

number_of_povs= 1

number_of_axis= 4

VPAD_VIRTUAL_BUTTON_START= button 11

VPAD_VIRTUAL_BUTTON_SELECT= not_assigned -1

VPAD_VIRTUAL_BUTTON_CROSS= button 3

VPAD_VIRTUAL_BUTTON_CIRCLE= button 4

VPAD_VIRTUAL_BUTTON_SQUARE= button 1

VPAD_VIRTUAL_BUTTON_TRIANGLE= button 2

VPAD_VIRTUAL_BUTTON_L1= button 7

VPAD_VIRTUAL_BUTTON_R1= button 8

VPAD_VIRTUAL_BUTTON_L2= button 5

VPAD_VIRTUAL_BUTTON_R2= button 6

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- 3

VPAD_VIRTUAL_BUTTON_R_STICK_LEFT= axis+ 3

VPAD_VIRTUAL_BUTTON_R_STICK_UP= axis+ 4

VPAD_VIRTUAL_BUTTON_R_STICK_DOWN= axis- 4

VPAD_PITCH_1= button 2

VPAD_PITCH_2= button 3

VPAD_PITCH_3= button 1

VPAD_PITCH_4= button 4

VPAD_PITCH_5= button 6

VPAD_FIELD_PICK_OFF_THROW_FIRST= button 3

VPAD_FIELD_PICK_OFF_THROW_SECOND= button 4

VPAD_FIELD_PICK_OFF_THROW_THIRD= button 1

VPAD_PITCH_OUT= button 2

VPAD_THROW_BALL= not_assigned -1

VPAD_INTENTIONAL_WALK= button 10

VPAD_INTENTIONAL_HITBATTER= button 9

VPAD_PITCH_HISTORY_OPEN= button 7

VPAD_SWING_NORMAL= button 2

VPAD_SWING_BUNT= button 9

VPAD_CHARGE_MOUND= button 4

VPAD_FIELD_THROW_FIRST= button 3

VPAD_FIELD_THROW_SECOND= button 4

VPAD_FIELD_THROW_THIRD= button 1

VPAD_FIELD_THROW_HOME= button 2

VPAD_FIELD_SWITCH= button 6

VPAD_FIELD_RELAY_THROW= button 5

VPAD_FIELD_CUTOFF_THROW= button 8

VPAD_FIELD_FAKE_RUNDOWN_THROW= button 7

VPAD_RUNNER_FIRST_SELECT= button 3

VPAD_RUNNER_SECOND_SELECT= button 4

VPAD_RUNNER_THIRD_SELECT= button 1

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

[RedSoxFox7]

With the original Dual Action I was able to just plug it in and MVP had all the right settings. Are you saying I'll have to change some settings w/ the Rumblepad 2?

[PolishJoe]

Two questions real quick with the way the configuration is now:

1) When pressing down the left analog stick, (assuming you have it in analog mode), does it bring up the "Pause" screen within the game? Or, do you have to hit one of the two "extra" buttons? If that's the case, which one - the black or the gray one?

2) Using PS2 controller terms, what buttons is able to throw to the cutoff man, R1 or R2?

And to address what I was saying about the Logitech Gamepad, I should have spoken clearer. All you have to do is go into the controller.config file one time and change the right-analog axis values. Where it says 3, change to 4 and vice-versa. That's all - nothing major though. Sorry about that.

[pfalvey]

I am using a Saitek P880 Dual Analog with MVP and I've never had to edit a config file or anything. Works fine with other games, too.

[RedSoxFox7]

Two questions real quick with the way the configuration is now:

1) When pressing down the left analog stick, (assuming you have it in analog mode), does it bring up the "Pause" screen within the game? Or, do you have to hit one of the two "extra" buttons? If that's the case, which one - the black or the gray one?

2) Using PS2 controller terms, what buttons is able to throw to the cutoff man, R1 or R2?

And to address what I was saying about the Logitech Gamepad, I should have spoken clearer. All you have to do is go into the controller.config file one time and change the right-analog axis values. Where it says 3, change to 4 and vice-versa. That's all - nothing major though. Sorry about that.

Pressing down on the left stick, as in pushing it as a button? Or as in I want to throw a ball in the dirt?

If I push it like a button, like L3 on a PS2, nothing happens. I have to hit the "FPS" button to pull up the pause screen.

The button action of the two analog sticks doesn't appear to actually do anything. If I go into the Game Controller control panel and hit Properties on the P2600, nothing happens when I push the analog "buttons." They click and everything like a PS2 controller or Logitech controller, but they don't actually do anything. It seems as though they're just there for looks.

The cutoff button *should* be R2, but I don't remember being able to make any cutoff throws with it.

[PolishJoe]

pfalvey, for your P880, can you push in on your joysticks and use them as buttons?

Also, RedSoxFox7, I should have said L3 - sorry.

So, after looking over the Saitek P2600 manual, it appears that the joysticks have "buttons", right? Well, I was looking over the P880 manual, and it had the same layout - buttons 11 & 12.

Then, out of curiousity, I looked over the 990's manual. Same thing... almost. On the first page of the 990, instead of saying "Joysticks" like in the 880 and 2600, it said "Joysticks with built in buttons." Sounds like neither of you have the built-in buttons like you had said RSF7.

So, assuming this is correct, (I'd like to see if pfalvey can verify that), then you can use your controller like a PS2 controller with one exception:

Instead of pushing in the joysticks, L3/ R3, you can use the two extra buttons on the far right of the gamepad as the L3/ R3 equivalents. If that's the case, just let me know and I'll try to configure a file for you.

[pfalvey]

Yes, if I press down on the analog sticks in MVP it brings up pitch history for L3 and I'm not sure about R3, but yes they are buttons.

[PolishJoe]

Yes, if I press down on the analog sticks in MVP it brings up pitch history for L3 and I'm not sure about R3, but yes they are buttons.

Thanks pfalvey!

RedSoxFox7, when you inserted your controller, did you use the built-in drivers included in Windows or did you install software from Saitek? If not, did your controller come with a disc?

Thanks again pfalvey! :!:

[RedSoxFox7]

Thanks pfalvey!

RedSoxFox7, when you inserted your controller, did you use the built-in drivers included in Windows or did you install software from Saitek? If not, did your controller come with a disc?

Thanks again pfalvey! :!:

I just used the Windows drivers.

It's just as well it didn't work out of the box. I just returned it, cash refund, no restocking fee. I then went down to RadioShack on the advice of some other people and got this little gem for less than $10 with sales tax.

http://www.radioshack.com/product/index.js...rentPage=search

[RedSoxFox7]

OK, almost there!

I'll do some searching after this post to see if I can get it figured out myself, but here goes.

The L1/2 and R1/2 buttons are flipped with the driver I'm using. Instead of L1=5, R1=6, L2=7, R2=8 like with the Logitech, it is L1=7, R1=8, L2=5, R2=6. So, because of that I need to press L2 to do a quick pickoff, and I need to configure R2 to be my 5th pitch.

Now for the regular thumb buttons 1-4, they're in reverse order. 1=4, 2=3, 3=1, 4=1.

And like you mentioned earlier, the right stick needs to be changed up.

It doesn't appear I can change what the buttons are considered by the driver itself. But that's no big deal.

There are 3 things I need to do:

1. Fix the right stick axis.

2. Flip the L & R buttons so L1 is a quick pickoff, R1 is pitch 5 and so on.

3. This isn't totally necessary, but it'd be nice if I could make button 3 the one that skips through menus and cut scenes instead of 2.

I'm off to search and try messing with this myself, but here's the CFG file if anyone is interested in fixing it for me.

profile= USB_Dual_Vibration_Joystick

device= USB_Dual_Vibration_Joystick

player= 1

number_of_buttons= 12

number_of_povs= 1

number_of_axis= 4

VPAD_VIRTUAL_BUTTON_START= button 10

VPAD_VIRTUAL_BUTTON_SELECT= button 9

VPAD_VIRTUAL_BUTTON_CROSS= button 2

VPAD_VIRTUAL_BUTTON_CIRCLE= button 3

VPAD_VIRTUAL_BUTTON_SQUARE= button 1

VPAD_VIRTUAL_BUTTON_TRIANGLE= button 4

VPAD_VIRTUAL_BUTTON_L1= button 5

VPAD_VIRTUAL_BUTTON_R1= button 6

VPAD_VIRTUAL_BUTTON_L2= button 7

VPAD_VIRTUAL_BUTTON_R2= button 8

VPAD_VIRTUAL_BUTTON_L3= button 11

VPAD_VIRTUAL_BUTTON_R3= button 12

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- 3

VPAD_VIRTUAL_BUTTON_R_STICK_LEFT= axis+ 3

VPAD_VIRTUAL_BUTTON_R_STICK_UP= axis+ 4

VPAD_VIRTUAL_BUTTON_R_STICK_DOWN= axis- 4

VPAD_PITCH_1= button 3

VPAD_PITCH_2= button 2

VPAD_PITCH_3= button 4

VPAD_PITCH_4= button 1

VPAD_PITCH_5= button 6

VPAD_FIELD_PICK_OFF_THROW_FIRST= button 2

VPAD_FIELD_PICK_OFF_THROW_SECOND= button 1

VPAD_FIELD_PICK_OFF_THROW_THIRD= button 4

VPAD_PITCH_OUT= button 3

VPAD_THROW_BALL= not_assigned -1

VPAD_INTENTIONAL_WALK= button 12

VPAD_INTENTIONAL_HITBATTER= button 11

VPAD_PITCH_HISTORY_OPEN= button 11

VPAD_SWING_NORMAL= button 3

VPAD_SWING_BUNT= button 12

VPAD_CHARGE_MOUND= button 1

VPAD_FIELD_THROW_FIRST= button 2

VPAD_FIELD_THROW_SECOND= button 1

VPAD_FIELD_THROW_THIRD= button 4

VPAD_FIELD_THROW_HOME= button 3

VPAD_FIELD_SWITCH= button 7

VPAD_FIELD_RELAY_THROW= button 6

VPAD_FIELD_CUTOFF_THROW= button 6

VPAD_FIELD_FAKE_RUNDOWN_THROW= button 8

VPAD_RUNNER_FIRST_SELECT= button 2

VPAD_RUNNER_SECOND_SELECT= button 1

VPAD_RUNNER_THIRD_SELECT= button 4

VPAD_RUNNER_RUNFIRST= pov90 1

VPAD_RUNNER_RUNSECOND= pov0 1

VPAD_RUNNER_RUNTHIRD= pov270 1

VPAD_RUNNER_RUNHOME2SCORE= pov180 1

VPAD_BASERUNNER_ADVANCEALL= button 7

VPAD_BASERUNNER_RETREATALL= button 8

[RedSoxFox7]

Got it working on my own, and for those that may search and run into the same issues here's the changes I made:

profile= USB_Dual_Vibration_Joystick

device= USB_Dual_Vibration_Joystick

player= 1

number_of_buttons= 12

number_of_povs= 1

number_of_axis= 4

VPAD_VIRTUAL_BUTTON_START= button 10

VPAD_VIRTUAL_BUTTON_SELECT= button 9

VPAD_VIRTUAL_BUTTON_CROSS= button 3

VPAD_VIRTUAL_BUTTON_CIRCLE= button 2

VPAD_VIRTUAL_BUTTON_SQUARE= button 4

VPAD_VIRTUAL_BUTTON_TRIANGLE= button 1

VPAD_VIRTUAL_BUTTON_L1= button 7

VPAD_VIRTUAL_BUTTON_R1= button 8

VPAD_VIRTUAL_BUTTON_L2= button 5

VPAD_VIRTUAL_BUTTON_R2= button 6

VPAD_VIRTUAL_BUTTON_L3= button 11

VPAD_VIRTUAL_BUTTON_R3= button 12

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+ 3

VPAD_VIRTUAL_BUTTON_R_STICK_DOWN= axis- 3

VPAD_PITCH_1= button 3

VPAD_PITCH_2= button 2

VPAD_PITCH_3= button 4

VPAD_PITCH_4= button 1

VPAD_PITCH_5= button 8

VPAD_FIELD_PICK_OFF_THROW_FIRST= button 2

VPAD_FIELD_PICK_OFF_THROW_SECOND= button 1

VPAD_FIELD_PICK_OFF_THROW_THIRD= button 4

VPAD_PITCH_OUT= button 3

VPAD_THROW_BALL= not_assigned -1

VPAD_INTENTIONAL_WALK= button 12

VPAD_INTENTIONAL_HITBATTER= button 11

VPAD_PITCH_HISTORY_OPEN= button 11

VPAD_SWING_NORMAL= button 3

VPAD_SWING_BUNT= button 12

VPAD_CHARGE_MOUND= button 1

VPAD_FIELD_THROW_FIRST= button 2

VPAD_FIELD_THROW_SECOND= button 1

VPAD_FIELD_THROW_THIRD= button 4

VPAD_FIELD_THROW_HOME= button 3

VPAD_FIELD_SWITCH= button 7

VPAD_FIELD_RELAY_THROW= button 6

VPAD_FIELD_CUTOFF_THROW= button 6

VPAD_FIELD_FAKE_RUNDOWN_THROW= button 8

VPAD_RUNNER_FIRST_SELECT= button 2

VPAD_RUNNER_SECOND_SELECT= button 1

VPAD_RUNNER_THIRD_SELECT= button 4

VPAD_RUNNER_RUNFIRST= pov90 1

VPAD_RUNNER_RUNSECOND= pov0 1

VPAD_RUNNER_RUNTHIRD= pov270 1

VPAD_RUNNER_RUNHOME2SCORE= pov180 1

VPAD_BASERUNNER_ADVANCEALL= button 7

VPAD_BASERUNNER_RETREATALL= button 8

[PolishJoe]

Hey RedSoxFox7,

Honestly, I think you did a smart thing! :yeah: I don't like to force my opinions on people, but I think purchasing an adapter for your PS2 was the best! :mrgreen:

Not only did it cost you less, but it's far more durable than most regular PC controllers.

That being said, I think you'll find the attached zipped file should address all of your issues.

Just a note: Instead of thinking in terms of Swing = Button 3, I'd think of it as Swing = X, etc.

Let me know if you need any help with the file!

[RedSoxFox7]

Thanks man, I actually managed to figure it out on my own and it's been smooth sailing since.

It wasn't that I was opposed to getting the PS2->PC converter, I just didn't know where to get it at a physical store.

A few people on another forum were talking about the same thing and someone mentioned RadioShack sells them, and that was all I needed to hear.

Cost me a whopping $7.32, almost $20 cheaper than the Saitek after tax.

[PolishJoe]

Nice! :yeah:

Hopefully you'll be able to enjoy the game the way it was meant to be! :wink: