Viper V4 Pro LOD issues?

I’ve noticed this. I have both Viper V3 Pro and the new Viper V4 Pro. I think either the FW or Synapse is bugged. Low LOD on both models are NOT the same. On the V4, the low LOD feels like the Viper V3’s Medium. 

I have both connected right now and they are obviously very different. Exact same feet and glass mousepad (CR005).

Okay cool. By chance do you use 8khz? or your system work okay with 8khz? Cause on VV4Pro, there’s this constant jitter timing outlier present at 8khz that’s not present with Viper V3 Pro. 4khz on Viper V4 Pro looks perfectly fine. It’s just there on the 8khz setting

I was using MouseTester just performing a swipe. Would figure the graph look clean/sharp at 8khz with the new FrameSync tech in it

EDIT: I just submitted a ticket to support. Hopefully there’ll be some news on it 

I have the same lod issues. Just got it out the box, installed the newest firmware update and set the lod to the lowest setting.

Now i load a game of cs, noticing me not being able to lift my mouse anymore without the mouse tracking the liftoff due to high ingame sens. 

Im not satisfied at all, i had no problems with the vv3 pro. 

VV3 Pro had minor LOD issues at launch as well. It got resolved possibly about 3 weeks after it was addressed. But the VV3Pro LOD issues were worse. I believe every time you placed your mouse down after resetting, it would momentarily not track LOL

VV4Pro LOD issue is that it is high and that’s it

Currently my support ticket is in the process of being “escalated” to a senior tech to run diagnostics (At least I really hope that is the case)

Here’s a short that I submitted to Razer support regarding the high LOD as well as me trying to demo the weird jitter timing issue on 8khz

^ Above are the weird outlier behavior for the 8khz which I want to believe it’s a jitter timing issue with the polling. It doesn’t exhibit this behavior on Viper V3 Pro. But the “look” of the outlier behaves similarly across all these swipe tests, so there IS something definitely going on. Got a balanced system as far as I’m aware of and haven’t seen anything go on with my system to indicate otherwise. Especially if my 9950x3D is idling during this …

All other polling rates 2khz and 4khz graphs look uniform like you would expect a typical Motion Sync would look like, or Frame Sync in the case of Viper V4 Pro. Hence why I feel there’s got to be something buggy going on, since it’s a new tech Razer has showcasing with their sensor implementation. Something new Razer hasn’t showcased since they first introduced Motion Sync with their Viper Ultimate and Viper V2 Pro

seriously? approval? what is this? and no carry over from forum of 2017 either

https://x.com/minliangtan/status/ [removed by moderator] 027900?sort_replies=recency

ur welcome/.

Same issue

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

Yeah just keep up with the replies. I know it’s lame but, we’re not “PRO” players, so it takes a bit for them to take it seriously. Since there’s more than 1 person actually inquiring about the same issues I have, it should make a difference

Razer maybe it's time to read the people's forum and help resolve the issue with the LOD sensor. I'm sure a lot of people have gathered there about this, don't you really give a damn about the community?

As long as it’s addressed or something is being said, I will happily take that.

If the high LOD thing is “how the mouse sensor is supposed to behave” I will shut my mouth and take it.

If the 8khz jitter polling outlier thing is unfortunately how its supposed to look like for now, I will gladly take that.

If the LED feature on the dongle only works by changing colors when switching DPI only when Synapse4  (non-web) is running … I will take that …

^This is a new bug I found btw. Tested the DeathAdder V4 Pro, and it doesn’t exhibit this at all. When I change DPI’s the LED on both the mouse and dongle change to the corresponding color

Any ways … I will GLADLY accept any feedback that all these things that are going on are just how the Viper V4 Pro is” just how it is” and I think that would be enough. Granted it is at least being quoted from a legitimate Razer Test Engineer to validate these claims.

I have purchased 3 black Viper V4 Pros and 2 white Viper V4 Pros. All of which exhibit this. I don’t need an RMA, I just wish to improve/fix something that’s going on with the esteemed Viper V4 Pro.

I am honestly thinking that ‘might’ be the case. I was beginning to consider since this is a very very new sensor I was thinking that maybe the standards for this implementation might have changed. In my recent support ticket, I have asked if they could provide me the value representations of low, medium, and high LOD values in mm. Including what asymmetric for 2 lod and 1 landing distance would represent.

8kHz debacle has been resolved on my case. It wasn’t necessarily an issue before but utilizing a fullscreen app in combination with MouseTester provided a more expected representation of Razers’ 8khz polling graph. It wasn’t needed in the past when I performed the test or Viper V3 Pro but something in regards to the OS scheduling behavior treated that MouseTester app in combination with background processes causing the graph to create an arch. 

Other issue now that I have discovered is that the DPI feature for the Dongle doesn’t work. It appears the connection quality and battery feature seems to work but the DPI doesn’t work when changing DPI values on the mouse. The LED’s on the mouse change color so it’s technically fine. It’s just that the DeathAdder V4 Pro dongle doesn’t have that problem, especially when not running Synapse 4.

With Synapse 4, Viper V4 Pro DPI led on dongle does change colors accurately. But when you close it, it doesn’t work. So that just kind of bothers me a little but doesn’t really affect the performance of the mouse. Just more of a QoL thing