What is your OS, launch options and config?

Windows 10

-high -noipx -novid -nocrashdialog -nojoy -noborder -threads 4 -useforcedmparms -noforcemaccel -noforcemspd -heapsize 4194304 -fullscreen -console +map_background preload_room +exec autoexec.cfg

should i make a mediafire link to my auto exec and the graphics config i use.
However i have 12 different graphic configs i switch from and i had the issue before putting in the configs

Remove -noipx -nocrashdialog -noborder -heapsize -fullscreen and +exec autoexec.cfg

Sure, mediafire works.

I understand the rest but why remove +exec autoexec.cfg? Its what activates my cfg isnt it?

Also here is the autoexec

https://www.mediafire.com/file/1aiz45a88o4f4jb/TF2%20Thing.rar

Autoexec gets automatically executed on launch, hence the name. If you add +exec autoexec.cfg, you run your autoexec twice.

I couldn't find anything that would cause it for sure, but you can try removing cl_forcepreload and sv_forcepreload. Also, you have 2 maps for preloading being loaded in your config, as well as one being loaded in your launch options. Try removing those, they might be preloading too many resources.

Also a bit unrelated but you should be executing the comfig file first and then the presets.

I do execute the comfig file first and then the presets

You sure theres nothing else i can try?

Try this in your launch options: +clientport 27006-27015

I had a similar issue in the past and putting that in my launch options sorted things out for me. It might also be worth adjusting the port range there depending on the ports of the servers you are connecting to.

Im currently banned from faceit and possibly tf2center atm now because of this issue i cant test out +clientport 27006-27015, is there anyway i can test this out?

jesus christ how horrifying

literally only three of those commands do anything you'd want (novid, nojoy, noborder), and you probably only need two. hell, some of them cancel each other out (noborder and fullscreen).

edit: here im just going to document it so people know in the future

-high increases TF2's thread priority, which should really not be an issue unless you've got a shitload of other applications open
-noipx just disables IPX networking which you don't use
-novid is actually relevant
-nocrashdialog is meant for srcds and does pretty much nothing for your client
-nojoy is really only useful if your game keeps enabling the gamepad and disabling mouse/keyboard (happens for some people), but apparently it doesn't even work anymore so YMMV
-noborder makes it so windowed mode is borderless fullscreen, if you're playing in actual fullscreen then this option does nothing
-threads forces TF2 to use a certain number of threads, this is very likely useless for you as TF2 automatically handles thread creation
-useforcedmparms -noforcemaccel -noforcemspd became irrelevant in 2011 when raw input was added
-heapsize was removed from the game in 2010, and even then, it never did what you thought it did. heapsize affects the size of the chunks of memory the game allocates over time, not how much memory it actually uses
-fullscreen is irrelevant because you can set this ingame
-console just opens the console when you start the game, it doesn't enable the console (there's an ingame option for that)
+map_background preload_room will launch preload_room, i assume you're doing this to preload. this can be moved to an autoexec line though, try:

map_background preload_room; wait 10; disconnect

+exec autoexec.cfg literally will make your autoexec exec twice, wtf. it already execs when you start your game. that's why it's called autoexec.

rent a server from serveme?

map_background preload_room; wait 10; disconnect

are you okay? XD it seems like your going into abit of a rant, but do you also have any fixes for the Sending Client issue? all you have done is explained to me what they do, which some i already have known what they do. You have not provided me with a fix.........

yeah it's a bit of a rant but now I can point people to my post whenever they add stupid launch options, which someone does every single day

oof so do you have a fix too my issue or?

well you have to test a bit more tbh, like pinging to a competitive server that you've rented is a start...

and maybe remove this from your profile since you're getting schooled hard here lol

https://i.imgur.com/QrMNqmC.png

remove literally all of those launch options, add -default to your launch options, and then try connecting to a problematic server.

if it still happens, it's an issue with the server, steam auth, or your computer outside of TF2. if it doesn't happen, you've got problematic settings because you copied whatever nonsense you found on the internet.

I'm sorry but I have to correct yttrium a bit.

-high improves responsiveness with better preemption and execution of tasks. It helps even with just background processes. However, these benefits depend on the CPU.

It saves a bit of memory and decreases startup time by preventing the joystick system from starting. It still works, you can check this by comparing the stdout output from TF2 when -nojoy is present and removed.

No, this tells TF2 how many worker threads are available for tasks. TF2's automatic detection for worker thread count is limited to 3 threads, so -threads allows you to force a higher count.

But some people have problems with raw input, so it is still useful for those with raw input disabled.

That's what priority is, yeah. But Windows should handle background process management enough that this shouldn't be an issue, no? And if you're seeing real benefit from this you should probably be using something like CPUCores (or one of its non retarded variants) that isolates background processes to separate cores.

Okay, so the documentation that it was removed in the orange box engine is wrong - but how much memory/startup time does it really save?

I thought it's been documented that any threads over 3 that it creates anyway are essentially zombie processes? Wouldn't mind a correction on that.

I'm willing to bet he has m_rawinput 1 in his autoexec, in which case that launch argument is pointless.

Just like the majority of these commands, they aren't ALL useless, but their use cases are so far and few between that it's probably a good idea to not propagate them on the internet.

try installing a new fps cfg and see if that helps, most preferably comanglias stability config

I have all his configs still not working ;(