cg_lightningStyle <1-5>: the looks of the lg beam. It's completely depending on preference.
cg_trueLightning <0-1>: controls, how much the beam bends. Most common settings are 0.9 and 1.

cg_gunX -10; cg_gunY 2; cg_gunZ -8 (default is 0; 0; 0): the placement of the weapon itself along the X, Y and Z-axis. With these settings, you will have thinner beam with cg_drawGun 1 or 2 (and you still won't see the weapon itself).
----> the commonly known term "thinshaft" is this: cg_gunX -10; cg_gunY 2 (or 3); cg_gunZ -8; cg_lightningStyle 4.


cg_lightningImpact <0-1>: enables / disables the showing of the impact on hit (it's like a little blob at the receiving end of the beam)
cg_lightningImpactCap <default: 192>: you can set the size of the "impact-blob", when cg_lightningImpact is 1.
cg_impactSparks <0-1>: enables / disables sparks on hit

cg_hitBeep <0-3>: the sound effect, when you hit. Some prefer 3 because of the lower tone.

cg_forceEnemyModel: the cvar for setting enemy model. Some prefer to use tankjr / bright exclusively for shaft, because it's wider. You can rack up multiple cvars for each weapons with using ";" and "set - vstr".

For example:
------------------
seta ch_customCrosshair "1"

bind MWHEELUP "vstr pummel"
bind MWHEELDOWN "vstr mgun"
bind r "vstr shotgun"
bind e "vstr nade"
bind c "vstr rocket"
bind f "vstr shaft"
bind q "vstr rail"
bind ALT "vstr plasma"
bind v "vstr bfg"
bind F2 "vstr nailgun"
bind F3 "vstr proxy"
bind F1 "vstr chaingun"

set pummel "weapon 1; vstr offset1; vstr model1; vstr zfov3; vstr xhair1; ch_customCrosshair 0; vstr gpos3; vstr wOn; vstr nudgeOff"
set mgun "weapon 2; vstr offset1; vstr model1; vstr zfov1; vstr xhair1; ch_customCrosshair 0; vstr gpos3; vstr wOn; vstr nudgeOff"
set shotgun "weapon 3; vstr offset1; vstr model1; vstr zfov2; vstr xhair1; ch_customCrosshair 1; vstr gpos1; vstr wOn; vstr nudgeOff"
set nade "weapon 4; vstr offset1; vstr model1; vstr zfov2; vstr xhair1; ch_customCrosshair 1; vstr gpos3; vstr wOn; vstr nudgeOff"
set rocket "weapon 5; vstr offset2; vstr model1; vstr zfov2; vstr xhair1; ch_customCrosshair 0; vstr gpos3; vstr wOn; vstr nudgeOff"
set shaft "weapon 6; vstr offset2; vstr model2; vstr zfov2; vstr xhair1; ch_customCrosshair 0; vstr gpos4; vstr wOff; vstr nudgeOff"
set rail "weapon 7; vstr offset2; vstr model1; vstr zfov0; vstr xhair2; ch_customCrosshair 0; vstr gpos3; vstr wOn; vstr nudgeOff"
set plasma "weapon 8; vstr offset1; vstr model1; vstr zfov2; vstr xhair3; ch_customCrosshair 0; vstr gpos2; vstr wOn; vstr nudgeOn"
set bfg "weapon 9; vstr offset2; vstr model1; vstr zfov2; vstr xhair4; ch_customCrosshair 0; vstr gpos3; vstr wOff; vstr nudgeOff"
set nailgun "weapon 11;vstr offset1; vstr model1; vstr zfov2; vstr xhair1; ch_customCrosshair 0; vstr gpos3; vstr wOn; vstr nudgeOff"
set proxy "weapon 12;vstr offset1; vstr model1; vstr zfov2; vstr xhair1; ch_customCrosshair 1; vstr gpos3; vstr wOn; vstr nudgeOff"
set chaingun "weapon 13;vstr offset1; vstr model1; vstr zfov2; vstr xhair1; ch_customCrosshair 0; vstr gpos3; vstr wOn; vstr nudgeOff"

set offset1 "cl_mouseAccelOffset 0"
set offset2 "cl_mouseAccelOffset 5"

set model1 "cg_forceEnemyModel keel/bright"
set model2 "cg_forceEnemyModel tankjr/bright"

set zfov0 "cg_zoomFov 35"
set zfov1 "cg_zoomFov 50"
set zfov2 "cg_zoomFov 70"
set zfov3 "cg_zoomFov 110"

set gpos1 "cg_gunX -2; cg_gunY 3; cg_gunZ -3"
set gpos2 "cg_gunX 1; cg_gunY 2; cg_gunZ -3"
set gpos3 "cg_gunX 3; cg_gunY 0; cg_gunZ -2"
set gpos4 "cg_gunX 10; cg_gunY 2; cg_gunZ -8"

set xhair1 "cg_drawCrosshair 2; cg_crosshairSize 30"
set xhair2 "cg_drawCrosshair 7; cg_crosshairSize 30"
set xhair3 "cg_drawCrosshair 7; cg_crosshairSize 37"
set xhair4 "cg_drawCrosshair 15;cg_crosshairSize 30"

set wOn "cg_drawGun 2"
set wOff "cg_drawGun 0"

set nudgeOn "cl_timenudge -20"
set nudgeOff "cl_timenudge 0"

seta cg_weaponConfig ""
seta cg_weaponConfig_g "cg_hitBeep 3; cg_crosshairHitStyle 2; cg_crosshairHitColor 1"
seta cg_weaponConfig_mg "cg_hitBeep 3; cg_crosshairHitStyle 2; cg_crosshairHitColor 13"
seta cg_weaponConfig_sg "cg_hitBeep 2; cg_crosshairHitStyle 1; cg_crosshairHitColor 2"
seta cg_weaponConfig_gl "cg_hitBeep 2; cg_crosshairHitStyle 1; cg_crosshairHitColor 2"
seta cg_weaponConfig_rl "cg_hitBeep 2; cg_crosshairHitStyle 0; cg_crosshairHitColor 1"
seta cg_weaponConfig_lg "cg_hitBeep 3; cg_crosshairHitStyle 0; cg_crosshairHitColor 13"
seta cg_weaponConfig_rg "cg_hitBeep 2; cg_crosshairHitStyle 2; cg_crosshairHitColor 1"
seta cg_weaponConfig_pg "cg_hitBeep 3; cg_crosshairHitStyle 2; cg_crosshairHitColor 13"
seta cg_weaponConfig_bfg "cg_hitBeep 2; cg_crosshairHitStyle 1; cg_crosshairHitColor 2"
seta cg_weaponConfig_cg "cg_hitBeep 3; cg_crosshairHitStyle 2; cg_crosshairHitColor 13"
seta cg_weaponConfig_ng "cg_hitBeep 2; cg_crosshairHitStyle 2; cg_crosshairHitColor 1"
seta cg_weaponConfig_gh ""
seta cg_weaponConfig_pl "cg_hitBeep 2; cg_crosshairHitStyle 1; cg_crosshairHitColor 2"



cg_drawCrosshair: the style of crosshair. Entirely up to preference, but many people use 2 or 7 for shaft.
cg_crosshairSize <default: 32>: the size of the crosshair.
cg_crosshairColor <1-25>: the color of the crosshair

These are the more common settings, that you can play with. There's some other little nuances you can tinker with, like different light-settings, modelcolors, crosshairhitcolors and such. Some people claims, that a bit lower contrast between the enemymodel and map objects (r_overBrightBits, r_mapOverBrighBits, r_mapOverBrightCap, r_ignorehwgamma 0 / 1 (1 works only, if r_enablePostProcess is 0)) helps shafting a bit - in the end, it depends on you, like so many things in the game.

Some people also say, that lowering your sensitivity is good for your lg, but for me, the opposite is better, so this is entirely up to personal preference too.
Many players using zoom while lg-ing, even in mid-range.

And lastly, the most important setting: practice, practice, practice @ Fatal1ty.

is there a point in setting up all these custom cg_weaponconfig thingies for each weapon instead of e.g.
bind e "weapon 6;cg_drawcrosshair 5;cg_fov 90;..."
for every weapon bind? (apart from the fact that the settings are only applied when the button is pressed of course)

If you press a button for a weapon you dont have (or dont have ammo for in the case of switchtoempty option), it wont apply those weapons settings without a switch

lulz, get good mousepad/mouse/120hz monitor = shaft 40+

ez

Could you tell me what mousepad/mouse is good?
I use Logitech G500 and Steelseries qck.

Tried Microsoft 3.0 - bad
Razer Abyss - bad

QCK is good. Some use the PureTrak pads. The latest Logitech G400 is the best mouse in the world, in my opinion. The Microsoft Wheel Mouse is a classic most players stand by. You basically want a wired mouse without angle snapping, 1000Hz report rate and a comfortable shape. I like the G400 a lot because @ 800 DPI you can move up to 4m/s before the sensor malfunctions. Definitely not the case with Microsoft Wheel Mouse.

1000 Hz is an overkill, for several reasons.

1. May be incompatible with some motherboards
2. Unnecessary CPU-load and extra burden on southbridge
3. May shorten the mouse's and / or USB-slot's lifetime
4. May 500 Hz be more stable
5. In some cases, can cause weird mouse behaviour
6. Only 1 ms difference comparing to 500 Hz in contrary of the above mentioned things

Most high quality mice are equipped with 1000Hz by default. I don't see a reason not to use it.

I see 6 reasons not to. Except Abyssus, where I'm forced to use 1000 Hz, unless I want 125.

1. This is uncommon.
2. If your computer can't handle the demand of a primary device maybe you need a better one.
3. Insignificant to most people.
4. Don't know.
5. Never heard of it.
6. If 1 millisecond is insignificant, why isn't 8-20? Most people have an average reaction time of 200 milliseconds. Therefore few would notice a difference if a mouse had up to 20 milliseconds due to the value fluctuation involved in calculating an average. Knowing this, would you mind using the aforementioned mouse? I wouldn't use it and it's for the same reason I choose to have a 1000Hz rate: I want as little obstruction between me and the game as possible.

1. Not everybody uses latest tech.
2. Maybe this is not the only device, there may be important programs running in the background, etc.. Anyways, money doesn't grow on trees, especially not in Hungary. EU prices but EU salary / 5 wages.
3. Sad to hear that. Maybe not everybody respects the things they have - or just have an infinite money supply and doesn't care.
4. I know. : )
5. I experienced it, multiple times during the years, on different computers, even with different mice.
6. 1 ms is quite insignificant. 8-20 is not, because it's 8x - 20x times bigger than 1. Not that 1 ms will be the weak spot in your game, that's for sure.

1. Then maybe they shouldn't play latest games : )
2. It's a little like complaining about radio draining your car battery.
3. My motherboard has 6 USB ports already. USB hubs are inexpensive should some fail.
4. If it functions better at 500Hz then maybe you should use it at 500Hz. This is specific to certain mice, though.
5. You never described what you experienced so I still don't know what you mean.
6. So an additional 1/10 of latency is noticeable by most people? Nah.

Twice the problems for 1/20 the benefit.

1. Quake Live is 4 years old already, Quake 3 is 13, War 3 TFT is 9 and SC: BW is 13 also, I believe. And I'm not really playing anything besides these - I'm getting older, and new games become more and more crap and noobish and I'm not feeling entertained. I play with great classics now and then though.
2. Totally irrelevant comparison.
3. As I said, some people just doesn't care.
4. I use everything on 500 Hz for good reasons. Except Abyssus, but we know why.
5. Changing sensitivity, lags, delay, even skipping
6. No. Most people don't feel a difference between 8 ms and 2 ms. Not even ~15 ms (wireless) and 2 ms, even when the difference is so obvious. They just don't have the proper neural system and hand-eye coordination to do so - or just don't realise, that the weirdness they feeling is the mouslag. But the difference between 2 ms and 1 ms is really insignificant.

I guess these mice would be better @ 500Hz...

http://www.esreality.com/?a=longpost&id=1265679&page=22

Check comment #14. : )

The reasons you don't use 1000Hz are: you're laughably poor, you use outdated technology and MUH USB PORTS. Never seen so much whining about something technologically superior. Keep on using your emoticons, autistic fuck. The best mouse in the world is 1000Hz and it costs 34 USD.

LOL YOU DON'T USE WHAT I USE SO YOU MUST BE RETARDED I AM THE BEST EVER LOLOLOLOLOL GET RAPED ON INTERNET FORUM BRO NICE EMOTICON LOL

this is what I read your post as

I don't care what he uses. I care that he's shitposting about 1000Hz mice like a dunce.

I'd say most probably you aren't getting stable 1000hz in-game playing QL (moving it around in circles obviously), even more so in newer games, and stable500hz>fluctuating 1000hz.
Also it will unnecessarily stress all CPUs (as that's how this works and it's more than you think), will have usb/motherboard power problems with lots of laptops and some desktops, dying usb slots, fps stutters, etc.....and all that for 1/1000 of a second less response time that no one in the world can perceive and won't get you a single frag, and remember not a single mice in the world really benefits from using more than 500hz tracking-wise (the only ones that do are the more than 10 years old microsoft and logitech mice and that's up to 250hz).

If you want to save milliseconds the way to do it is up to 500hz. 1000hz is simply overkill, with 1/20 the benefits of 500 and with lots of drawbacks.

You mean the logitech g400 that dies after 3 months because the cable gets cut down due to poor materials? You mean the logitech g400 that will work the exact same with 500hz while having 2x less the said problems?

Dude you came here in 2012. We've been on this for years.

Technically I came in your mom in 1987. Does that take away from your existence?

I'm older than that, which is not a good thing considering I'm posting on a gaming forum.

Ran out of ideas?

No, I have one more. Name your kid megaman4.

grandpa megaman1 will be proud.

hehehe nice1

You leave megaman alone

So if you run out of objective technical information to continue a debate in a well-mannered way or you cannot argue with other people's experience, you use brainless off-the-spot insults to "defend" your ultimately subjective and flawed opinion (which is only half on-topic, because I never said that G400 is not a good mouse), even when others also said, that you're wrong.

How clever, but I'm not gonna give you the satisfaction / self-justification to reply to your offensive rant in the same simpleton way. I was just trying to exchange experiences, but like many times, I was repelled by socially uncomprehendable anger and ignorance. So be it, not my money, not my temporal tripping into thin air. Feel free to rage, or throwing new insults at me.

On a sidenote, after reading your insightful post about my lg below; I'm not a great player, I don't play all the time, there're many people who are way better than me, but I don't have too much trouble with my aim, even if I had to 3x my sensitivity and my hands are a bit shaky due to carpal tunnel syndrome.

http://www.quakelive.com/#!profile/statistics/kasual


Have a nice day.

cg_teamChatsOnly 1

If you have no problems then your zero problems are doubled. That is the lesson you learned today.

You are having them right now, but more importantly than this useless discussion the thing is you'll redact a mail to logitech in the next months or year to get a replacement. And again, and again.

We'll see. I've had this mouse for 6 months now.

Most gaming mice don't have better tracking by just increasing hz. Actually those are very exceptional (1.1 sensor, old/classic logitechs) and the full benefit is reached at 250hz.

So all things considered, as you are not noting that no matter the pc 1000hz is always troublesome and detrimental, yes all of them will perform better at 500hz hence why the ninox aurora (aka the perfect gaming mice) will not use a higher polling rate than that.

Source: The very same thing you quoted (wmo part and comments), the japanese mousescore thing from a couple of years ago and actually owning the things instead of a 2012 user theorizing.

I hope unlike nymphets you can break 30% LG. You know what they say, when you can't aim you better use the most stable mouse possible.

My main QL account has 42% lg, 40.01% total accuracy including duel. In my current one it is just 40% lg, but playing against better players and the netcode/hitbox makes it harder to hit than when QL started.

Besides hitting lg is a lot more about positioning and strafing than moving the mouse. Any retard can hit 45%+ in CA with a ball mouse.

37% lg, 60 % rail. Ciao.

I play with 70 ping against 999 skill rating players. In addition, LG is not my strongest weapon, but I do hit 40 percent on elite dodgers. Can you say the same, o my brother?

I play with 70 ping against 999 skill rating players. In addition, LG is not my strongest weapon, but I do hit 40 percent on elite dodgers. Can you say the same, o my brother?

There, I could say it.

<3

As far as I know, the old 8 bit mice (WMO, IM 1.1, IME 3.0, MX300, MX500) reaches their full benefits at 500 Hz (1,55 and 4,91 m/s).

I'm looking forward to bst's mouse too. Based on the thread, it's getting to be pretty awesome in many ways. Except the "ninox" brandname. : )

cover that with a cooller sticker

That would be ultramegabrutal-CILLER. Too awesome to be true.

it's funny but it's not the reaction time that matters, it's the difference in reaction time. our reaction time could be 5 minutes, but if one person is 4:59 they'll win. but still don't think 1ms really matters.

You can force the abyssus to 500hz. I did so because mine was unstable @ 1000hz.

How?

Same as any other mouse - hidusbf.zip. Provided you're on XP. If not ask someone with your OS(mouse is irrelevant).

Using Win7. But what about the hardware switch on Abyssus?

I set mine on 1000.

Hmmm...thanks for the info, I'm gonna try that.

May the CPM-POWER be with you.

Because a lot of mice perform better on 500hz.

QCK is a bad mousepad, especially the QCK+ non team editions

Why? What is better then? And why is it better then?

You have one hour! Go!

Allsop XL, low static, high kinetic
Artisan ShidenKai Mid Large, slippery pad(glass coating over a cloth pad) which makes it feel like a plastic pad but less slippery. Low kinetic, low static.
I use the shidenkai mid large normally now, but if I am vs'ing someone really good at a LG duel, then I swap to the allsop.
Low friction pads take more dexterity, but they are more fun
Razer goliathus speed is basically a worse version of the allsop.
Razer goliathus control is just meh, but it doesn't stick on mouse feet. Some mice feet that are glossy and smooth have a tendency to stick more. The G9x feet are like this, but the feet on the deathadder work great.

Pads that aren't smooth can have less static friction but they don't glide consistently that well.
The best pad like this is the Artisan hien hard, if you want to go that route.

Most tribe ascend players migrated to the allsop xl pad and love it. My friend zubin was the one who started telling people to get it, and he is right.
Very cheap too.

The qck+ does not stay flat, and has a ton of kinetic and static friction. The team edition is the same thing but folds on itself less. The glide is not consistent either depending on how much pressure you put on your mouse.

The pad is an illusion. Aim is in your brain.

hehe I prefer the opposite where I want as much friction I can get and I actually find brand new qck+'s too slippery at first.

I use the same setup...g400s with PureTrak Talent and I agreement with this statement.

Tried G500 - usable - well, not a TOTAL piece of crap, but could be better several times

Have IME 3.0 - good / awesome
Have Abyssus - good / awesome
Have Salmosa - awesome
Have Diamondback 3G - good

Had Diamondback - good
Had MX510 - good
Had MX500 - good
Had MX700 - total crap
Had WMO - good / awesome
Had IM 1.1a - good / awesome

Tried Krait - good
Tried G1 - good
Tried G5 - was usable on non-homogenic patterned cloth pads with mid-high sens
Tried G7 - total crap
Tried G700 - total crap
Tried G400 - good
Tried MX300 - awesome
Tried MX310 - good
Tried Ikari Optical - good
Tried Kinzu v1 - good (if you can accustom yourself to the built-in accel)
Tried A4Tech X-710 - "somewhat" good
Tried A4Tech X-750 - bad
Tried Roccat Pyra wired - bad

Tried...many others. : D



But basically, if you like your Logitech's shape and weight, you can use it. In this case, practice is what matters.

lol. this is actually not a terrible advice. But I will say this, the one thing I've noticed from a new 144hz monitor is that my railgun has become more consistent, to the point where all the noobs think I cheat (wat a tragedy, they think the GoD cheats)

yeah. I think at my level I feel most people lack consistency in their mechanics. that's all. So @ op: just keep playing. I was terrible at this game an year ago and im still terrible at it now.

Have all of those, no 40+ shaft :( must really suck Im happy when i get 30

a) Sensitivity too high
b) Accel too high
c) FOV too high
c) Latency too high
d) Your opponent has great dodging

50 is the new 40 honestly. There are many poor dodgers. Most probably aren't aware of it because of first person view. Try your best to keep the crosshair on the enemy. That is what matters.

hehe.

a) its 4.25 (400dpi)
b) no accel
c) 100 fov
d) palying on 20-50 ping depending on loc
e) decent dodgin on most opponents, very good on few.

Seems OK. Maybe your crosshair obscures vision of enemy? Too big or too similar to enemy color? How much % do you hit on a bot, such as Hunter or Hossman?

Usually its about 40. Honestly, I think i just have bad aim. Hitting a rail is like a mini celebration for me.. The xhair is small, i use keel because I feel that its better for me.

Honestly, i just think I just suck at aiming, its not a settings issue. Although friends tell me that my aim has improved when i got the monitor.

Just practice then. It will pay off.

Hehe. Ive been doing so. :)

The cvars are:

cg_LightningStyle 1-5

Setting 4 is arguably the thinnest. Setting 5 has a nice feature in that it is transparent, although certainly much larger than setting 4. Some people like setting 2, as it is only slightly larger than 4, yet has a faster animation closer to the actual dps of the LG.

cg_Truelightning 0 - 1 (float)

Setting 1 snaps the LG beam to the crosshair. It might turn on some special anti-lag code that works up to 80 ms. In practice I've found that while it can work, the behavior of 1 is a little unpredictable. It seems like the beam is on the enemy, yet it does not hit. With practice you can get a good feel for when it does hit, and with a low enough ping it probably doesn't even matter.

Values between 0.5 and 0.99 are another option, with many players using values like 0.75, 0.85, 0.9, 0.95. I've been using 0.88 for some time at the time of writing, as with the normal pings I play at it seems to work well with the dodging speed of the enemy and the speed of my turns.

Hardcore LG beam investigators can try 0 for a while, to see just how deep the rabbit hole goes with it. Supposedly a beam with setting 0 will always register a hit if it touches the enemy model. It would seem though that this can happen with other values too, and using 0 can be extremely unpleasant.

The LG beam can be made thinner by doing the following:

cg_Drawgun 2
cg_gunX -10
cg_gunY 2.7
cg_gunZ -8

What this does is it shows the gun model but prevents it from wagging/bobbing, but then hides and centers it. The results a centered LG that is thinner than normal. Some players (not all!) find it easier to aim this way, myself included. Even when I used to play showing the guns, I would hide it for the LG.

cg_LightningImpact shows the little sparkler animation when the LG hits something. While this can help someone gauge depth with the LG, I personally have found it a distraction and I recommend turning it off.

By far the biggest help for me was to do the following:

Set map hellsgate pre-game CA with a friend. Both set handicap to 80 or so. Then LG fight near the "tower". Whoever kills the other jumps in the pit, then starts again.

Record a demo playing this for a while, then go back and watch it in timescale 0.25. You'll be surprised what you see. It will show you exactly what you're doing wrong, and what you're doing right in terms of the actual turns required to hit with the LG.

Then you can endeavor to fix the problem with sens changes, or strafe keys vs. mouse balancing.

If you know any really great LG users, record them and do the same so you can see what they're doing differently.

With time and practice you'll be an LG master. The tricky part then becomes being good with the other weapons and having great movement in addition to just having great LG aim.

thank you for this great post which will help the OP a lot

however, I wouldn't recommend hellsgate as an lg practice map at all, being the dodge patterns extremely easy to predict since it's so small (although it's good practice for +back defensive lg in my opinion, trying to lure the enemy in whilst running behind the main outern corridory "Pillars" always gives an advantage and it's a technique this guy should definitely learn)

it might actually develop wrong habits (monotonous dodge patterns)

i'd either go for almost lost or amphi if you really need to self-kill option

i watched my LG at .25 timescale and I'm starting to think I'm retarded

: D

Most players will tell you to use thinnest beam, low sensitivity, 120Hz monitor and maybe zoom. There is some truth to this, but I think what matters is what you're most consistent with. Strenx and Stermy have strong shafts and their configurations are quite different.

Strenx uses:

120Hz
~50cm/360
cg_lightningstyle "2"
cg_truelightning ".80"
cg_drawgun "0"
cg_gunx "0"
cg_guny "0"
cg_gunz "0"
cg_drawcrosshair "07"
cg_crosshairsize "32"
cg_crosshaircolor "25"
cg_crosshairhitcolor "1"
cg_forceenemymodel "tankjr/bright"
cg_impactsparks "0"
cl_mouseaccel "0"
r_lodbias "0"
+zoom

Stermy uses:

120Hz
~23cm/360
cg_lightningstyle "1"
cg_truelightning ".99"
cg_drawgun "0"
cg_gunx "0"
cg_guny "0"
cg_gunz "0"
cg_drawcrosshair "13"
cg_crosshairsize "53"
cg_crosshaircolor "5"
cg_crosshairhitcolor "1"
cg_forceenemymodel "keel/bright"
cg_impactsparks "0"
cl_mouseaccel "0"
r_lodbias "0"
-zoom

What I take away from this is the most common beliefs regarding good shaft aim are just preference. Low or high sensitivity doesn't matter. Thin or thick beam doesn't matter. Experience with the lightning gun is more important than everything else. You need to find what you're most comfortable with and work on improving it from there.

first line, fail. strenx said on his stream (he said it before as well) he uses 60 hz monitor

and stermy uses lower truelightning, not .99, dumbass, bah cba to read more, your post is obviously shit

Strenx does not use 60Hz in competition and Stermy does use .99 truelightning, dumbass. Your existence is obviously shit.

you're a clueless raging piece of shit
/ignore

I'm clueless.

that was 4 years ago lol Current Stermy Config from Qcon 2013 - Here

Same value.

2 nYmPhets
2 Lorfa
2 Retribution

Guys, thank you very much!
Now i will try to change my parameters.
I hope I can do smth and the reason in not my hands or mouse )

Which mouse do you use?

I use Logitech mouse, now it's G500. Mousepad steelseries qck.

I don't know why my shaft is so bad, because I have no problems with Railgun and Rocket, they are always more then 35%, but i never had shaft more then 30% and usually I have 22-24...

Pad is good. Mouse is good, but better if you disable angle snapping in options and overclock it to 1000Hz. Those are the only adjustments I can recommend. Removing angle snapping is a must, in my opinion. Also, if you do not have pointer precision disabled in Windows you should.

My mistake, I thought you meant the MX500. The G500 I know little about.

Dont overclock your mouse to 1000hz, retribution is clueless and a victim to the modern days belief that higher numbers are allways preferable. This is a really annoying thing and you come across it everywhere when subject is tech. More CPU Cores are allways better!!!!!!! Lolz you only have 4 cores in your mobile!! More megapixels are rules!!!! Why only hd resolution on a 5" screen, 4k is where its at!!!!!!

I recommend 500 or 1000. Whichever is most convenient. It definitely feels much smoother than 125.

It's not overclocking really, just increasing the polling rate.

The other stuff you wrote is like, unrelated.

If you're using hardware made after about 1998, there's really no risk to use 1000hz.
As Lorfa correctly pointed out, you're not actually overclocking anything. It's just that by default the motherboard polls USB devices at 125hz, but the maximum supported is 1000hz. Drivers like hidusbf.inf don't alter the functionality of your motherboard in any way, IIRC they simply alter the device driver of the mouse to request a different polling rate from the motherboard, that's all.
The only problem you're likely to encounter is that older sensors might not react properly at 1000hz, and might suffer from some glitches, but that's not "Dangerous" in any way. If you're using a newer mouse, and a proper motherboard that cost more than $10, then 1000hz > 500hz > 125hz.
There is a small amount of input lag necessary to detect a change and interpolate mouse pointer positions, 125hz = 8ms, 500hs = ~2ms, 1000hz = ~1ms
Less time between updates = less input lag.
Deal with it, it's simple math.

You're welcome.

I'm not at home right now but I'll try to compile a few that I know by heart.


cg_lightningStyle ["1,2,3,4,5"]

Gun position:
cg_guny (max 10, min -20, default 0)
cg_gunz (max 0, min -8, default 0)
cg_gunx (max 10, min -10, default 0)

You can push the weapon behind the visible area easily with this commands, resulting in a thinner shaft (if you prefer those).
Play around with those until you the the value that fits you most.

cg_truelightning (0 to 1) - this is a tricky one, each person prefers a different value, it's hugely based on what ping you play on.

If your ping is less than 80, I recommend something between 0.8 and 1.

Go on an online server, wiggle around with your LG with truelightning 0, you will notice the beam lag behind the crosshair.

another thread about TL

cg_lightningImpactCap - Change the size of the lightning impact effect when impact is closer than x units.

don't mess with parameters, just point and track

This statement is simultaneously wise and stuipid at the same time.

nah, he should just ask some cheater for aim assist, then he doesn't even need to point and track

I use default settings. I hope that helps.

huuuuge

dont think about lging. just concentrating on keeping the crosshair on enemy model and your dodging

its all about positioning and playing smart. and in TDM making good use of distractions / teammates is great, I managed to get a 40% with 80 ping once just cause I kept catching people out as they were fighting my mates :p

Don't listen to the retards and stick to truelightning 1 : the game is antilagged up to 80ms, until 100ms timenudge -20 or autotimenudge 1 do the job and you'd be crazy to play above that anyway.

little edit : using the gunoffset stuff to get a thinner shaft isn't a bad idea but I wouldn't really recommend that with lightningstyle 5 because it makes the beam even more blue. I can't see shit through that.

do you know why ql won't let me set cg_autoprojectilenudge 1? it's min/max 0.

thanks for making me aware of autotn btw, when was that introduced?

autotn has been around on and off for a while, been using it since the previous update. As for projectilenudge was 0-80 during the previous update, no idea if it actually did anything at all.

you mean cg_projectilenudge and it works (again), visibly changes stuff now actually. what i meant was the auto function for that, they added it but kept it to min/max 0.

I'd love to get a few tips on how projectilenudge works, I could use something like that ( values/ping basically )

I remember something about setting projectilenudge to your ping and this will make projectiles appear as they do on LAN. autoprojectilenudge is probably disabled for this reason, because if the value needs to be higher than 80 I imagine visuals get really messy.

ye, nudge = ping, but it's starts getting weird at around 40-50. if you are close to someone with rl it's harder to dodge when the rocket spawns 5 meters in front of him :C

wait what? They added autotn again?

Depends. Would your whine be worth reading again if I said yes ?

I said they should implement it... they did... we tested it... it was awesome... they didn't want to put it into the game due to some sound bugs on high pings :S

cg_drawcrosshair makes a difference i believe. 2 (cross) is easy to lose on your screen and seems to make me overreact more, so i use 7 (cross + circle) which seems to steady my aim and keep LG locks

and if you have a compulsion to get LG thinner than the gunz trick it's possible, but it takes a long script

@OP

This is a really big topic which might be better to continue once you've read everything in this QL Forum thread: http://www.quakelive.com/forum/showthread.php...next-level

Surprising I know but there is some useful stuff there sometimes...

m_pitch 0.025

/thread

w/ m_yaw 0.015

How can you say that the WMO isn't good and then list 1.1 and 3.0 as good, when they share the same sensor?

oh ok, jiggly deleted his long ass post. Great.

Becos 2 year old thread
Also becos I remember dis is esr n i mus win at tru cancer


I didn't mean the sensor, the shape of the ime 1.1/3.0 give you better control of the mouse. I've heard the same thing said by pretty much anyone(who is paying attention) that the IME 1.1 shape gives significantly more control than the WMO.

2 years old thread..

Timeless subject.

R_ignorehwgamma "1", r_gamma "2.5", cg_lightningStyle "1" = pink shaft = amazing accuracies. You'll be king of shaft in no time!
http://i.imgur.com/pMyEDiE.jpg

lolnodepth

a completely uniform texture layout is much better for no distraction hitscan

depth is for people who use projectiles

probably, but then again, shafting up close and shafting far away is quiiiiiiite different. that config gets about as lolnodepth as ive ever seen haha

yea that is nex level
burning my eyes

a completely uniform texture layout is much better for no distraction hitscan

depth is for people who use projectiles

that lllllllllllllgggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggg

12in x 1.8in

not one player on this thread has kilt me more than a few times 1v1 LG ....


and i use stock config ....