AimIsADick
Account Details
SteamID64 76561198443218901
SteamID3 [U:1:482953173]
SteamID32 STEAM_0:1:241476586
Country United States
Signed Up July 26, 2020
Last Posted February 26, 2024 at 8:36 PM
Posts 572 (0.4 per day)
Game Settings
In-game Sensitivity 2.21
Windows Sensitivity None. Accel: 1.9
Raw Input  
DPI
800
Resolution
1280x720
Refresh Rate
60hz
Hardware Peripherals
Mouse Razer Viper Mini Corded
Keyboard Integrated
Mousepad None
Headphones None
Monitor Integrated
1 ⋅⋅ 34 35 36 37 38
#28 Packet Choke issues. in Customization

Ok so I tried pinging (windows command ping) while TF2 was running, and I got this:

Reply from 173.194.219.103: bytes=32 time=18ms TTL=106
Reply from 173.194.219.103: bytes=32 time=19ms TTL=106
Reply from 173.194.219.103: bytes=32 time=28ms TTL=106
Reply from 173.194.219.103: bytes=32 time=72ms TTL=106
Reply from 173.194.219.103: bytes=32 time=21ms TTL=106
Reply from 173.194.219.103: bytes=32 time=18ms TTL=106
Reply from 173.194.219.103: bytes=32 time=19ms TTL=106
Reply from 173.194.219.103: bytes=32 time=20ms TTL=106
Reply from 173.194.219.103: bytes=32 time=24ms TTL=106
Reply from 173.194.219.103: bytes=32 time=24ms TTL=106
Reply from 173.194.219.103: bytes=32 time=16ms TTL=106
Reply from 173.194.219.103: bytes=32 time=170ms TTL=106
Reply from 173.194.219.103: bytes=32 time=20ms TTL=106
Reply from 173.194.219.103: bytes=32 time=118ms TTL=106
Reply from 173.194.219.103: bytes=32 time=18ms TTL=106
Reply from 173.194.219.103: bytes=32 time=273ms TTL=106
Reply from 173.194.219.103: bytes=32 time=31ms TTL=106
Reply from 173.194.219.103: bytes=32 time=19ms TTL=106
Reply from 173.194.219.103: bytes=32 time=17ms TTL=106
Reply from 173.194.219.103: bytes=32 time=23ms TTL=106
Reply from 173.194.219.103: bytes=32 time=18ms TTL=106
Reply from 173.194.219.103: bytes=32 time=21ms TTL=106
Reply from 173.194.219.103: bytes=32 time=170ms TTL=106
Reply from 173.194.219.103: bytes=32 time=19ms TTL=106
Reply from 173.194.219.103: bytes=32 time=47ms TTL=106
Reply from 173.194.219.103: bytes=32 time=18ms TTL=106
Reply from 173.194.219.103: bytes=32 time=19ms TTL=106
Reply from 173.194.219.103: bytes=32 time=18ms TTL=106
Reply from 173.194.219.103: bytes=32 time=20ms TTL=106
Reply from 173.194.219.103: bytes=32 time=38ms TTL=106
Reply from 173.194.219.103: bytes=32 time=46ms TTL=106
Reply from 173.194.219.103: bytes=32 time=22ms TTL=106
Reply from 173.194.219.103: bytes=32 time=31ms TTL=106
Reply from 173.194.219.103: bytes=32 time=19ms TTL=106
Reply from 173.194.219.103: bytes=32 time=22ms TTL=106
Reply from 173.194.219.103: bytes=32 time=21ms TTL=106
Reply from 173.194.219.103: bytes=32 time=18ms TTL=106
Reply from 173.194.219.103: bytes=32 time=65ms TTL=106
Reply from 173.194.219.103: bytes=32 time=296ms TTL=106
Reply from 173.194.219.103: bytes=32 time=326ms TTL=106
Reply from 173.194.219.103: bytes=32 time=322ms TTL=106
Reply from 173.194.219.103: bytes=32 time=18ms TTL=106
Reply from 173.194.219.103: bytes=32 time=20ms TTL=106
Reply from 173.194.219.103: bytes=32 time=18ms TTL=106
Reply from 173.194.219.103: bytes=32 time=19ms TTL=106
Reply from 173.194.219.103: bytes=32 time=138ms TTL=106
Reply from 173.194.219.103: bytes=32 time=19ms TTL=106
Reply from 173.194.219.103: bytes=32 time=18ms TTL=106
Reply from 173.194.219.103: bytes=32 time=19ms TTL=106
Reply from 173.194.219.103: bytes=32 time=19ms TTL=106
Reply from 173.194.219.103: bytes=32 time=19ms TTL=106
Reply from 173.194.219.103: bytes=32 time=19ms TTL=106
Reply from 173.194.219.103: bytes=32 time=18ms TTL=106
Reply from 173.194.219.103: bytes=32 time=18ms TTL=106
Reply from 173.194.219.103: bytes=32 time=27ms TTL=106
Reply from 173.194.219.103: bytes=32 time=323ms TTL=106
Reply from 173.194.219.103: bytes=32 time=27ms TTL=106
Reply from 173.194.219.103: bytes=32 time=18ms TTL=106
Reply from 173.194.219.103: bytes=32 time=23ms TTL=106
Reply from 173.194.219.103: bytes=32 time=18ms TTL=106
Reply from 173.194.219.103: bytes=32 time=22ms TTL=106
Reply from 173.194.219.103: bytes=32 time=19ms TTL=106
Reply from 173.194.219.103: bytes=32 time=18ms TTL=106
Reply from 173.194.219.103: bytes=32 time=19ms TTL=106
Reply from 173.194.219.103: bytes=32 time=20ms TTL=106
…

omfg there's a word limit? Anyway at the lowest settings possible I consistently got ~120fps across the board with updaterate and cmdrate at 33, and the choke issue still occurred. I'm getting a strong feeling that it's either the NIC or my internet.

posted about 3 years ago
#1 Launch Options leaked from 2020 TF2 leak. in Customization

I am documenting leaked launch options, because there may be some launch ops that could be useful. Let me know if I got a launch option's documentation wrong!

List Link.

posted about 3 years ago
#1 Voicemenu Generator in Customization

Repo link.

Voicemenu Generator (VMG) is a generator for emulated voicemenus. By emulated voicemenus, I mean emulating voicemenus through scripting and captions. "But couldn't you just change voicecommands.txt?" you ask, but you see, voicecommands.txt is not whitelisted in any sv_pure level higher than -1, so you can only remove entries. Even if they were in all sv_pure levels, voicecommands.txt is quite limiting, as you can't make entries run commands, can only use three voicemenus, forced to take a long time on unnecessary features, and even worse…you can't format the menu labels!

The alternative of course is to make emulate a voicemenu with scripting and captions. See you can bind a key to a command, but you can also bind a key to rebind other keys to rebind other keys to commands (this is the concept of a page). You can display what the binds do through captions, which also This is the concept of an emulated voicemenu. They are much less limited as you can format the menu labels, run any command through any entry, insert voicemenus into voicemenus to categorize binds (aka pages).

However, it takes a while to create an emulated voicemenu. You have to test it over and over, make more binds and . This is why I created the VMG: To reduce wasted time on making an emulated voicemenu.

"Why make an emulated voicemenu?" Well you could shift the binds that don't need direct input off your keyboard, to an external input system that doesn't cost money or isn't clunky to use, like an external keyboard. You could put chat binds, useful commands like load_itempreset and eureka_teleport into emulated voicemenus. That way you can use your keys for stuff that actually needs to have direct input.

(Yes the code may be bad, but it gets the job done.)

posted about 3 years ago
#27 Packet Choke issues. in Customization
SetsulDoing things you don't like to get things you do like is an experience not necessarily limited to your teenage years.

Then again I found a job I did like to pay for my first pc, I very much recommend that option.

Yeah. Even if I did find a job I liked, I'm still in highschool, so trying to focus on both would be hell. For now I'll focus on school (as in getting just enough to have a buffer from the bare minimum needed to pass to get into a high school job, not as in focus on getting all As because that is not happening ever), but after I graduate I'll immediately focus on getting a labored-based job.

SetsulAnyway, that's the end of the line for me. Sorry I didn't do anything but spread despair about the inescapable suffering of TF2 on a laptop but that's just how it goes. I played TF2 on a laptop with a 1.4 GHz single core Celeron from 2004 so I can tell you it could be much worse.

I dealt with this dilemma a while back, and it still keeps coming back, but in a much weaker state than the previous.

posted about 3 years ago
#6 Packet Choke issues. in Q/A Help
mastercomsAimIsADickTo add rotten cherries as well, it seems that the MTU size is hard coded as 1200 bytes. Why not just make a cvar for it so the user can use their optimized MTU size?Limitation in Steam.

I'd like to know more about this actually.

mastercomsAimIsADickWill you use the 2020 leak of TF2 as research in mastercomfig?Already done.

Ah ok. I was planning on replacing the list that could be junk with the list of launch options from the 2020 code leak of TF2. (NOT the documented list!)

posted about 3 years ago
#25 Packet Choke issues. in Customization
Setsul1.6 GHz baseclock sure is a treat huh. At least with only 15W it shouldn't overheat.
Could probably get more out of it if you manage to raise the TDP but laptop BIOS are usually fairly locked down.
Either way that goes beyond the scope of the choke problem.

Can't change the TDP from the BIOS. I would start working for a new PC…If teenage jobs didn't suck ass!

posted about 3 years ago
#23 Packet Choke issues. in Customization
turbochad69What cpu and gpu? Your fps seems extremely low for anything recent unless it's a celeron or something.

CPU: Intel(R) Core(TM) i5-10210U CPU
GPU: Integrated Graphics…

SetsulOh, shitty laptop suffering. Either way, 100%, you need all the fps you can get. Unless it's overheating, but that would be kind of embarrassing for a laptop that new.

Yeah it sucks.

posted about 3 years ago
#20 Packet Choke issues. in Customization
SetsulDefragging actually "damages" SSDs, but you do you. They can only sustain a limited number of write cycles and there are no mechnical parts so unlike with an HDD it really does not matter where the data is located. Not that defragging could do anything about that since they lie to the OS about where they put the data anyway. Wouldn't help with fps either, only loading times, but you do you.

Ah ok. I was unsure, but I'll stop defragging.

SetsulDo you want the CPU to outlive you? I guess it's kind of old judging by the fps you're getting but anything not overclocked or otherwise abused should last for 20-30 years.

It's one year old. (Yes, this is an intel laptop…) It's not overclocked.

posted about 3 years ago
#4 Packet Choke issues. in Q/A Help

As said from Setsul, the only thing that may be causing the choke is probably because of my FPS. I usually get ~60fps in a not maxed out server, and ~100fps when no one is around and I am in a tight room. I have no idea how else to optimize TF2 though…

posted about 3 years ago
#17 Packet Choke issues. in Customization
SetsulI'm pretty sure the fps drops cause the choke, not the other way around and I don't think I can do anything about it.
Did you only change the updaterate or cmdrate as well? I doubt it's going to do anything but I'm out of ideas beyond "it's the fps drops".

I did change the updaterate and cmdrate to both 33. Looks like I'll need to increase my FPS even further. Any tips to do so? I already:

  • Have the No Hats Mod. (I'll always have this regardless of if I need FPS, because TF2 cosmetics ruin the game.)
  • Excluded steam/appcache/stats from my Anti-Virus (Windows Security). Any more constantly written to files that I need to exclude?
  • Am using DX81.
  • Defragged my SSD *multiple times*. (I know it's generally not necessary, but you never know with how much misinformation is online.)

My resolution is 1600x900. I can reduce it further up to 720p. After that it's diminishing returns and I hate resolutions lower than that. I haven't disabled the Steam Overlay, because I commonly check profiles through the scoreboard. (Set tf_scoreboard_mouse_mode to 1 or 2 if you want this feature.)

Also note that I forced the maximum processor usage to 88%, because I value longevity.

posted about 3 years ago
#3 Packet Choke issues. in Q/A Help

Yeah from what Setsul said in the post in Customization:

SetsulYeah, I don't think you're getting choke because the packets jump to twice the normal size, you're getting packets twice the normal size because half of them are choked back so you get twice the data in the next packet.

Yeah this seems to be an issue with the game itself, and not necessarily my configuration or hardware.

To add rotten cherries as well, it seems that the MTU size is hard coded as 1200 bytes. Why not just make a cvar for it so the user can use their optimized MTU size?

(EDIT) P.S Will you use the 2020 leak of TF2 as research in mastercomfig?

posted about 3 years ago
#7 Moving mouse causes TF2 to drop 20-30 fps in Hardware

How expensive is your mouse? If it's not that expensive, I'd just replace your mouse in general. This issue sounds like an issue with the mouse itself.

posted about 3 years ago
#15 Packet Choke issues. in Customization
SetsulYeah, fewer packets mean they're larger. Sort of confirms that the packet size isn't the problem, you're simply getting larger packets after a choke to transmit the missing data.

Well do you get choke when you're near no one and get 100 fps?

updaterate 66: I still get packet choke sometimes even when I'm near no one, and my fps does drop, but not long enough to be measured. Also fps does seem to drop by ~20fps each time the choke occurs, but that could be from the net_graph itself.

updaterate 33: No packet choke or fps drops when no one is near me. fps still drops by ~20fps when it occurs though.

posted about 3 years ago
#13 Packet Choke issues. in Customization
SetsulYeah, I don't think you're getting choke because the packets jump to twice the normal size, you're getting packets twice the normal size because half of them are choked back so you get twice the data in the next packet.
Also solved the mystery of why your cmdrate drops: Your fps are dropping below 66. Makes no sense to send multiple packets per frame.

I don't know how to solve it either.

SetsulDo you get fps drops when the choke occurs?

Honestly I don't know how to solve your choke problem (not sure if it is solvable) but things are always going to be weird if your fps drop below your rates. Unless you've got a way to get more fps I'd say dropping your rates is actually a good idea for once. Maybe 40 or 33.

No FPS drops it seems. I only lose about ~10fps but that's probably coming from the net_graph's display.

Also when I set my updaterate and cmdrate to 33, now my game doesn't choke up often on packet sizes 1260-~1900. It only chokes up at packet sizes ~3000-~6000 bytes.

EDIT: When I'm near no one I usually get ~100fps.

posted about 3 years ago
#11 Packet Choke issues. in Customization

My choke goes as high as 25. Images of net_graph.

posted about 3 years ago
1 ⋅⋅ 34 35 36 37 38