| Account Details | |
|---|---|
| SteamID64 | 76561198001693793 |
| SteamID3 | [U:1:41428065] |
| SteamID32 | STEAM_0:1:20714032 |
| Country | Northern Mariana Islands |
| Signed Up | August 21, 2012 |
| Last Posted | July 25, 2024 at 7:48 PM |
| Posts | 568 (0.1 per day) |
| Game Settings | |
|---|---|
| In-game Sensitivity | -frags don't matter |
| Windows Sensitivity | 6/11 |
| Raw Input | 1 |
DPI |
400 |
Resolution |
1920x1080 |
Refresh Rate |
|
| Hardware Peripherals | |
|---|---|
| Mouse | micro$oft intellimouse 3.0 |
| Keyboard | |
| Mousepad | |
| Headphones | |
| Monitor | |
hmm.. the naga is really good.. for mmo's
its not good for fps because of the weight.. and an optical sensor would be better than laser, ofc.
but it does what it was made for.
@op id get FK/FK2
they are slightly better than the current ec1/ec2 (the new ones might be nice, though)
no point in getting chroma over 2013 DA
g400s/aurora have issues
you can use an extreme widescreen resolution giving you a higher fov and stretch it vertically..
not that its worth crying about
probably something like cl_ejectbrass?
sile#1582
kt alliance - main is druid (boomy, os resto), priest (disc/shadow)
tich alliance - druid (boomy/resto)
tich horde - rogue, lock
pvp focused
im kind of burnt out at the moment to be honest tho
wow I didnt know you had that in you gj sheepy.
then get a roccat keyboard why are u asking us.
the ryos tkl. brown switches, get dampening rings if too loud
I mean matching your mouse to your keyboard is hella gay but whatever
Ungirthedso i just put "viewmodel_fov 360" in autoexec?
yes. if you want it for every class and every weapon. but you should probably use viewmodels for melee
if you want medic only put it in your medic.cfg (and put viewmodel_fov 90 or w/e in class.cfg)
if you want it for medigun only then you have to put it in your weapon binds
eg: bind x "slot2;viewmodel_fov 360" then have your other weapon binds
bind y "slot1;viewmodel_fov 0" and bind z "slot3;viewmodel_fov 90"
oktober, its a problem with the custom lens in the original and 2014 fk (but not the fk1).
theres a mod that will 100% fix it. (essentially open the mouse, take out the lens which is molded in two pieces, separate the small piece with a screwdriver, put the big piece back/reassemble the mouse)
kamo, I would assume this applies to the ec1 eVo CL as well but I haven't looked at it, I can open one and check if you want. oh and the darker the pad the better tracking you'll have but it's not really a fix
pvh, just fyi its worth trying hidusbf over zowies hz changer, it can potentially fix the smoothness problem. but I guess your mouse is in pieces at this point anyway
I can bhop better with 16 step wheel.
especially on 64tick matchmaking servers (the explanation for why is really retarded, but the fact remains)
so nah you're not the only one, but I doubt many people care
Driven by HASTE, drone, fanom, Phelon, syckness, cringe, BloodSire, warped, Abuser, Phaser, DJ_konfuzion, virulent, skeletoN, hocz
worst: kileR4fuNN really stands so far.. like just head and shoulders above the competition, its almost a boring answer. honorable mention to Sniper w/o Ammo, dellort
Mike, MIKE, other Mike, justin etc
it should work. item_whitelist.txt should be in your servers main tf folder and it will auto load.
if you put it in cfg then you can load it with:
rcon mp_tournament_whitelist "cfg/item_whitelist.txt"
make sure the server is in tournament mode or it wont work but im sure it is..
stabbyPixel skipping is observable. Set your DPI to 100 or whatever your mouse's lowest notch is, then pump up your in-game sensitivity so that your "real sensitivity" matches what it would be with the corresponding max DPI setting. Do this with both configurations: Shoot a wall, look at the bullet hole, then budge your mouse as little as possible to the right--does your crosshair move smoothly from one position to the other or does it jump?
Anyway, don't take it from me, I've already provided a source for you all on this:
http://www.teamliquid.net/forum/tech-support/333648-an-overview-of-mouse-technology
ctrl+f: pixel skipping
That article doesn't prove that you aim in 1 pixel intervals in a 3d game, and not less. Which is necessary for pixel skipping to be a relevant term. and your test is inconclusive for several reasons lol.
I would be interested on a nice source on this though.
stabbyI'm not sure why you're making a point to say that something "doesn't matter" when the alternative is either slightly inferior or the same. Better safe than sorry, no? Not that I'm at all uncertain about the existence of pixel skipping. I'm simply advising people on the best option available when they're deciding what to set their DPI and in-game sensitivity to.
More important to me, however, is the choppiness caused by excessive in-game sensitivity when moving my FOV--I certainly can notice it clearly with an in-game sensitivity of >4.0, myself. Maybe I'm just a little more sensitive to this stuff than you are, and I'm not the only one--this guide is made for everrrrrybodyyy :D
I'm saying the different feel and potential benefits of lower DPI is a lot more important. So raising your DPI to accommodate pixel skipping is stupid. It's not a better safe than sorry example.
no one is arguing that higher DPI isn't technically more precise. its more about does it matter and does it outweigh the negatives of raising the DPI, and in many cases I would say no. your choppiness is literally the more DPI argument all over again with a side of placebo.
I would recommend people simply use what DPI feels the best.
stabbywonderlandhow the sensor performs/feels at that DPI is way more important than 'avoiding pixel skipping'Well, yeah, I don't think I implied otherwise.
Pixel skipping exists, so why not avoid it if there are no benefits to alternative configurations? I also make the point that sensors tend to perform better at lower DPI's, mind you.
I'm simply informing people here, no reason to get hostile. I appreciate feedback, but maybe keep it, you know, relevant to something.
as far as I know you can aim at a sub-pixel level. so no I don't think pixel skipping exists.
either way, the effects of running too low DPI are simply not noticeable. people talk a lot about pixel skipping but its the MOAR DPI thing all over again, except instead of 5000DPI it's 1000DPI.
the 'benefit' is so slight that its just irrelevant and should not affect your choice of DPI or sensitivity to use.