Between 0.8375 and 1.0

why .8375 and not 0.8 ?

he did 67/80=.8375, which isn't even the "right" made up placebo formula

No, DoGJA's 80/ping IS the correct placebo formula.

You don't need truelightning < 1 at all unless your ping is greater than 80. As long as server-side reconciliation is used, there is little reason to use anything other than cg_trueLightning 1. So much that I've been tempted in the past just to make it default and non-configurable.

By the time the unlagged code can no longer do its job, if you actually use a lower value of cg_trueLightning you're trying to deal with this horrid wet noodle, when its best just to shoot at the player you see, and let the laghax do its work.

I don't think its ever very wise to set cg_truelightning below 0.75, which according to the formula would be recommended above a ping of 105. And while the higher ping you have the more lagged your lg beam is, I don't think lowering your truelightning value to see that lag does you much good. (It absolutely does what the cvar <1 is intended to do, but doesn't do you much good. :) At lower pings you can almost utilize some of that knowledge to help you correct, but as your ping rises its a lost cause.

67/80 = .8375

80/67 = 1.19

Correct, and despite the unlagged code's presence being able to find and hit players in the lagged path during its backwards reconciliation, there can still be benefits to players visually seeing a bit of their lg stream lag when in the 60-80 ping range, where a value between 0.75 and 1.0 may be desired, even though its not entirely necessary (for obtaining hits).

1.19 is correct for unlagged purposes of obtaining the hit, but ~.83 will allow you to get the hits and understand some of the compensating you may want to do to stay ahead of your opponent, rather than just obtaining unlagged validated hits.

Both are just handy calculations to approximate what you want. 80/ping is absolutely correct if you wish to see how lagged your lg beam is. But I wouldn't recommend anyone playing with a 160 ping to use cg_trueLightning 0.5 either.

If you just want to see it in the proper position despite it being lagged, yes:

y=1 (ping 80ms or less)
y=80 / x (ping greater than 80ms)

x is ping in ms, y is value of cg_truelightning.

Just pointing out the difference here is deciding whether it better to see where it is hitting, or just having it fairly straight but have some sway in the direction in which it is currently lagged so that you may compensate.

If you can play with it in its correctly lagged position, that's great, but most people cannot aim the lagged beam and totally disregard the crosshair.

Wet noodle shaft is the worst. Set it to 1.

1 and cl_autotimenudge 1

80 / ping = truelightning

i was reading this from the top down trying to figure out when i would learn how this became your formula ^_^

lol

I have ~80 ping and I used to play with cg_truelightning 0. I cant say if this is either good or bad, I guess it depends on the fighting situation, sometimes I can hit 50 percent shaft and sometimes only 15 %. With my current 0.96 I'm mostly at the high 20s/low 30s of accuracy. I'd say if you have a very stable connection (ping changes only by +1/-1) try cg_tl 0 for a week or something, but for 0 you have to ignore the crosshair completly and that's very hard for many players

Good Luck

No you don't have to ignore the crosshair, with sv_fps 40 and snaps 40, cg_truelightning 0 lags 25ms behind the crosshair assuming you have 0ms latency, now with the client side hit detection it would mean that it doesn't matter just aim the crosshair and bam it hits, but at 80ms you have to predict either way as that's when you the netcode stops increasing compensation for you ping.

What I used to do since I was playing at ~150ms was, set cg_trulightining 1, and predict at all times like I was aiming direct rockets, and I would get 20-25% acc assuming the enemy's ping was also stable.

Beam is a distraction. Ping is a disadvantage no matter what, so make it work.

I use cg_truelightning .65 for any ping over 45

I use small amount of truelightning, just to remind me that i shouldn't flick the shaft. You should stroke it.

it was only a matter of time...

I see what you did there.