Quick-start config for LG aimers

Common cvars used to improve LG

Section

They say config doesn't matter that much. It does matter. Having the right config can boost your LG acc by up to 15%.
I'm going to show you the important cvars for getting good LG.

Prerequesites to this guide:

• You already know how to aim
  
• Your pc and monitor can run at least 120 fps.

If you don't have the top hardware, you will never reach your maximum potential.
I personally play Quake with a GTX 980 Ti.

The values listed here may vary depending on your hardware.
These are the important cvars:

• com_maxfps 144: Set to refresh rate of your monitor (60, 120, 144). If you want to go higher FINE. THATS YOUR CHOICE. BUT JUST MAKE SURE ITS STABLE. People give me s**t for saying 144 fps and yet nobody can explain why it should be higher than your refresh rate.
  
• r_displayRefresh 144: Set to refresh rate of your monitor.
  
• cl_timeNudge -20: Set this to as low as you can.
  
• in_mouse 2: Just do it.
  
• cl_mouseAccel 0: Mouse accel screws up aiming. Always set to 0.
  
• sensitivity 2: Low sens for good accuracy. For 400 dpi mouse, anything near 2 is good to start with. If you have 800 dpi, try sensitivity 1.
  
• cg_lightningStyle 5: 5 or 2 are good. The other effects are too distracting.
  
• cg_gunY 2.5: Centers your LG beam
  
• cg_drawGun 0: Remove gun distraction
  
• cg_trueLightning 1: Remove LG sway

The following ui settings are optional and highly preferenced based:

• r_overbrightBits 3: Makes enemies and your crosshair uber bright
  
• r_mapOverBrightBits 2: Makes map and rest of ui kind of dark (Set to 3 for bright map)
  
• cg_enemyHeadColor 0xffffffff: Make enemies bright white
  
• cg_enemyUpperColor 0xffffffff
  
• cg_enemyLowerColor 0xffffffff
  
• cg_forceEnemyModel keel/bright: keel is less ambiguous than tankjr for precise targetting
  
• cg_drawCrosshair 22: The best crosshair.
  
• cg_crosshairSize 48: Big
  
• cg_crosshairBrightness 1.0: bright
  
• cg_crosshairColor 1: and bloody.
  
• cg_lightningImpact 0: Distracting
  
• cg_impactSparks 0: Distracting
  
• cg_drawFragMessages 0: Distracting
  
• cg_drawRewards 0: Distracting
  
• cg_drawAmmoWarning 0: Distracting
  
• cg_simpleItems 1: Less distracting

The above ui settings give you a darker map, bright white enemies, and big bright red crosshair.

If you don't like that then you can also try these alternatives:

• Normal map, bright green enemies, big bright yellow crosshair
  
• Bright map, bright white/green enemies, big black crosshair
  
• Dark map, bright green enemies, big bright yellow crosshair

The whole idea is there should be contrast between the enemies, the map, and your crosshair.

[chedca]

I take it back this bitc cheat for sure

[chedca]

my game improved for this guide. ty OG, sorry i thot you cheat

[^5*^4WRAITH^5*]

Hmmmm... I think there are a lot of cvars missing from this because...

1. Maps are still bright as shit
2.Are the crosshairs supposed to turn light blue when hitting enemy?
3. With these settings alone, config still feels like a crappy default config.
4. What about internet settings for optimal gameplay online? ( besides cl_timenudge )
5.Is there a certain config that you have modified with these settings in order to get the dark maps, and bright crosshairs that you were talking about?


The Red Crosshairs and Bright white keel are a cool Idea. I really enjoyed that. And the LG centered to crosshairs. I had no idea you could center the beam.

[_nucle0n]

[PART 1]

So much wrong, but since you're obviously a troll, it's unlikely this guide was ever intended to help anyone.

Firstly, having maxfps set to ANY value other than 125 or 250 results in a reduction in the number of packets being sent, which will cause the player to warp and be harder to hit. This behavior is inherent to the engine. What's particularly amusing is that cl_maxpackets was cheat protected over a year ago, because players were abusing it by setting their maxpackets low, thus causing them to microwarp and become harder to hit, while also instakilling people with their warp. Sadly, this "cheat" can still be achieved by using max fps values like "144".

Secondly, there is no such thing as 144 fps in Quake. The engine can only run at 250, 200, 166, 142, 125, 111, or 100 fps (I won't bother listing lower numbers). When you set your max fps to 144, you're actually getting 166. The 142 and 166 increments are both the worst for warping, by the way.

[_nucle0n]

[PART 2]

Even IF there was an actual 144 fps mode in Quake, and even IF it wasn't a warp exploit, setting fps to the refresh rate still makes no sense. Unless you're using gsync or vsync (more lag), the timing of the gpu and the monitor will not be synced. Just because the two numbers are the same does not mean the timing of both devices is synchronized. Higher fps means greater odds that an up-to-date frame will arrive to the monitor at the moment it's ready to refresh.

Regarding timenudge, this is yet another example of something that is easily exploited. While it's fine to use on high ping, it easily becomes abuseable at lower pings. Using TN has its pros and cons, but it leads to annoying playstyles at moderate to low pings. Nothing related to networking or lag compensation should be user adjustable, because it's so open to abuse.

You should also stop playing on wi-fi or whatever else you're doing. This netcode greatly rewards warp and playing on wi-fi is another exploit.

[Dr_G]

Not exactly. Setting r_displayrefresh can be useful.
See here:
http://fatal1ty.com/fatal1tys-quake-live-configs/

[Brandon]

Ok, you suggest setting the frame rate to the monitor refresh, but there is no reason for that. Do you really think people with a 60hz monitor should set the max fps to 60? That is just ridiculous, they would have worse screen tearing for no reason. There is absolutely no reason to restrict the frame rate to your refresh rate, but there is a good reason to set it higher. That is why I gave you a thumbs down, and I didn't even bother to read past that point before giving it.

[OrangeGirl]

If you're going to reject my guide at least give a reason.

[FAB]

com_maxfps 144

nope.

[Brandon]

@^1Ку^7д^1ес yeah I'm not sure why anyone would limit their FPS to the monitor refresh rate.