stabby
Account Details
SteamID64 76561197975080641
SteamID3 [U:1:14814913]
SteamID32 STEAM_0:1:7407456
Country United States
Signed Up March 21, 2013
Last Posted May 16, 2018 at 5:40 PM
Posts 274 (0.1 per day)
Game Settings
In-game Sensitivity
Windows Sensitivity
Raw Input  
DPI
 
Resolution
 
Refresh Rate
 
Hardware Peripherals
Mouse  
Keyboard  
Mousepad  
Headphones  
Monitor  
1 ⋅⋅ 10 11 12 13 14 15 16 ⋅⋅ 19
#7 Stabby's stream graphics in Q/A Help

It's my config (has filterlightmaps fix) + the LOD tweak. The reddit thread should have you covered.

posted about 9 years ago
#22 Thoughts on the G502 in Hardware

g402, actually. Not really a g400 variant.

posted about 9 years ago
#16 Thoughts on the G502 in Hardware
iridescentFUZZstabbyIt has excessive smoothing. As does the g400s ;)
The hell? I thought accel and prediction and skipping were the only things one had to avoid in a mouse sensor.

This guide covers the stuff to worry about concerning a sensor, and gives some nice mini-reviews of mice with quality sensors:

http://geekhack.org/index.php?topic=56240.0

posted about 9 years ago
#15 Thoughts on the G502 in Hardware

Yeah, I'm saying the DA 2013 and g400s have smoothing noticeable to a large number of people. The g502 has none, so that's a plus.

posted about 9 years ago
#12 Thoughts on the G502 in Hardware
hooliHow is the new DA sensor inferior? I have one as a backup in case my g400s dies.

It has excessive smoothing. As does the g400s ;)

posted about 9 years ago
#3 Thoughts on the G502 in Hardware

Pros:
-The sensor is the best there is--perfect at all dpi levels (which come in increments of 50!)--I find it noticeably superior to the Zowie Evo 2 CL I am switching from. It won't malfunction at any possible speed, smallest liftoff distance in the market, no jitter at any DPI, no smoothing like in most other new optical mice...truly a 100% perfect sensor.
-Nice buttons. On the sensitive side, clicky, more or less well-placed (the "sniper button" is a bit hard to reach, as are the DPI buttons, even with big hands, but mouse4/5 are perfect)
-Very ergonomic. Shape keeps thumb and pinky from dragging on pad.
-Good software (macro support, all buttons reprogrammable).

Cons:
-The clunky metal mouse wheel kind of sucks, although it does have side and free scroll. Not enough steps, too much play, too heavy, unsatisfying mushy feedback on rotations (no "click").
-It is very very heavy. Like, unwieldy heavy.
There are extra weights which can be placed to adjust the weight distribution...so if you like heft you're in luck, otherwise the nice feature is wasted.

If you like heavier mice and the mouse wheel isn't important to you for gaming, grab it. If not, the Roccat Kone Pure Military just came out...Should be very good. The Zowie FK1 is another good option if you have an ambidextrous grip.

Avoid Razer...new DA has an inferior sensor.

I wish the g402 were out already :(

posted about 9 years ago
#9 Anyone tried tweaking flip queue size/prerendered in TF2 General Discussion
BLoodSireOn a related note, I believe ATI Tray Tools is severely outdated, and flip queue does not appear to be available in CCC. Sorry AMD users :{

There's still RadeonPro.

posted about 9 years ago
#4 Anyone tried tweaking flip queue size/prerendered in TF2 General Discussion

Right :)

posted about 9 years ago
#1 Anyone tried tweaking flip queue size/prerendered in TF2 General Discussion

Apparently decreasing this below "3" in your GPU controls can reduce input lag and/or alleviate stuttering, but can decrease FPS and/or cause stuttering.

Anyone played with it? I'm having good results with "2"--"1" gave me microstuttering.

posted about 9 years ago
#33 Increasing DPI vs. increasing in-game sensitivity in Q/A Help

I'm sure some googling should turn up an answer...look up the native a steps for the sensor if you can't find them for the specific mouse.

posted about 9 years ago
#29 Increasing DPI vs. increasing in-game sensitivity in Q/A Help
CrizzlstabbySetsulstabbysnipThat's assuming 90° horizontal fov.
Using fov_desired 90 with a 16:9 aspect ratio will give you 106.26° horizontal fov in the source engine. The correct maximum sensitivity is therefore 3.61714.
For fov_desired 75 it's 2.77561.

hfov = fov_desired for 4:3 aspect ratio.
If you're using values other than 90 for fov_desired on 16:9 or have a different aspect ratio like 16:10 or glorious 21:9 use http://www.casualhacks.net/Source-FOV-calculator.html to calculate your real fov.
Nice, thank you.

EDIT: Pretty sure I just mathed wrong.

Wait...did you? I'm bad at mathing :(

posted about 9 years ago
#22 Increasing DPI vs. increasing in-game sensitivity in Q/A Help
SetsulstabbyIn-game sensitivity is a multiplier. It takes the counts of movement recorded by mouse and multiplies it to determine the final distance your cursor moves.

DPI or CPI = Dots/Counts per inch. CPI basically is the number of units the mouse splits an inch into. So if you have a CPI of "1,000" your mouse records 1,000 movement units, and tells the cursor to move 1,000 pixels. So, using an in-game sensitivity of "1.0" and a CPI of "400", if you move your mouse one inch your view will move 400 pixels on your display.

If your sensitivity is too high (above 2.7128 for 1920x1080 displays), you will be unable to move your view by one pixel at a time, even with the slightest movement--this is called "pixel skipping".

Do note that higher DPI is not always better. Certain mice have "native" DPI steps which you should use. Most mice also get tracking errors at lower speeds with higher DPI's. And as was mentioned, on multimonitor displays it can cause your cursor to fly onto the other screen out of game (this can be rectified with an .exe called "CursorLock" btw).

So...use the in-game sensitivity that will allow you to use a native DPI step while keeping your in-game under 2.7128 (for other resolutions, use this to calculate the number).
That's assuming 90° horizontal fov.
Using fov_desired 90 with a 16:9 aspect ratio will give you 106.26° horizontal fov in the source engine. The correct maximum sensitivity is therefore 3.61714.
For fov_desired 75 it's 2.77561.

hfov = fov_desired for 4:3 aspect ratio.
If you're using values other than 90 for fov_desired on 16:9 or have a different aspect ratio like 16:10 or glorious 21:9 use http://www.casualhacks.net/Source-FOV-calculator.html to calculate your real fov.

Nice, thank you.

posted about 9 years ago
#15 Increasing DPI vs. increasing in-game sensitivity in Q/A Help
rakzbrbr
in the rest if you use high dpi you should use higher resolution
thats why they are made for.. and for gaming brands make marketing.

Again, high DPI is not necessarily better. Most mice get tracking errors at lower speeds at higher DPI's.

posted about 9 years ago
#14 Increasing DPI vs. increasing in-game sensitivity in Q/A Help
DudeMartinstabbyWhat's the mouse?

The native CPI is probably a multiple of a divisible of the max DPI. Don't go with something your max DPI can't be evenly divided by. Keep your DPI as low as you can while keeping sensitivity below 2.7128, I'd recommend.

Why 2.7128? I understand that in your example you defined that at 400 CPI, my cursor would move 400 pixels as a result of one inch of physical mouse movement. However, I am not sure how you derived the constant 2.7128 for 1080p (which is the resolution I play at, by the way).

I derived it from the "useful DPI" formula found here: http://www.funender.com/quake/mouse/index.html

posted about 9 years ago
#11 Increasing DPI vs. increasing in-game sensitivity in Q/A Help

What's the mouse?

The native CPI is probably a multiple of a divisible of the max DPI. Don't go with something your max DPI can't be evenly divided by. Keep your DPI as low as you can while keeping sensitivity below 2.7128, I'd recommend.

posted about 9 years ago
1 ⋅⋅ 10 11 12 13 14 15 16 ⋅⋅ 19