M4TTThe g402 uses the am010 which is not as good as the big-name sensors such as the 3988,3310,3090,3366 and others
Why are those sensors better? Are you being general and vague because you don't know?
Account Details | |
---|---|
SteamID64 | 76561197993274972 |
SteamID3 | [U:1:33009244] |
SteamID32 | STEAM_0:0:16504622 |
Country | Australia |
Signed Up | September 20, 2012 |
Last Posted | January 3, 2016 at 3:13 AM |
Posts | 108 (0 per day) |
Game Settings | |
---|---|
In-game Sensitivity | 1.5 rinput |
Windows Sensitivity | 6/11 |
Raw Input | |
DPI |
800 |
Resolution |
1920x900 |
Refresh Rate |
144Hz |
Hardware Peripherals | |
---|---|
Mouse | Zowie ZA13 |
Keyboard | Ducky DK9087 G2 Pro w/PBT side printed caps |
Mousepad | Half of a Glorious PC Gaming Race 3XL |
Headphones | Beyerdynamic DT880 Pro |
Monitor | Asus VG248QE |
M4TTThe g402 uses the am010 which is not as good as the big-name sensors such as the 3988,3310,3090,3366 and others
Why are those sensors better? Are you being general and vague because you don't know?
Which qualities of the G402 sensor do you believe to be inferior?
It got a great review on prad.de. I don't think they tested the backlight strobing though
http://www.prad.de/new/monitore/test/2014/test-lg-24gm77-b.html
DigiSony GDM-FW900 has got to be the best CRT, though there are also a lot of other good ones out there, just keep an eye on craigslist and check the horizontal scanning frequency (kHz) of the ones available, most CRT monitors are pretty solid unless you want to have a good refresh rate on high resolutions, then you should look for certain specifications.
I have a Mitsubishi Diamond Pro 930sb which has a horizontal scanning frequency of 110kHz, and I use 1024x768 res @ 120hz, basically look out for the kHz, assuming you are looking for a CRT to get a better refresh rate and don't want to spend the money on a 120hz or better LCD. The better kHz, the better refresh rate.
Just look for Trinitron / Diamondtron CRTs, most that are over 20" should be fine.
Somd good brands would be mitsubishi, sony, toshiba, dell, iiyama, and viewsonic.
All excellent points, particularly paying attention to horizontal scanning rate. When I'm browsing CRTs, I plug their specs into this site to get an idea of maximum possible resolution at the maximum vertical refresh rate.
mat_showlowresimage and mat_fullbright are cheat protected
heres what it looks like with mat_viewportscale as well rofl
People on ESR are saying if you submit a ticket through the site and request cancellation, he gets to it very fast. I would try that before filing a dispute with paypal.
I'm the sad fan who kept believing and refreshed the page every day until the store finally went online (source). I'm probably the first order in the system. It sucks to have paid earlier and more than everyone who is getting their stuff already. Having said that, I'm still keeping my pre-order and waiting. The reason I followed this project so closely and pre-ordered instantly is because I want to support bst, as stupid as that sounds after everything thats happened. Even if it turns out to be absolute trash, it's worth more than its dollar value to me.
I'm really looking forward to what war has to say about it!
phraxedit: off topic but povo what are the "best" settings in terms of hz/DPI for the 2013 fk because 2300 DPI and half sens feels distinctly different to 1150 and normal and idk why
1000Hz was better than 500Hz on my 2013 FK. The 500Hz setting would have a 1ms period every 8 counts or so.
http://drok-radnik.com/junk/fk500hz.jpg
http://drok-radnik.com/junk/fk1000hz.jpg
I didn't do any extensive testing on the different CPI/Hz combinations and max speeds, and currently my 2013 internals are without a shell, because i put my FK1 internals in my FK13 shell, so I can't do anything with it at the moment. I do have an older Zowie AM-GS which probably has the same internals as the original FK (eg: red led, single cutout in bottom shell for sensor), so maybe I could test on that.
TL;DR - 500Hz and 2300 CPI gives the highest possible malfunction speed on the 2014 FK.
The MCU in the 2014 edition FK has clearly defined count caps at different hz/cpi combinations. 500Hz/2300CPI maxes out at 512 counts per polling period (2ms) equalling 2.82m/s assuming 2300cpi is the real cpi (its generally higher in practice on these mice). 1000Hz/2300CPI maxes out at 128 counts per polling period (1ms) equalling 1.41m/s (once again assuming 2300cpi). The other CPI steps exhibit a similar behaviour, but with even lower max speeds. The original FK did not have this problem at 1000Hz, and could hit over 350 counts per polling period.
You should be able to replicate these results
http://drok-radnik.com/junk/fk2014_500hz.jpg
http://drok-radnik.com/junk/fk2014_1khzcap.jpg
Hope this helps!
If you already own an old FK and FK1, you can make the FK2 yourself. All the internals are completely compatible
If you are looking for a heavy gaming mouse I don't think you'll have a problem finding one. This mouse is for people who want an alternative to the 100g+ bricks that gaming peripheral manufacturers are flooding the market with, because apparently light = entry level office grade mouse and heavy = premium product.
also remember you need to have mat_mipmaptextures set to 1 in-game
When I was shopping around for a new laptop in early 2013, there was no Windows equivalent to the retina MBP in terms of both specs and form factor. Closest you are going to find with similar weight and thickness is probably the Razer Blade, but even that makes Apple laptops look cost effective.
If you don't mind lugging around a brick I'm sure you'll have plenty of choice.
The main sensor is the AM010, same as g100s. If anything, its a customised 3050.
edit: image http://cdn.overclock.net/4/42/900x900px-LL-42dd277c_AWDsoGo.jpeg
By counts per millisecond I mean the total of the X/Y values that have been reported by the mouse. The range would be 0 to whatever the highest amount of counts you can produce from your mouse in 1ms. For example, this would be 0-256 in the case of the ir-led zowie mice at 500hz.
Polling rate fluctuations are handled probably as good as is possible. The driver knows how long it has been between updates and adjusts the speed calculation for acceleration accordingly. Source has been up for ages feel free to browse it, maybe it could be improved somehow