big shmooz Posted March 16, 2005 Share Posted March 16, 2005 Does anybody know how I can configure either in the game or in the controller.cfg file to get the right shoulder button (button 8 ) to be the button to throw to the cutoff man from the outfield? I seem to get no matter what I do to adjust the numbers in the button configuration screen in the section of the controller configuration, or in the actual file of controller.cfg, to get it to only "fake throw" I am then forced to throw all the way to a base instead. Basically my problem is, that I can't seem to map the throw to the cutoff man from the outfield to any button other than my 7 button (left shoulder button). I will copy & paste below what my cntroller.cfg file looks like. profile= Saitek_Cyborg_Force_Rumble_Pad device= Saitek_Cyborg_Force_Rumble_Pad player= 2 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 3 VPAD_PITCH_2= button 4 VPAD_PITCH_3= button 1 VPAD_PITCH_4= button 2 VPAD_PITCH_5= button 8 VPAD_FIELD_PICK_OFF_THROW_FIRST= button 4 VPAD_FIELD_PICK_OFF_THROW_SECOND= button 2 VPAD_FIELD_PICK_OFF_THROW_THIRD= button 1 VPAD_PITCH_OUT= button 3 VPAD_THROW_BALL= button 7 VPAD_INTENTIONAL_WALK= not_assigned -1 VPAD_INTENTIONAL_HITBATTER= button 9 VPAD_PITCH_HISTORY_OPEN= not_assigned -1 VPAD_SWING_NORMAL= button 3 VPAD_SWING_BUNT= button 10 VPAD_CHARGE_MOUND= button 2 VPAD_FIELD_THROW_FIRST= button 4 VPAD_FIELD_THROW_SECOND= button 2 VPAD_FIELD_THROW_THIRD= button 1 VPAD_FIELD_THROW_HOME= button 3 VPAD_FIELD_SWITCH= button 6 VPAD_FIELD_RELAY_THROW= button 7 VPAD_FIELD_CUTOFF_THROW= button 8 VPAD_FIELD_FAKE_RUNDOWN_THROW= button 10 VPAD_RUNNER_FIRST_SELECT= button 4 VPAD_RUNNER_SECOND_SELECT= button 2 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 8 VPAD_BASERUNNER_RETREATALL= button 7 Can anybody post a solution? It would be greatly appreciated. Link to comment Share on other sites More sharing options...
big shmooz Posted March 22, 2005 Author Share Posted March 22, 2005 Anybody? Link to comment Share on other sites More sharing options...
Rylo_c Posted July 3, 2006 Share Posted July 3, 2006 got the game and the saitek p2500 today and i'm just setting the pad up. Did you ever find the answer to this question as i've modelled my cfg the same as yours. If anyone else knows it would be greatly appreciated Link to comment Share on other sites More sharing options...
big shmooz Posted July 4, 2006 Author Share Posted July 4, 2006 No, I never found an answer. I have gotten used to using the left shoulder button (the 7 button) over time. Link to comment Share on other sites More sharing options...
Kamasutra Posted July 6, 2006 Share Posted July 6, 2006 No, I never found an answer. I have gotten used to using the left shoulder button (the 7 button) over time. i've managed to map the relay to any button on my p880. I currently have it on button 6 (3rd button to the far right, top row) The secret is basically in the VPAD_VIRTUAL_BUTTON_R2, needs to be mapped to the button you will use for the cutoff, and that R1/L1 are NOT mapped to the cutoff (as it is in the default saitek profile). If you map the correct buttons, without overlapping the cutoff button, to the proper virtual R1/L1 L2/R2 L3/R3 you'll have no problems. Here's my file: profile= Saitek_P880_Pad device= Saitek_P880_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 8 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 3 VPAD_PITCH_2= button 4 VPAD_PITCH_3= button 1 VPAD_PITCH_4= button 2 VPAD_PITCH_5= button 5 VPAD_FIELD_PICK_OFF_THROW_FIRST= button 4 VPAD_FIELD_PICK_OFF_THROW_SECOND= button 2 VPAD_FIELD_PICK_OFF_THROW_THIRD= button 1 VPAD_PITCH_OUT= button 3 VPAD_THROW_BALL= not_assigned -1 VPAD_INTENTIONAL_WALK= button 10 VPAD_INTENTIONAL_HITBATTER= button 5 VPAD_PITCH_HISTORY_OPEN= button 9 VPAD_SWING_NORMAL= button 3 VPAD_SWING_BUNT= button 10 VPAD_CHARGE_MOUND= button 2 VPAD_FIELD_THROW_FIRST= button 4 VPAD_FIELD_THROW_SECOND= button 2 VPAD_FIELD_THROW_THIRD= button 1 VPAD_FIELD_THROW_HOME= button 3 VPAD_FIELD_SWITCH= button 5 VPAD_FIELD_RELAY_THROW= button 6 VPAD_FIELD_CUTOFF_THROW= button 6 VPAD_FIELD_FAKE_RUNDOWN_THROW= button 8 VPAD_RUNNER_FIRST_SELECT= button 4 VPAD_RUNNER_SECOND_SELECT= button 2 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 7 VPAD_BASERUNNER_RETREATALL= button 8 in this config, the following were changed from default: Relay Throw => Button 6 ( Default 8 ) VPAD_VIRTUAL_BUTTON_L2= button 8 ( Default 5 ) VPAD_PITCH_5= button 5 ( Default 8 ) VPAD_FIELD_SWITCH= button 5 (Default 7, i hated switching with the left trigger) Link to comment Share on other sites More sharing options...
Gordo Posted July 6, 2006 Share Posted July 6, 2006 Schmooz et al. I have the Saitek 2500 and I do believe my R trigger is the cutoff throw (isn't it amazing you can play a game with multiple button configuration, do them, but can't remember what to tell people what they really are? lol) Catch me on AIM (daflyboys2k3) and I'll send you my cfg file when I'm home later this evening. Link to comment Share on other sites More sharing options...
big shmooz Posted July 6, 2006 Author Share Posted July 6, 2006 Thanks guys. It is much appreciated. But now I will have to get used to the change all over again if I change my .cfg file. Link to comment Share on other sites More sharing options...
Kamasutra Posted July 6, 2006 Share Posted July 6, 2006 Thanks guys. It is much appreciated. But now I will have to get used to the change all over again if I change my .cfg file. no probs, just change the relay button in your file as mentioned, or stick with what you have :p Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.