well, i don't want this kind of screenshots actually :D

post a REAL screenshot :p, no troll pls man :)

medium (c)

post a screenshot of your shaft settings pretty pls! :)

guys this is a serious thread, no troll whatsoever

so post a picture of your shaft settings !

and tell me which one to use :)







ty in advance

I'm never happy with my shaft settings, not crosshair, not beam etc

style 5 is shit, dunno who the fuck likes that one

I wanted to use the superthinshaft mod with fov 130/zoomfov, but I need the zoom button and cg_zoomfov in other situations more

also the animation with style 4 is pretty disgusting imo and style 1, although I played the longest time with that is too fat

hearty do you like lightningimpact too? I set it to a high impactcap, but it helps in depth perception imho

naise, whats ur texture settings?

guess it's mostly

r_picmip 6
r_texturemode gl_nearest_mipmap_nearest

aka plaid quake or brutal minecraft (c) sharpe

well seems less exagerrated than some gl_nearest_mipmap_nearest configs i've seen, looks like the squares are larger and less IN-YO-FACE.

depends on the map I guess, and it was picmip 7 in the screenshot actually

http://i.imgur.com/wCHRNhM.jpg
cg_lightningstyle 4 no impact no truelightning default gun z,y,x
no impact.
But i change it a lot mainly thin lightingstyle 2 and thin 4.
If I was you I'd go with the medium one just because I feel too thin might force you to move your mouse too much.

I want strenx's cfg.

Also, seems like tankjr is easier to hit with lg than keel. I know keel represents the hitbox better though (what was that command to make tankjr smaller?)

r_lodbias, either 2 or -2 can't remember which

It's easy to test with bots or in warmup. The setting takes effect right away (no vid_restart).

what is r_lodbias?

ideal hitboxes:

cg_forcenemymodel keel/bright
r_lodbias -2

or

cg_forceenemymodel tankjr/bright
r_lodbias 2

is this still accurate after the hitbox changes and now that it's not a box anymore?

when they changed from box -> small cylinder, tankjr was too big for sure iirc, but now that the cylinder was made larger by 10%, small tankjr is really nice as well

strenx uploaded his cfg here 2 days ago :
http://www.sendspace.com/file/0nxumd

https://dl.dropboxusercontent.com/u/11777259/shot0047.jpg
https://dl.dropboxusercontent.com/u/11777259/h8m3.rar

Really nice crosshair !
I'm actually trying to modify it to suit my taste, yellow with black border.
Now I only need to find a way to make the circle more visible, but the transparency is already at 1.
Do you know how i can do that ?

If you're doing a custom xhair, you can use the xhair images that are in qlive. In the itemDef, set "background" to "gfx/2d/crosshair1.tga". That's the circle, this way you could perhaps use multiple ones to get the opacity you want.

thx, i'm gonna try that !

change the line #19 in xhairs.menu from crosshaire to crosshaira

Post hud element for time clock plz

menuDef {
name "CurrentTime"
fullScreen MENU_FALSE
visible 1

itemDef {
name "CurrentTime"
textalign 2
style 0
rect 5 15 50 12
visible 1
textstyle 3
decoration
forecolor 1 1 1 1
textscale .26
ownerdraw CG_LOCALTIME
}
}

thanks, awesome config.

http://www.pic-upload.de/view-19519451/lg.jpg.html

http://i.imgur.com/zuIWd7u.jpg

lightningstyle 2, drawgun 0

Post a screenshot of my shaft, you say?

I will PM you, tiger

…………………...„„-~^^~„-„„_
………………„-^*'' : : „'' : : : : *-„
…………..„-* : : :„„--/ : : : : : : : '\
…………./ : : „-* . .| : : : : : : : : '|
……….../ : „-* . . . | : : : : : : : : |
………...\„-* . . . . .| : : : : : : : :'|
……….../ . . . . . . '| : : : : : : : :|
……..../ . . . . . . . .'\ : : : : : : : |
……../ . . . . . . . . . .\ : : : : : : :|
……./ . . . . . . . . . . . '\ : : : : : /
….../ . . . . . . . . . . . . . *-„„„„-*'
….'/ . . . . . . . . . . . . . . '|
…/ . . . . . . . ./ . . . . . . .|
../ . . . . . . . .'/ . . . . . . .'|
./ . . . . . . . . / . . . . . . .'|
'/ . . . . . . . . . . . . . . . .'|
'| . . . . . \ . . . . . . . . . .|
'| . . . . . . \„_^- „ . . . . .'|
'| . . . . . . . . .'\ .\ ./ '/ . |
| .\ . . . . . . . . . \ .'' / . '|
| . . . . . . . . . . / .'/ . . .|
| . . . . . . .| . . / ./ ./ . .|

hwat is this? sad mummi?

It's that fucking dog again. He never looks this way though, only stares out to a non-existent horizon. :(

Lonely puppy. ;____;

am I the only one who sees a dick with some cum on it ?

>with some cum on it
bad news for your sir...

http://i.imgur.com/4tS48u9.jpg

shaft alltimes 30.

Thin shaft settings for ultimate dodge
medium shaft settings for mix of aim/dodge
large shaft settings for aimwhore (little dodge)

I've tried all those exact settings heartless posted + crosshairs at one time.

Results are as stated
usually hit 40 lg on thin shaft, while others hit me 30% on me
usually hit 45% on medium shaft others hit me 37ish
usually hit 47-50% on large shaft (+tankjr) however I get hit for 40-42% as well

So pick your poison.

For duel i'd use large shaft because normally you'd never take a 1v1 shaft fight straight on (you'd combo), so using shaft vs other opponents gun = easy frags. And if you take a 1v1 shaft fight you almost always win.

For CA i'd use thinshaft because you both have tons of health, but being able to own them and take no damage, means you can keep raping the other team, or 1v1 lg on thunderstruck is more boss when you dodge everything.

If NA had tdm i'd probably use medium shaft settings. LG is harder to get, so you need to kill them vs other guns, but also avoid a ton of spam from random faggots. So being able to dodge helps but you also want a quicker kill because of your low health/armor.

thks man

i'll take your advices into consideration

i think i'm gonna stick with medium shaft settings, i think i'm more used to it now that i play with it for like almost 2 years now

also, the medium shaft setting seems to be more balanced, it's aim+dodge like you said, usually my dodges>aim but still, maybe with these settings i can aim a little bit better

Do you really think that what you see effects your dodge ? Seems very weird to me,should be able to dodge as good with klesk as enemymodel and lightningstyle 3 for example :)

try the thinshaft settings (gunx/y/z changed,drawgun 2) and use truelightning .7 and then do some circles around people

the way the shaft looks and distorts with these settings makes strafing weirdly and holding a steady shaft on enemies much easier.

It's because the movement of the lg on .7 tl + the thinness of it makes it seem more wavy, but certain strafe patterns effect the flow of it subconsciously making you move in a weird way to keep the lock.

That is why when you learn how to use the strafe patterns + mouse aim, you can keep a lock doing the most ridic 360s on people.

If people microstrafe as another posted said, all you do is mimic it and the strafes do the work of aiming and if they move normally, I just circle them.

It's more technique driven for sure. It is harder to keep a scary lock on people (45% acc or higher) but much easier to dodge.

Anyway this is what i've observed for lg and lg settings.

And you might be correct sir :) Gonna fiddle abit.

what are your thoughts on truelightning? I remember syncerror posted it doesn't really matter nowadays, but then again he has no clue.

with TL of 0.8 i feel it is easier to dodge, and getting a more calm aim. Btw all top players prety much all use tl 0.8 to 0.9, strenx 0.8 cypher .8 - .9 etc.

i'm a top player and i use 1

what are your thoughts on truelightning? I remember syncerror posted it doesn't really matter nowadays, but then again he has no clue.

This is all well and good, except that truelightning does more or less nothing in QL. I would say that it does more or less nothing in Q3 too, except that without unlagged netcode, you can actually potentially reap the benefits of using it.
I know some people are still/have grown adjusted to using it... but I really can't understand why.
All truelightning does is delay the updating of the shaft animation by ((1-truelightning)*yourPing)ms. Provided your ping is <80, and the netcode is working in a correct manner, the LG shaft will be hitting what's under the crosshair, or REAL CLOSE, depending on how accurately the server gauges your ping for backwards reconciliation.
I can see the benefits of what you said, but I still think people should stop relying on weird truelightning, and learn what it actually does and why it does pretty much nothing for your accuracy.
inb4 Strenx, yeah I know he uses it and I still can't work out why.

That's what TL1 is supposed to do. In practice it does not. There are plenty of times when your LG is on the player yet you get no hits with TL1.

TL0 appears to be the only setting under which if the beam is on the player, hits are guaranteed. We all know how horrible that setting is though.

I've been using TL1 for a while (I've used all the critical values at one time or another, including 0), but I use it with the knowledge that what I'm being shown on screen as far as the shaft is concerned is not necessarily what's happening in-game.

Values between 0.75 and 1 make sense because they try to grab the best of both worlds.

Probably there is a formula for an "ideal" value that is based on your ping, but then you would still have to put up with a changing LG graphic + setting change on different servers.

I think a lot of people just leave TL at 1 and do whatever adaptations they need through other factors. One that can be said for TL1 is that the graphic always looks exactly the same regardless of ping or movement, and so in a way it can be ignored.

tl 1 is so terrible. The beam always looks straight but in reality it bends, so when you are in a lg fight you'll get raped by trying to always center it on the enemy. Especially if this nigga is a dodge type player, he'll force you to catch his strafes but your lg beam won't have the indication of how far back/ahead of the enemy model it is at.

The only way it works well is if you have very low sensitivity and low ping. At least use .95 or .9 to give you some indication when the beam is going to break off the enemy, so you can reposition (your strafe or mouse aim) to align it.

This is how you start to get the infamous 'DAT BOT LG LOCK' where anyone speccing you or the guy you're lging says dis nigga cheatin'


On lan i'd probably use 1 because of such low ping but never been on lan so dunno.


OSP lg was all strafe aim.
RA3 lg was all -50 timenudge.
CPMA lg was all xerp.
Quakelive lg is all visuals and mouse aim.

I can think of a few players with TL 1 who have godlike aim with lg
so the argument about TL1 being terrible is retarded

uh I didn't say its impossible to lg good with tl 1 I just said it's harder to dodge and to catch other peoples dodges.

I know toxjq uses 1 but that's because hes so precise in his mouse movements that the lg visual is nearly NEVER off the enemy model. Imagine that for a sec son, no large strafe/medium/short dodges can shake his aim off of you, that's fucking godlike and scary.

But for us mortals that shit is impossible, so I play more dodge style because my track ain't toxjq, so I need indication of where the lg will go.

It also depends what mode you play and who you lg on. Are your friends lging against pros? or scrubs? are they playing tdm? or 1v1 ts? it all matters. Dodges and jumppad lg and such all have different levels of skill. I can choose my lg fights in a game of ca and get 60% by picking easy locks, but that doesn't mean i'd be boss in a straight up lg vs lg fight. (i am boss though)

"TL0 appears to be the only setting under which if the beam is on the player, hits are guaranteed. We all know how horrible that setting is though."

What game are you playing?
And if you're going to say Quake Live, then on what ping?
The only situation in which what you just described is valid is if you are above the 80ms threshold for unlagged netcode and are forced to 'lead' shots.
Backwards reconciliation is designed in such a way that if you aim at the model, the server will do the correct calculations to determine whether or not that was a hit based on your ping...
I'm not going to get into an argument about the netcode, because the facts are plainly described in so many places that it'd be laboring the point.
If you have Truelightning set to 0, and are on anywhere above 2ms ping, then even if you were tracking perfectly with the crosshair on the model the beam will always be trailing (yourping)ms behind wherever the enemy actually is, yet the game would register perfect hits...
I have no idea what you are thinking...

"I use it with the knowledge that what I'm being shown on screen as far as the shaft is concerned is not necessarily what's happening in-game."

What on earth are you talking about? Yes, some players' dodgy connections have adverse affects on unlagged netcode, causing there to be a disparity between model and hitbox positions during fast movement... but if backwards reconciliation is running correctly the only place that you should be aiming is at the model.

I'll say it again, all truelightning does is delay updating the ANIMATION of the lightning beam.
It's exactly the same as machinegun, which has no beam. The HITSCAN is calculated in the exact same manner on the server... same with the railgun... all the lightningGun technically is, is a short range railgun that fires every 50ms and does 6dmg per hit, with a lightning beam animation thrown in there.

As for Jamalz, I really have no idea what you just posted, it's incoherent and only barely cogent.... The LG beam does.not.bend.... not ever.
Do some reading about how unlagged netcode works.

What game are you playing?
And if you're going to say Quake Live, then on what ping?

Quake Live, I've run tests from localhost up to 250 ms and many critical points between.

The only situation in which what you just described is valid is if you are above the 80ms threshold for unlagged netcode and are forced to 'lead' shots.

It doesn't work this way in practice.

Backwards reconciliation is designed in such a way that if you aim at the model, the server will do the correct calculations to determine whether or not that was a hit based on your ping...

I understand that and more.

It is not perfect, and part of this imperfection can be dealt with by using a truelightning <1.

I'm not going to get into an argument about the netcode, because the facts are plainly described in so many places that it'd be laboring the point.

I know what the netcode says as far as what can be known without the QL source.

What's important is the actual result with all the variables intact, in an actual game. We can use what's stated on paper as a guide, but when it doesn't measure up we must adjust our models.

If you have Truelightning set to 0, and are on anywhere above 2ms ping, then even if you were tracking perfectly with the crosshair on the model the beam will always be trailing (yourping)ms behind wherever the enemy actually is, yet the game would register perfect hits...

This is not true. Test it.

Compare the results with cg_nopredict 1, and cg_marks 1.

With 0, it _will_ hit if the beam is on the player. It's just that 0 makes it overly difficult to do this.

What on earth are you talking about? Yes, some players' dodgy connections have adverse affects on unlagged netcode, causing there to be a disparity between model and hitbox positions during fast movement... but if backwards reconciliation is running correctly the only place that you should be aiming is at the model.

Again, I know the intended behavior of the netcode and what it looks like on paper.

In practice it behaves differently.

I'll say it again, all truelightning does is delay updating the ANIMATION of the lightning beam.

Then the animation is always incorrect with TL1, since there is at least 25 ms delay with sv_fps 40. You can tell this by setting TL0 on localhost, and comparing it to sv_fps 40 to sv_fps 125.

The truth is some mixture between backwards reconciliation and the actual latency from the server and the ping. TL1 does not mean that "beam on the player hits". Localhost or lan may be sufficient for this due to hit cylinder size and player speeds, but it still wouldn't be exactly where it's displayed.

As for Jamalz, I really have no idea what you just posted, it's incoherent and only barely cogent.... The LG beam does.not.bend.... not ever.

He's talking in a practical, visual sense.

Actually if you're using cg_playerlean 1 and keel like the majority of players, when the player is leaning, the hitbox is not aligned with the chest but with the feet.

So using cg_truelightning < 1 helps since the beam stays a little behind, you can aim at the chest and still hitting the hitbox.

Or you can just aim at the feet. Or using tankjr. Or using cg_playerlean 0.

correct!

Try some #natdm.ql

Nvm.

THINSHAFT IS SHIT. PERIOD (especially when ur enemy usin micro-strafes while his hitbox stay almost at one place)
cg_lightningstyle 5;cg_drawgun 0

http://i.imgur.com/CCsjAE6.jpg

lol

problem? :D

n1.... you got the settings from wasoen didnt you? :D .... can't believe someone palys like that

No. You don't like the picmip 0, hu? Thought this was about shaft style.

FYI: I used to play with vertex lighting, where picmip improves depth perception. I also swap alot between 0 and 6, but everything in between is just blurry and ugly, as many other pictures in this thread show.

"like" is relative... I would not wana play with it on a competitive level ;D

Yeah, because it really matters when you play vs cypher if you have picmip 0 or 7! ;)

It does against someone same skill. At least I see the enemy model on maps like silence ;D

http://imgur.com/I3RHy3Z thin shaft + taking out impact considerably improved my dodge and aim, respectively. don't think I'll touch my LG settings ever again.

also TL is for queers. keep it stiff boyz

Why does everyone suddenly feel like they're strenx in this thread :DD?

Unfortunately shaft settings, like many settings, are often subject to extreme over analysis. That being said, I prefer the transparent wide beam.

interesting thread

my personal opinion is that cg_playerlean and cg_drawcrosshair are the only important settings regarding the lg

cg_playerlean should always be kept at 0 tbh

because the lean of the player can bit a bit distracting, when the model stays straight, it's actually easier to only focus on the hitbox

that's personal preference: anything 0.5<playerlean<1 is better than 0 in my opinion, as I think it helps adjusting faster to direction changes whilst dodging (especially if you aim at the legs with the lg) or just predicting airrockets more accurately

Ye preference but in ql you actually get away with lean 0 and tl 1 that wasnt the case in osp (which most quakers are most familiar with).

My shaft is long and wide.

I see what you did there, sneaky sneaky :))