alias +ins +inspect
alias -ins -inspect

bind MOUSE5 "r_drawviewmodel 1;+ins"

try

alias +ins "+inspect;r_drawviewmodel 1
alias -ins -inspect

bind mouse5 +ins

if anyone receives a EC1-A or EC2-A and dislikes it,

i'd gladly take it

i own one and definitely recommend it if you own a nice pair of headphones / earphones.
awesome piece of hardware with an insane price-to-quality ratio.
and in case of solid-state amplifiers like this, second-hand is basically like new.

@x3
i presume it uses the 120V power plug? might be worth mentioning :-)

if not a bug, then at least an oversight. surely they didn't mean to have the 20% bonus while disguising.

a lot of my maps look like this:

http://i.imgur.com/OpUXEPo.jpg

maps filled with pitch black textures.
i've also seen others have the same issue when inspecting the new skin-weapons (pitch black, no texture visible).

no idea what's causing it or how to fix it. started happening after the update.

done some testing: having mat_compressedtextures set to 0 will absolutely wreck my game. simply unplayable as soon as one of the new skins is rendered.

could someone else test if this is also the case for them..?

seems to be just me, but whenever one of those skins is rendered (can be behind walls) then my game just becomes unplayable. my fps drops with 80 or something and the game plays like it's on 5fps.

if even 1 player has a new skin, i have to leave the server.. simply unplayable whenever he takes it out.

a lot of maps have a ton of pitch black textures for me :/

and apparently it's the new skins that fuck my fps real hard
1 player on a server with one of them new skins means i have to leave. simply unplayable

how about cratered without an enemy getting credit?
how about cratered with credit? (soldier juggles and then he craters, for example)

i'm getting some weird fps crap. doesn't seem like it's map-related. for example my fps will just drop from ~200 to ~90, but the game feels like it's running on 5 fps.

and i know what 90 looks and feels like, and that shit does not look and feel like 90fps. there's something seriously broken. might be fixable by changing the value of a cvar, but who knows which one.
comparable to that botkiller bug that absolutely crippled fps, but this one is even worse

couldn't tell what was causing it though.
using dx9

didn't realise that contracts are class-specific challenges.
anyone got a seriously shitty contract?

i think i have hit two of the easiest ones..(?)
scout (kill demo, cap point)
sniper (scoped bodyshot kill, headshot kill)

(if only i wasn't terrible at sniper, though)

my fps is total shit in that new japanese map, pretty much unplayable. the payload one is fine

so you gotta get a ticket and a key? the ticket becomes a coin after you activate it, and you can turn in that coin to get a crate? then use the key on the crate?

phew

i'm not even halfway through the list and i've already seen so many cool changes :-)

+1 to valve. there are a lot of practical changes (in stead of based on theories they came up with themselves), obviously based on feedback of the community too.

can't wait to check this out later

you can get the player out of the game, but can you get the game out of the player?
#tf2victim