Overview
This guide shows an .ini file edit to enable Aim Down Sights / Iron Sights for keyboard and mouse players. (You can use ADS when using a controller already, but this allows you to setup a keybind to use that same ADS command with your mouse.)
Let There Be SIGHTS ┌┐▄┌┐
By default, there is no listing for an “aim down sights” command in the keyboard controls. You may notice in the keyboard control settings, that “TOGGLE THIRD PERSON” is disabled. Since it’s disabled and there’s no command for aim down sights, we’re going to change this command to actually invoke an aim down sights command and then manually bind a key to it.
You’ll only need to edit one INI file to get aim down sights for you keyboard and mouse players. You’ll need to open DefaultInput.ini (located in …SteamSteamAppscommonPrimal Carnage ExtinctionPrimalCarnageGameConfig ) in a text editor (notepad).
It’s recommended to make a back-up of this file in case you accidentially muck this up or your computer suddenly loses power or something like that…
*****
Go down to about line 37 in the file and you should see:
We’re going to change “GBA_ToggleThird” to the same aim down sights command that’s already programmed into the game, “GBA_ScopeFocus”. So now that line should be:
Now, whatever key we have set in game to the command that still appears as Toggle Third Person will actually be the key that will activate aim down sights. But we still need to define that key manually because we can’t do it in-game.
We’re going to set this to the right mouse button by default. This way, if we accidentially bind another action to the right mouse in game and it clears this key from our aim down sights, we can just click on Reset to Defaults to get it back to right mouse button (since, again, we can’t set it in-game). Go down to about line 192 and you should see these two lines (3rd line shown in the code box is actually part of the 2nd line):
Notice the commented line (starting with the semi-colon), it’s telling us that we can change this so that this action is bound to middle mouse button. Though it doesn’t tell us which action it is because all the actions are listed as “DefaultKeyboardLayout” It’s the order that is import-they match up to the actions listed in the Keyboard settings in-game. That line with no key bound to the action is the one originally for Toggle Third Person, but will now function as our aim down sights (“ScopeFocus”). Instead of using “MiddleMouseButton”, we’re going to use “RightMouseButton” so that we should have the following
Now we should see this in the game, the Toggle Third Person is set to RMB:
That’s (almost) it. Now you’ll want to go into the game, into the keyboard settings and make sure that you’ve got another key assigned to alt fire/alt attackIf you’re wonder why the heck I’d have “left” set as my alt fire, it’s because I’m using a mouse with extra buttons that I have programmed to the arrow keys. The button assigned to left arrow is just to the left of my left mouse button, almost like a second trigger. Otherwise I’d be using middle mouse button like I suspect a lot of people would choose.And if you’re wondering why A is set to use, it’s because I’m no WASD sheep and prefer the natural, standard position of my hand on the keyboard- I use ESDF for movement (also allowing for more keys within reach to bind actions to. Give it a try!)
Optional: Set Default Controls
Continuing from where we left off in DefaultInput.ini, we are at the section that defines the default controls (starting about line 174). You can set these to your controls so that if you ever accidentially unbind the right mouse button from Toggle Third person and you have to Reset to Defaults, you can get all of your keybinds back without having to set them again. So here you can set up your middle mouse button to your alt fire, and change any other keys you need to, so you’re all ready to go when you get into the game. You may need to click Reset to Defaults to get the keys to stick if you’ve previously had Right Mouse Button set to your alt fire
In order, the actions you are assigning keys to are (starting about line 174):
A list of mappable keys you can bind to can be found here:
http://udn.epicgames.com/Three/KeyBinds.html#Mappable%20keys
Just put the keyname you want to use (listed in bold on the page) in the quotes for each
Optional: Change Aiming Sensitivity!
I’ve noticed that the aim down sights sensitivity seems to be somewhat sluggish, in my opinion. If it’s fine for you, don’t bother with this part. But if you’re like me and find aiming down sights doesn’t let you turn fast enough, this will help you change that! (Unfortunately, this doesn’t seem to work the the Scientist (sniper) class with their tranq. gun… I’m not sure why that is…)
First, you’ll want to know what aim sensitivity setting feels right for you. Take note of what your sensitivity setting is already at in game. I have mine set to 3. But now we want to test out the aim sensitivity. To do that, start a new game, say a private server with just yourself. Once you choose your class *cough*Commando*cough* and are in the level, test out aiming down the sights and turning. If it is too slow, press the grave/tilde key ( ` ) (~) to open the console and type:
where F is a “float”, a decimal number, so for example, I tried:
and that’s what sensitivity I liked while aiming. (I was using 3 as my default sensitivity.) REMEMBER!: We are only changing the sensitivity to see what number feels comfortable only while we’re aiming. But if you want, you can repeat the same process (console command) to find a more comfortable normal sensitivity that’s a decimal number, like say 3.4, if you don’t like being limited to the integer values that are only available in the settings menu.
Got your aim sensitivity number memorized? And perhaps a new decimal sensitivity (for when you’re not aiming?) Good. Here we go, some advanced copy&paste stuff right here!
Again, this is all in DefaultInput.ini. At the very top of the file, line 6 your mouse sensitivity should be listed. If you’ve found a more comfortable non-aiming sensitivity, go ahead and change it here. So for me, I changed 3 to 3.4, like below:
Now we want the aim sensitivity to kick in, but only when we’re aiming. To do this, we need to add a few things to the GBA_ScopeFocus command that we’re using. At about line 80 you should see:
We’re going to add in commands to change the sensitivity to our aim sensitivity, and back to our non-aim sensitivity. I’m going to use my settings of 3.4 for normal sensitivity and 5.8 for my aiming sensitivity. So basically just copy and paste the below and change the numbers to the ones you want to use:
If this didn’t work, copy the lines/values you’ve changed from DefaultInput.ini and replace their old counter parts in PrimalCarnageInput.ini with the new ones from DefaultInput.ini. So for example, the last line we changed to change the sensitivity is also in PrimalCarnageInput.ini at about line 59: the same declaration for GBA_ScopeFocus. So replace that line with the one we changed in DefaultInput.ini.
All Done!
There you go. Now go kill some dinos!
Thanks for viewing!
Comments, Questions, Suggestions, requests?