Hello,

I've wanted to make a "better" respawn bind for a long time, I've finally taken the time to make one.
It makes use of class switching rather than loadout switching (except for Medic), it's quite similar to a loadout switch bind.
You hold your respawn key, it switches you to a random class, you release the key, it switches you back to the previous class. If you mis-time it, you can just click again and switch back to the previous class. It probably works if you spam the key as well, but I wouldn't.
It should work regardless of other scripts, it makes use of "native" features only and does not require you to overlay all your class change binds.
It may not work in situations where all class limits are filled up (e.g.: highlander lobbies).

https://github.com/ldesgoui/tf2-custom/tree/master/optimal-respawn-bind

It may not work for everyone, but it works for me, and I'd rather share it than keep it to myself.

Hopefully you can make good use of it.

done

Y'a un mot de passe?

pas drôle, n'a pas rigolé

surely you have something better to present, right?
you wouldn't be talking shit if you had nothing to back that up, right?
what's less outdated than the latest mumble release candidate, dated 16 days ago?

TF2 is a single-threaded game that bottlenecks primarily on CPU
Your CPU is fairly dated and is designed for laptop usage
You're not going to get good performance, sorry

Your best bet is to reduce the resolution
Also 20/30 fps is a considerable improvement

Yep, thank you, I think we bought the domain a few hours after your post

https://do-i-play-too-much-videogames.com/
Don't take the personality test at the end it's not worth the time spent

My results

You can ask for your account to be permabanned without throwing a fit, just so you know

Does your cfg folder contain a server.cfg file? If so that should be it

done

done

Hopefully I make this concise and simple:
- Client and server communicate by sending network packets to each-other
- Different type of data is sent through different types of packets depending on the use case
- Different types of packets have different guarantees (can packet loss be ignored, can packet duplication be ignored, can packet order be ignored)
- View Angles are sent in packets that have the lowest guarantees because: we only want to know what a person is aiming at *now*, guarantees add virtual latency, we can fake through packet loss by pretending to receive the same packet and reconciliating once the stream is back to stable
If you want to learn more, read https://gafferongames.com (https://github.com/gafferongames/gafferongames/tree/master/content/post)

What you see is: scrambled gets a ping spike, his packets will lag in transit, server will pretend everything is normal by replaying his previous packets, his ping spike will stop, new packets will arive at the same time that the old packets and server will accept both as source of truth, producing what you saw

https://cdn.discordapp.com/attachments/533502615065985025/590169029277122560/IMG_20190617_145830__01.jpg

It could be video memory (which Shadowplay definitely makes plenty use of), what GPU do you have?
Verify game files

If you want to push it as far as using server mods, it should be possible to raise the max as long as FCVAR_REPLICATED doesn't fuck with that, which I doubt it does.
I know there's a generic SourceMod plugin that lets you change ConVar flags (mainly used to disable the sv_cheats requirement) but I'm not sure if there's one that lets you fuck with default/min/max, I'm gonna start looking, otherwise it should be fairly easy to implement.

What I'm getting at is, if this is wanted, it can be achieved. Most likely.

EDIT: sm_cvar was the command I was thinking about, according to docs it doesn't respect min/max bounds, I'll try this locally.

EDIT 2: ^ didn't work, this does; https://github.com/ldesgoui/unbounded_mp_bonusroundtime/releases

I'm quoting a post asking "Why do you think it's successful?" and bringing up the reason why I think it's successful.