Xbox 360 Controller Settings

[johnclark1102 276]

First of all, thank you for the excellent work on 1.0 and for including real Xbox 360 controller support and functions.

 

I'm having a few issues unique to using a controller, and am looking for the best way to correct these issues.

 

I'd like to know how to disable the "Quick Action Menu"? This is brought up by pressing and holding the left stick of the controller, and when doing so it slows time. Pressing and holding left stick is also the same button that I use to change my siren tones. I only play multiplayer, so I have no need for any of the functions in the Quick Action Menu and would rather just disable it so I can continue to change my siren tones while driving. After reviewing the user documentation and exploring the config file, it appears that the option "ShowQuickActionMenu=Capital" may disable the menu if I delete the value here. Is this correct, or is there a more appropriate way to disable the quick action menu?

 

I would also like to know if there is a different way to select options during a traffic stop. Currently, I'm prompted to use the D-Pad on the controller to select a reason for the stop, check ID or not, issue a citation, etc. However, the other functions of the D-Pad are not disabled, so while I'm making these selections I'm also changing weapons, bringing up the player list, and zooming in on the mini map. Is there a way to disable these functions and just use the keyboard to select options during a traffic stop?

 

Thanks for your help!

 

 

[Kevin376 4]

All your controls (xbox and keyboard) can be changed in your LCPDFR.ini file located in the lcpdfr folder in gtaiv. Open it up with note pad and change the value to whichever control you would like to use. 

 

Disabling the quick action menu can be done by deleting "Capital" and entering "None" for both enteries (Keyboard and Xbox) 

 

Same goes for changing the D-Pad, change each one individually 

[johnclark1102 276]

Excellent, that's what I thought.

 

Thanks for your help.

[Kevin376 4]

your welcome

[johnclark1102 276]

Sorry to bump this post, but I've recently tried using LCPDFR 1.0B since it was released, and I'm still having trouble with the Xbox controller for windows.

 

As I said in the original post, when I'm on a traffic stop or trying to work with a Ped, LCPDFR is prompting me to press the controller buttons to select the different dialog options (the Dpad buttons by default). However, all these controls do other things in GTA, such as changing weapons, etc.

 

Sometimes LCPDFR prompts me to select keyboard commands, and sometimes it prompts me to select controller buttons. Sometimes it will change the prompts half way through an interaction.

 

 

 

 

Is there a way that I can simply disable the controller support, and use only the keyboard commands like I currently do with version .95?

[LMS 2,065]

Hello,

 

LCPDFR will always switch to the most recent input device, so if you use your keyboard during a traffic stop but then press a button on your controller, it will use the controller. To entirely disable all LCPDFR controller settings, you have to map all keys to None. There is no other way at the moment.

 

LMS

[johnclark1102 276]

Hello,

 

LCPDFR will always switch to the most recent input device, so if you use your keyboard during a traffic stop but then press a button on your controller, it will use the controller. To entirely disable all LCPDFR controller settings, you have to map all keys to None. There is no other way at the moment.

 

LMS

 

Thanks for the suggestion, but that unfortunately doesn't work for me.

 

I set all the values to None but LCPDFR is still trying to prompt me to use the controller. But now that the keys are mapped to None, it doesn't know what key to use so I can't do anything. It shows me options like "Press ~ for Speeding", "Press ~ for Aggressive Driving" etc.

 

I try to just use the keyboard but it seems that once LCPDFR thinks I'm using the controller it won't respond to keyboard input.

Edited April 11, 2014 by johnclark1102

[LMS 2,065]

Ah sorry, I thought you just wanted to disable any LCPDFR actions via the controller. Forcing keyboard actions when using a controller is not possible, sorry.

[johnclark1102 276]

Ah sorry, I thought you just wanted to disable any LCPDFR actions via the controller. Forcing keyboard actions when using a controller is not possible, sorry.

 

No problem, thanks for the help anyway.

 

Maybe I'll get lucky with 1.0C and controller input can be made as a selectable option in the ini file.

[LMS 2,065]

No problem, thanks for the help anyway.

 

Maybe I'll get lucky with 1.0C and controller input can be made as a selectable option in the ini file.

 

Maybe ;-)

 

[johnclark1102 276]

So, I was very excited when I saw in the patch notes for 1.0C that controller input can be disabled now, by using the "AlwaysForceKeyboardInput option in the configuration file".

 

Well, I cannot find this option in the configuration file. I've looked through every line, I've used CTRL+F to try and find it, and I can't seem to locate it. I've tried using the automatic install, and the manual install.

 

Does anyone know where can I find this option in the configuration file?

[ineseri 5,125]

You will have to add it yourself, as the .ini isn't updated. 

[johnclark1102 276]

You will have to add it yourself, as the .ini isn't updated. 

 

Thanks for the help.

 

I tried adding it to the "Main" section of the config and it didn't work. I'm going to try adding it to some other areas but, I also thought it might benefit others here to have some guidance on how to enable this feature since the .ini file hasn't been updated.

 

Where are we supposed to be adding this line to make it work? Does it even matter where in the .ini we put it?

 

"AlwaysForceKeyboardInput=True"

 

Or is it just:

 

"AlwaysForceKeyboardInput"

 

Without the need for a true / false?

 

I couldn't find any information about this new feature in the documentation; the only mention I've been able to find for it is in the patch notes so I'm just not sure how to take advantage of this new feature.

 

[ineseri 5,125]

I think LMS is better off answering this haha. 

[johnclark1102 276]

No worries, I'll wait for LMS to come along and provide his insight while I keep working on figuring it out.

 

Thanks again!

[johnclark1102 276]

I hate to bump a topic, but I've been looking all over the forums and haven't found anyone else talking about this new feature to force the keyboard inputs and I haven't had any luck figuring it out on my own. So, I wanted to bump this topic in the hopes that someone who knows how to use this feature will see it before it fades into oblivion.

 

I'm dying to try out 1.0C, but until I get the controller / keyboard conflicts resolved, it's simply not playable for me.

[LMS 2,065]

I have received a few reports where this feature is not working correctly and I'm looking into it. Sorry to hear it also doesn't work for you, but looks you got to wait for another release then if you can't get it to work now.

[johnclark1102 276]

I have received a few reports where this feature is not working correctly and I'm looking into it. Sorry to hear it also doesn't work for you, but looks you got to wait for another release then if you can't get it to work now.

 

Thanks for the response! So far I haven't been able to get this feature to work. Could you provide some guidance on where the line is supposed to go in the .ini file, or what other steps need to be taken to enable this feature and I'll try it again?

 

I've just been trying it in random sections of the .ini file so I'm not even sure if I'm setting it up correctly.

[LMS 2,065]

It goes ins "Main", but as I said, there have been reports of issues with it. I'll take a look. Sorry this didn't make it properly to 1.0c.

[johnclark1102 276]

It goes ins "Main", but as I said, there have been reports of issues with it. I'll take a look. Sorry this didn't make it properly to 1.0c.

 

Thanks.

 

After testing again with the line in the main section, I can confirm that it is not working for me.

 

Looking forward to an update in the future; thanks again for looking into it!