you guys did great!
good game, everyone. let's all have fun for the rest of the season. :)

AHAHAHAAHAHAHAHAHAAHAHAHAhAHAHAHAAHAHA

proto

knock knock

+1
sleeping is doing a great job
i'm currently doing the weakest on the team, if anything.

on topic, everyone in open is doing great!!! keep up the good work!!!

good scout. fun to MGE.

you are all doing great. keep up the good work!

nice pro gamers

hi guys here is a montage of last week
i'm looking forward to more!!!
https://www.youtube.com/watch?v=FMfJ44JMMTo

my first two seasons were in steel and silver, then i hopped over to open last season and now i'm in IM.
i attempted my first open scrims when i was in silver, and i don't think we even won a single one until the very end of our silver playoffs (against a low open team at that). however, they also provided us with the absolute best feedback as to the efficiency of our strategies & DM abilities.

i'd honestly make the transition over to open as soon as possible, as you'll improve much quicker with esea than UGC. i committed just as much time into tf2 when i was in UGC, so it didn't feel like i had to commit more time.

also, the transition to open was much easier after i finished silver because i spent much more time MGEing than i ever did before. honestly, nailing the fundamentals of combat will allow you to tackle strategies much more efficiently than only trying to scrim. you can get away with doing so many things in UGC that are quickly rendered impossible against coordinated teams that understand and respect combat momentum and pressure.

basically, just put a hundred hours or so into MGE and you should be just fine to start tackling open. if you don't feel confident with your DM abilities, try it anyway so you can properly gauge your deficiencies.

EDIT: cl_hud_minmode 1 is the culprit; hud_minmode causes the vpk's to incorrectly load (or not load at all) on anything higher than sv_pure 0. if you load your hud normally and then apply hud_minmode, the vpk's will still work until you restart the game. this seems to be the easiest statement i can make, but i'm interested as to why keeping dxlevel in my launch options while hud_minmode is enabled allows the vpks to work.

just confirmed that it clearly is a config issue. backing up my config folder, creating a new one by launching the game fresh again, specifying the dxlevel, and then removing the dxlevel from the launch options still allows the vpks (mainly, particle_removal) to work in sv_pure 1 (haven't tried higher yet). i just need to figure out what convar (or combination of convars) is causing the vpks to improperly load past sv_pure 0.

for the clean tf2 vpks to work in sv_pure 1 or higher, i need to keep my -dxlevel specified in my launch options. this doesn't really make a lot of sense, but i can clearly see one of the effects of specifying your dxlevel is that alt-tabbing back INTO tf2 is extremely delayed, with the screen appearing black for a bit before anything happens. i don't mean to imply that correlation proves causation, but there clearly is a connection with the launch option and my config settings.

my custom folder only has your vpk's in it right now. if necessary, i'd be glad to post my autoconfig and config files.
i've tried setting the read/write permissions for the folder & its files on and off in different combinations, but none of them seem to help. to reiterate, the only thing that seems to allow my clean tf2 vpks to stick in sv_pure 1 or higher is by keeping the dxlevel specified in the launch options.

in essence, i'm sure specifying dx_level also causes similar postconditions as to specifying autoconfig, but i'm not sure where the fault with my config lies.

what could be going on?

hi guys here is me playing heavy
https://www.youtube.com/watch?v=g_Veh81c1lQ

u better watch out this week

we're not matched up against a team, as #26 and #46 supposedly haven't played yet
PLEASE DON'T MAKE US LOSE OUR COLLATERAL, LOSER's BRACKET!!!

hi guys i made a frag compilation of our esea matches
https://www.youtube.com/watch?v=z6f5tH6CuBw