Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
Screen Type TN
Maximum Resolution 1920x1080p @240Hz
Viewing Angles 170° / 160°
Response Time (GTG) 1ms (OD Mode)
Brightness 400cd/m2
Contrast Ratio 1000:1
Dynamic Contrast Ratio 500,000:1
Number of Colors 16.7M Colors (RGB 8-bit)
Pixel Pitch 0.2832 x 0.2802 mm
EDIT: put the windows slider in the middle position...that means factor x1.0
But not anymore. Well, unless you're using a mouse 3-5 years old.
In short, if the sensor and the tech in the mouse is capable, dpi in the traditional sense - doesnt matter and simply acts as sensitivity to movement.
And that's where it gets interesting, because it then becomes a matter of delay for input to be done.
Thanks for the help, I can't put it exactly in the center, but I put it one notch higher instead of lower. I have the "enhanced" set in the off position.
I've got Quake set at 3, which is default also.
Also, polling is set for 1000/sec
Yea, I figure if I keep it set to say 400 or 800 I can simply hit my button to up the sensitivity, it's kinda nice having that right below my ability button, easy to remember when I need it. Also, I can switch to the railgun or machinegun while changing sensitivity and zoom with the mouse hand.
I would like to present something that isn't really thought of as much which is sensor divisors. Specifically, how is the sensor capable of "splitting" the reads to the dpi set in driver/firmware.
Here is the thing:
Many mouse offer you the opportunity to set dpi at intervals, be it 50 dpi increments, 100, 200 and so on. I've done my fair bit of testing on logitechs, cm's, microsoft, razer. What i usually always come back to is that it's better to stick to a divisor of the max dpi. and it must be able to doubled down.
Ie testing from my current mouse at max dpi, and then a odd dpi that just fits to make sensitivity ingame 1 work, vs again a third option to use a 4x divisor of max dpi. The odd dpi isnt nearly as "responsive" as either max dpi or a cleanly divided number of max dpi. So sensor issue.
I also found that with using maximum dpi, is the only real way to test if setting a higher mouse pitch, ie m_pitch ingame is going to offset pixel skipping or not. Some numbers work better then others there as well. But lowering the dpi of the mouse, would make a pitch number that doesnt work without pixel skipping on max dpi work, but upon further inspection, i've usually found that indeed that also can skip on even 400 dpi. They chose 0.022 yaw in all these years for a reason, it's a good minimal number that rounds off well.
Thanks for the insight DCR, I figured the multiples are there for a reason. Can you tell me how to get my DPI setting to work in game with QC? When I cycle it outside in the window environment, it works, but I can't cycle it inside Quake yet.
Your saying I should lower the QC in game sensitivity from it's default of 3 down to 1? then cycle the DPI up to an acceptable level?
I'm saying that barring the sensor is beyond perfect, max dpi dictates what divident you can use for lower dpi.
Ie for 12000 dpi mice, 6k, 3k, 1500, 750. Sure you can set f.ex 1150 dpi or 450, whatever - but it's not designed for it. It will have to do some interpolation of whatever it reads - off the scale - that isn't in line with the intended sensitivity of the mouse. Sensitivity=dpi=sensor.
There's a reason why certain mouse just comes with 400-800-1600-3200 steps, as example. Now - logitech has several mice with supposedly perfect sensors, but they still have to play by the same rules as other computer mouse sensors. Infact in order to fit a wide array of dpi steps, interpolation is indeed the key. There has been some mouse over the years that has done things differently, ie logitech dual optical, with 2 separate sensors, was pretty great for its time. Competition however leads to finding the best sensor for less cost. But ideally a sensor wouldnt just be 1 sensor, it would be a whole bunch of them - if the goal was to detect any movement whatsoever. But latency is also a factor, so it's back to 1 sensor again. Interpolation is also a latency step, tho it's practically done instant, it's still something to consider.
Alas ignoring whatever the maximum dpi is of the mouse and just setting your own preferred dpi, to fit a sensitivity setting in the game - while convinient and practical, it's not the most efficient for the mouse.
To complicate it a bit more, you should not set your sensitivity to make your dpi comfortable.
And vice versa for dpi to make ingame sensitivity comfortable.
Which sounds probably not logical. Until you take into context that your choices are not free to make. They're sort of already decided for you based on what mouse you're going to use and what sensor it has. How your hand is built, your reflexes and muscle memory should dictate how you should go about configuring your dpi. Basically your playing style, do you prefer long arm movements or not.
It IS possible that a custom dpi is useful in the event you measure 800 dpi across a distance is infact 850 dpi for your mouse. In which case you should return it, or try and see if 750 dpi will equal 800 dpi and its a firmware issue or whatever and the sensor is correct, but not the driver or whatever. However none of that is likely to happen with modern mice, practically any pwm 3300 and up is measuring perfectly that i've tested.
A modern computer mouse is practically it's own little computer these days with more and more powerful chips and sensors in them. And we treat computers with rules too in how they can be best configured for performance. We should not expect mice to just work flawlessly completely equal to performance, REGARDLESS of what dpi setting we set them to.
Hence, max dpi dictates everything. The maximum potential of your mouse.
If it fails at *max* dpi in some way, rma it. Most people tho probably ignore it out of simply "oh ♥♥♥♥ this is over 9000 dpi i cant use this". But exploring how well it can really perform can be educational and perhaps give an insight into yourself as a gamer, if nothing else.
that's right. still the resolution above 800 dpi is not the sensor actually being able to provide above 800 dpi but software that upscales the dpi which is not desirable. but let the expert talk you through it:
https://www.youtube.com/watch?v=lc7JVjcPzL0
https://docs.google.com/spreadsheets/d/e/2PACX-1vTexLm9MUWV3yqpzW7mDK_Ytkh0KcJNsZSNteIwY1Bqw_XrAD2HxE-swtPpDvyCYCnunmnNqrNdKSsf/pubhtml
Yea, I was actually looking at K1llsen on that earlier. 0.8142 deg/mm 44.22 cm/rev 400 2.350 0.022° 0.022° ? 1000 Hz 0 0.035 0 +0.014 sens/IPS ? 113° 635px@1080p ? ? G Pro 83g
Seeing that his Yaw Circumference is similar to what I am used,too, on the high side for most players, but not in the extreme. That's why I purchased his exact setup on mouse and surface. That and he's really good, maybe his setup will help me. He might use the wireless, but I still don't trust them, and won't fork out an extra $100 usd for that ♥♥♥♥. I got the mouse for $24 and mat for $13
i know what you mean. i go more in the direction of toxjq.
i am playing with the razer deathadder elite on a steelseries qck+, 800 dpi and 2.3 sens. yaw and pitch being 0.22.
sadly logitech stopped manufacturing quality products but continue to throw out plastic garbage for kids hands =(. mx 518 and all related mice were amazing back in the day.