Jump to content

17L20

Members
  • Content Сount

    85
  • Joined

  • Last visited

  • Battles

    10338
  • Clan

    [TMS]

Community Reputation

12 Neutral

About 17L20

  • Rank
    Petty Officer
  • Birthday November 12
  • Insignia

Profile Information

  • Gender
    Not Telling
  1. I'm guessing your double-click setting is a little slow. So the game sees the initial click and fires, then the double-click registers and fires the remaining guns. Try going to your Wndows Control Panel>Mouse and adjusting the double-click timing.
  2. You can modify a key that is already assigned to a double-click. So you can do a salvo fire with a single keystroke. But as Quaffer says, be careful. Strange things can happen when you mess with reserved keys. Here's how I recommend you do it. Start with clean default Controls. Start the game and enter the Settings>Controls page. Then assign the desired salvo key/mouse to the SECONDARY (right side box) Fire control (See the attached pic where I assign the middle mouse button to do the secondary Fire command and then, since I stole the MMB from here, I assign the Left Side mouse button for the Track Shell command). Apply the changes and exit the game. Now open your preferences.xml file and go to the <commands> section. It should look something similar to this (if you used the mid mouse button, otherwise the KEY will be different): <commands> <CMD_SHOOT context="ship" type="hold"> <VALUE key="KEY_MOUSE2" mods="" index="1" /> </CMD_SHOOT> <CMD_CINEMATIC_SHOOT context="ship" type="down"> <VALUE key="KEY_MOUSE4" mods="" index="0" /> </CMD_CINEMATIC_SHOOT> <CMD_SHOOT_SALVO context="ship" type="doubleTap"> <VALUE key="KEY_MOUSE2" mods="" index="1" /> </CMD_SHOOT_SALVO> Now, in the <CMD_SHOOT_SALVO> block, change the line type="doubleTap"> to type="down">. Your <CMD_SHOOT_SALVO> block should now look like this: <CMD_SHOOT_SALVO context="ship" type="down"> <VALUE key="KEY_MOUSE2" mods="" index="1" /> </CMD_SHOOT_SALVO> With the change, the game should see the 'down' action before the 'hold' action and salvo your guns. Save the file and you should be good to go. If you have any funny business, try deleting the <CMD_SHOOT> block. It might be interfering.
  3. Most players are familiar with the keyboard shortcuts to lock your guns on a particular bearing (Ctrl+X) or sector (Space+X). And these commands are real handy at times. But what if you're not real deft with the keyboard (like me) and want to assign those commands to different keys or mouse buttons. Unfortunately, there's no option for it in the Settings>Controls screen. So you must do it manually by editing the preferences.xml file. Here I'll show you how. But please be careful, and if you don't understand something, ASK. Because if you screw something up, well, you know the rest... 1. BACKUP YOUR preferences.xml FILE. Now open your preferences.xml file in your favorite text editor (I like wordpad). 2. Press Ctrl+F (find) and look for <commands>. It should appear near the bottom of the file. If it does, go to step 3. If not, then you've never altered a command. So do the following: 2a) Close the text editor and start up the game. 2b) Go to Settings>Controls and add a harmless key command. Example: assign the O key as the secondary key (right box) to the Reload Torpedo Tube command. 2c) Apply the command and exit the game. Start at step 1 again and you should now see the <command> section in step 2. 3. Next you must insert code into the <commands> section. Notice further down, there's a line that reads </commands>. This is the END of the section. If you have other keys reassigned or added, the code is inserted in blocks of code starting with the command name (like <CMD_TORPEDO_RELOAD) and ends with /command name (like </CMD_TORPEDO_RELOAD), (Note the forwardslash at the start of the ending command). You must insert code in it's own separate block. Between the end of one block and before the start of the next block. 4. To reassign a key/button for the Locked On Bearing command, insert this block of code: <CMD_RELATIVE_GUNS_LOCK context="ship" type="down"> <VALUE key="KEY_MOUSE4" mods="" index="1" /> </CMD_RELATIVE_GUNS_LOCK> Note that this will assign the command to the Mouse4 button. If you want a different key, replace the MOUSE4 with your desired key (Example "KEY_O" or "KEY_RBRACKET"). 5. To reassign a key/button for the Locked On Sector command, insert this block of code: <CMD_ABSOLUTE_GUNS_LOCK context="ship" type="down"> <VALUE key="KEY_MOUSE5" mods="" index="1" /> </CMD_ABSOLUTE_GUNS_LOCK> Note that this will assign the command to the Mouse5 button. If you want a different key, replace the MOUSE5 with your desired key (Example "KEY_P" or "KEY_LBRACKET"). 6. Save the file and start the game. If you screwed something up, the game will either crash or start and rep[lace the preferences.xml with the default one. In either event redo the process. Options: The code inserts will assign a secondary key to the commands. So the Ctrl+X and Shift+X keys will still work. If you want to replace the original key commands, change the index line from "1" to "0". If you want a key combo (a key pressed along with the ALT, CTRL or Shift key), insert that key name (KEY_LALT, KEY_LCONTROL, or KEY_LSHIFT) inside the quotes of the mods line (Example mods="KEY_LALT") If there's a part you don't understand or you think needs clarification, don't hesitate to ask.
  4. 17L20

    You could have asked!!!

    No [crap] they could have asked. Or at least notified us better than a short paragraph in the update news. I had several of my favorite replays saved. Now they're gone. Thanks a lot. (And no, they're not in the recycle bin)
  5. Sorry, I didn't explain it worth a crap. It's the semi-transparent minimap mod that I'm referring to. His minimaps have a grid spacing value in the upper left hand corner. In this case, 4.8km. I don't know if the author is still active or not, so I didn't know where else to post it. Since the gun range is 14.8km, the minimap gun range circle is 29.6km. And since the range circle covers 7 grid squares, the grid square value should equal 29.6 divided by 7, or 4.2km.
  6. I believe the grid spacing on the new Trident (41_Conquest) map is 4.2km. Not the 4.8km displayed on the minimap.
×