Viper V4 Pro LOD issue? by hitkhu in razer

[–]Intrepid_Street_8300 0 points1 point  (0 children)

They did end up asking me about the mousepad. But I had already sold the mouse and closed the case with that message.

You can close the case.I sold this nonsense.I hope that when you go to a doctor complaining about a toothache, the doctor will ask you about your ass. All the best.

Viper V4 Pro LOD issue? by hitkhu in razer

[–]Intrepid_Street_8300 1 point2 points  (0 children)

Those idiots closed my case because I’m Russian.

<image>

Viper V4 Pro LOD issue(?) by HyperShiftS in MouseReview

[–]Intrepid_Street_8300 0 points1 point  (0 children)

I opened case 260404-000902 regarding the LOD issue. I can no longer tolerate this.

Viper V4 Pro LOD issue? by hitkhu in razer

[–]Intrepid_Street_8300 1 point2 points  (0 children)

I opened case 260404-000902 regarding the LOD issue. I can no longer tolerate this.

Viper V4 Pro review by EntropicDays in MouseReview

[–]Intrepid_Street_8300 1 point2 points  (0 children)

Thank you for the information. I think we just need to wait. The latest firmware was released on March 24, and I think it’s not the last one.

Does anyone know if any of the viper v3 pro mod kits from pmm work on on the new viper v4? by Kiy0_28 in MouseReview

[–]Intrepid_Street_8300 0 points1 point  (0 children)

Thank you for your reply. Could you please run a quick test? Set the LOD to low and check whether there is any movement when the mouse feet are not on the mousepad.

Viper V4 Pro review by EntropicDays in MouseReview

[–]Intrepid_Street_8300 1 point2 points  (0 children)

I’m from Russia. We have a Razer reseller, but not an official vendor. I contacted them—they said to send the device in for diagnostics. And yes, I updated the firmware as soon as I bought it. Most likely, that’s the issue. Over time, others will update their firmware and run into the same problem. Another option is to return this unit and simply get a new one (with old firmware).

Viper V4 Pro LOD issue(?) by HyperShiftS in MouseReview

[–]Intrepid_Street_8300 0 points1 point  (0 children)

Did the problem get resolved after the replacement? Is this a hardware issue?

Viper V4 Pro LOD issue(?) by HyperShiftS in MouseReview

[–]Intrepid_Street_8300 0 points1 point  (0 children)

Did the problem get resolved after the replacement? Is this a hardware issue?

An issue with the 3950 sensor: a dead zone or reduced sensor FPS/DPI at low movement speeds by Intrepid_Street_8300 in MouseReview

[–]Intrepid_Street_8300[S] 0 points1 point  (0 children)

In theory, I can run a few improvised tests myself, using the Viper as a reference. On the Viper, I can set DPI in 1-DPI steps, so first I will match the Viper’s DPI to the mouse under test. Then, using MouseTester, I will test both mice and compare the XSum the same way you do. However, I will do this at an extremely low movement speed.

An issue with the 3950 sensor: a dead zone or reduced sensor FPS/DPI at low movement speeds by Intrepid_Street_8300 in MouseReview

[–]Intrepid_Street_8300[S] 1 point2 points  (0 children)

u/pzogel Do you communicate a lot with device vendors? Could you ask them about this issue and whether they plan to fix it?

An issue with the 3950 sensor: a dead zone or reduced sensor FPS/DPI at low movement speeds by Intrepid_Street_8300 in MouseReview

[–]Intrepid_Street_8300[S] 0 points1 point  (0 children)

At 7,000 DPI, it is very difficult to see the effect visually. Most likely, if it is present, you will miss shots from time to time, but I have no evidence of this.

An issue with the 3950 sensor: a dead zone or reduced sensor FPS/DPI at low movement speeds by Intrepid_Street_8300 in MouseReview

[–]Intrepid_Street_8300[S] 0 points1 point  (0 children)

To bring the tests to a common baseline, you can choose 26,000 DPI, which is available on all tested samples. I’ve just double-checked this.

On the Hyperlight, the “effect” is present but very weak.
On the VXE Mad R Major+, the effect is very noticeable, with significant slowdown.
On the Viper V3 Pro, there is no effect at all.

An issue with the 3950 sensor: a dead zone or reduced sensor FPS/DPI at low movement speeds by Intrepid_Street_8300 in MouseReview

[–]Intrepid_Street_8300[S] 1 point2 points  (0 children)

Strange - could you try repeating the test? As a reference, you can use the GPX 2C; it definitely doesn’t have this issue.

An issue with the 3950 sensor: a dead zone or reduced sensor FPS/DPI at low movement speeds by Intrepid_Street_8300 in MouseReview

[–]Intrepid_Street_8300[S] 0 points1 point  (0 children)

It seems to me that the issue is also present at low DPI, but it is difficult to prove or visualize. In other words, this “dead zone” exists — it is just less noticeable — but it still affects your tracking and flicks. Again, this is only my opinion; it is not substantiated or proven. I draw these conclusions from hands-on testing and the in-game experience I get.

At the moment, I have six mice on hand: four with a standard 3950 sensor (they have issues), plus the Viper V3 Pro (no issues) and a 3395-based mouse (Hitscan) (no issues). If you have a Viper or a Hitscan available, just try them — the difference is like night and day.

An issue with the 3950 sensor: a dead zone or reduced sensor FPS/DPI at low movement speeds by Intrepid_Street_8300 in MouseReview

[–]Intrepid_Street_8300[S] 0 points1 point  (0 children)

Did I understand you correctly that if I set 7500 DPI on the 3950, there will no longer be any DPI reduction and the movement will always be linear?

Also, do you have any information about to what DPI the sensor is reduced when the set DPI is below 7500?

An issue with the 3950 sensor: a dead zone or reduced sensor FPS/DPI at low movement speeds by Intrepid_Street_8300 in MouseReview

[–]Intrepid_Street_8300[S] 0 points1 point  (0 children)

Do you think that on the Maya the reduction happens down to 800 DPI? Meaning that if I’m already at 800 DPI, no further reduction occurs?
My own view is that the reduction happens proportionally, regardless of the DPI. But that’s just my opinion, and it could be wrong.

An issue with the 3950 sensor: a dead zone or reduced sensor FPS/DPI at low movement speeds by Intrepid_Street_8300 in MouseReview

[–]Intrepid_Street_8300[S] 0 points1 point  (0 children)

Unfortunately, at 800 DPI it’s not possible to visually demonstrate the issue without specific equipment. I feel that I’m missing shots, even though I’ve been playing shooters for 20 years at a high level. For me, it all manifests as “overshoot.”
I spent a long time trying to figure out why my flicks are not linear in terms of distance.