http://teamfortress.tv/forum/thread/331-the-120hz-monitor-thread
search bar
Account Details | |
---|---|
SteamID64 | 76561198020256631 |
SteamID3 | [U:1:59990903] |
SteamID32 | STEAM_0:1:29995451 |
Country | Pirate |
Signed Up | November 3, 2012 |
Last Posted | August 17, 2025 at 2:07 PM |
Posts | 1111 (0.2 per day) |
Game Settings | |
---|---|
In-game Sensitivity | |
Windows Sensitivity | |
Raw Input | 1 |
DPI |
|
Resolution |
|
Refresh Rate |
Hardware Peripherals | |
---|---|
Mouse | yes |
Keyboard | yes |
Mousepad | no |
Headphones | yes |
Monitor | 2 |
It's very inconsistent. I've tried macros, and because of the way tf2/source works, you have to set the delay between inputs to be just perfect, if it's too fast none of them will reg, if it's too slow it won't work.
The bug itself is the same as the edgebug that is used in trickjumping, and why sometimes if you're doing a pogo in a jump map you can hit the ground and do a speedshot unintentionally, even if you should get teleported back.
My guess is that it's related to the game doing physics collision checks, and any status-based modifiers which derive from collision are done after, and valve counted on them happening on the same game tick.
AMD FX 4300 @ stock clocks
GTX 560-ti II
16 GB 1833 MHz RAM
Testing different resolutions to see what the effect is on framerate
IN WINDOWED NOBORDER:
@ 1650x1080
2639 frames 26.881 seconds 98.17 fps (10.19 ms/f) 6.203 fps variability
@ 1440x900
2639 frames 26.724 seconds 98.75 fps (10.13 ms/f) 6.068 fps variability
@ 1280x800
2639 frames 26.932 seconds 97.99 fps (10.21 ms/f) 5.961 fps variability
@640x480
2639 frames 24.846 seconds 106.21 fps ( 9.42 ms/f) 6.491 fps variability
Clearly has no effect on performance in windowed mode, though the last number is interesting.
IN FULLSCREEN:
@1650x1080
2639 frames 26.678 seconds 98.92 fps (10.11 ms/f) 6.644 fps variability
@1440x900
2639 frames 26.806 seconds 98.45 fps (10.16 ms/f) 6.015 fps variability
@1280x800
2639 frames 26.796 seconds 98.48 fps (10.15 ms/f) 5.887 fps variability
@640x480
2639 frames 26.302 seconds 100.33 fps ( 9.97 ms/f) 5.587 fps variability
No real correlation here, either. I'm guessing that actual rendering is done entirely on the GPU, and since that's one of the few things done on the GPU for TF2, it always has top priority. Someone with an integrated card would probably experience better fps with low res.
baits me in csgo
could probably do well in main
December 17th
I don't know any of these people at all
If anyone is actually stupid enough to click on a link in a thread about a phishing link and type in their password, I don't know what the world is coming to. Just going to point out that clicking links in and of itself won't give anyone your password unless you have a really dumb browser, you would still have to manually type it into the fake site. Also, because the pages are usually complete copies of the legitimate ones, a lot of the links go back to the real steam site.
@Marxist
There have been a lot of attempts to test new maps, and tf2maps has done valve-backed mapping/modeling contests. What it would take to get that to be comp-centric would be a structured, prize-oriented contest for a competitive map, and then have the winner be decided by a second, prize-oriented tournament, played exclusively on said new maps. It would probably be the best way to get new maps into the competitive scene, and definitely the only way to get serious testing done on them.
always bet dbj
nice job mike
remove the spaces in the tag (inside the brackets)
If you're overclocking, you need to get the 3770k instead of a 3770, since that is the unlocked version.
I spent 2 hours fighting with a weed whacker, 2 hours watching lan, and the whole day putting off voluntary work.
I agree with hooky a lot, but the fedora-wearing liberal inside of me says that we need to give some level of power to the rest of the league, I think that every player who finishes the season on a team should have a vote, but weight the votes so higher divisions have more say (Invite players get 4 votes, Main gets 3, IM 2, Open 1). This could be used to allow invite/main players to effectively decide, but for the majority to veto it if necessary.
I'm reasonably certain that this can be done on any flat brush, it's a source engine bug. It can happen in a lot of different places, and (I think) is the same reason for suddenly getting stuck while surfing.