geel really needs to pay people back their skins, it's not like he doesn't make enough to cover it from scrap.tf etc. It's his responsibility and he's been dodging it for way too long, we need to hold him to account for that.
Account Details | |
---|---|
SteamID64 | 76561198078214483 |
SteamID3 | [U:1:117948755] |
SteamID32 | STEAM_0:1:58974377 |
Country | Australia |
Signed Up | May 18, 2014 |
Last Posted | June 13, 2018 at 2:54 AM |
Posts | 932 (0.2 per day) |
Game Settings | |
---|---|
In-game Sensitivity | 2.5 |
Windows Sensitivity | |
Raw Input | 1 |
DPI |
400 |
Resolution |
|
Refresh Rate |
60 |
Hardware Peripherals | |
---|---|
Mouse | Logitech g502 |
Keyboard | |
Mousepad | QCK+ |
Headphones | |
Monitor |
yeah well someone didn't save the vod of the final which was actually close, eh bunneeezee? :>
real bracket you can actually access is here:
this isn't news?
I've added you, I can give you a list of useful aus servers and explain how competitive is run down here. The advice you'd get on tftv is usually na or euro-centric, so while it's helpful it's not always exactly correct or relevant to australian players. Also, I wouldn't lock yourself into being a medic main just yet, it's a rare player who can do well on combat classes with 200 hours in the game.
Toxi-C-LoudAlright but what exactly makes the i3 better than the fx-6?
The i3 has much better single threaded performance than the fx, which is all that matters in tf2, and it has enough cores (2 or more) for tf2 to run optimally with it. Dedicating more than two cores to tf2 will not increase your framerates at all, as the game hasn't been optimised for multithreading
Essentially, the fx has six cores that together probably possess a similar amount of power to the i3-6300's two (four with hyperthreading), but tf2 can only utilise the first two cores, so all that extra performance in the amd cpu is wasted, on this game at least.
Interp's a pretty personal thing, your network connection is different to other people's networks. That said, with a perfect connection with no dropouts and a very low ping, having cl_interp and cl_interp_ratio set at the lowest (15.2 ms) will lead to the most accurate hitboxes with the smallest delay possible. If your network drops even a few packets every now and then, increasing your interp becomes more worth it. I play on the highest possible for ozfortress servers (30ms iirc), because Australian internet is shit and I drop packets all the time.
don't bet, it's a losing proposition
yttriumtrashput it this way, when microsoft pulls their head out of their ass and makes w10 usable for basic gaming stuff (windowed TF2 is still laggy and basically unfixable after win7) you can switch later on with no costWDDM 2.0 (used in Windows 10) has fixed the issue that makes windowed games laggy. dwm now gives rendering priority to D3D applications. it works as well as it used to in 7 with dwm disabled.
except with additional input lag
eeeDoes requesting more packets (even if they're not available) cause the game to update more often? Even if you're getting 67 packets a second, if you're updating 128 times a second will you have less packet latency?
It's not possible as the game only refreshes 66.66 ticks per second, so even if it does send you more packets (which it shouldn't, it's unlikely valve would have coded it to waste their upload like that), they won't actually benefit you anyway, they'd just most likely be interpolation that your client could do anyway.
If you don't want to have to uninstall all their crappy apps (which includes the xbox live one that forces on vsync for every game) every single time there's a relatively major windows update (has happened 3 times for me over the past ~10 months), revert back to windows 7.
If you like playing games in windowed fullscreen mode, revert back to windows 7, because aero is forced on with win 8 and higher, and that adds input lag for windowed fullscreen.
If you're concerned about your privacy and don't have at least the pro version, ideally enterprise, revert back to windows 7.
If you don't like having annoying updates scheduled at stupid times without there being any way to put them off more than a week, and don't have pro+, again, revert back to windows 7.
If none of these apply, then you probably will be fine using windows 10, at least after a clean install to fix your problems.
I've also been having this issue, thanks a lot for that hud!
yeah ozfortress are jumping on the bandwagon as well: http://heroesleague.org/
pity the game's trash
Gemmellnessthe problem is that tf2 isn't csgo
correct, i guess?
and most mm games will end up being x-0 rolls.
might need a fact check on this one
cs has more randomness as to who wins fights at low levels
debatable, I suppose you're referring to the lower TTK and the higher chance of being shot in the back without having a chance to react? There's plenty of dumb shit that goes on in lower level pubs as well. I mean, if you or I were to play a 'silver' level TF2 mm game, it would be difficult for us to die very often, but do you really think Get_Right would have any more trouble in a silver cs game? I think there's probably plenty of randomness that can affect fights at lower levels.
and the lack of respawns and the economy means having longer games makes sense.
Playing a team game where you actually have to set everyone's roles at the start of every game and communicate together effectively also means that having longer games makes sense. As I said before, by the time you get the perma spy onto soldier or scout a bo3 is probably going to already be over. At least with a timelimit + windifference ruleset you have a chance to come back once he's stopped being quite as useless, and perhaps as a bonus he'll be able to learn some new things about the game or playing in a team from your shotcalling or whatever. There just isn't time for getting to know your teammates when most mm games are less than ten minutes long.