Ping wheel is taking longer to come up and requires more mouse movement

Peast

New member
Lately, my ping wheel has been requiring me to move my mouse much further than it used to to trigger voice lines. This messes with my muscle memory a lot and also just feels worse, I want to be able to flick to the option I want quickly. On top of this, I just had a game where every time I pressed mouse3, the ping wheel would take a good quarter second to appear, which felt even worse. I don't think this is intentional and it doesn't feel very good, communication should be quick and snappy.
 
I wanted to add on to this; the ping wheel seems much less responsive now due to the new UI animations. I have also had problems doing basic enemy pings on occasion, as it feels much easier to accidentally say "Good job" rather than pinging a character location/to attack. (I have also had times where I have pinged myself to be careful when trying to ping something else.) The worst culprit seems to be trying to hit the top of the ping wheel, as it feels like it takes way more effort to reach it now, and results in leaving a basic ping in front of me. My suggestion for the ping wheel would be to hasten the animation starting on middle mouse press, as well as allowing the ping pointer to move at full speed before the UI is completely visible.
 
Seconding this. Much harder to communicate on certain occasions, especially in lower-ranked lobbies where microphone communication is less common.
 
---
Inquiry:
Does disabling "Mouse acceleration / smoothing / Enhance pointer precision" actually function as a workaround. Or did I for one encounter a placebo-effect / hallucination?

Want to add the speed-down is same regardless if the ping-button is a keuboard-binding or a mouse-button
( E.G. "Mouse-4" )

Also linking to my own thread also reporting the same issue
( did use "chat wheel" as search query instead of "ping wheel" hence semi-accidental duplicate ):
https://forums.playdeadlock.com/threads/chat-wheel-pointer-dpi-speed-dipped-to-minimum.103933/
Edit: My thread has some responses from Valve-folks. A summary is they're looking through the changes which caused this issue.
---
 
Last edited:
---
Inquiry:
Does disabling "Mouse acceleration / smoothing / Enhance pointer precision" actually function as a workaround. Or did I for one encounter a placebo-effect / hallucination?
---
Just to add my two cents in, i dont think it functions as a workaround. I've never had the "enhance pointer precision" toggled on in windows and the ping wheel is still INCREDIBLY sluggish.
 
Some people report sluggish movement while others report accidental activation.

Could y'all let me know what DPI your mouse is running?
 
Some people report sluggish movement while others report accidental activation.

Could y'all let me know what DPI your mouse is running?
i use 4000 DPI while ingame sens is about 1.17

For me i have not noticed sluggish movement

I did Had the instant accidental activation (refer here) but this has been changed and now i do have ocasional accidental activation, specially if spamming and looking around but minor issue for me.

I do have this and other find it annoying it. See here: https://forums.playdeadlock.com/thr...w-some-update-fix-caused-longer-delay.103318/
 
Some people report sluggish movement while others report accidental activation.

Could y'all let me know what DPI your mouse is running?
As of recent patch (celeste release and maybe some hotfix) the accidental activation problem for me has subsided, the sluggishness is somewhat fixed but it is still slower than usual

I use 5.6k DPI with 0.48 ingame sens. also have the y-scaling to 0.90.

I feel like the sluggishness comes from the green "cursor" thing where you need to actually move the cursor to the wheel option instead of the old mouse movement selection. This also becomes a problem when you double back on your decision.

example is if you want to say "going in!" on the top of the wheel the you want to say "nevermind" instead on the bottom of the wheel, the cursor has to move all the way to the bottom part of the wheel instead of instantly selecting the bottom of the wheel when you move your mouse downwards.

double example is when calling out lanes. when the "headed to lane..." option is hovered and the three lane command shows, usually by moving the mouse up and down you could select which command you want, but now you have to move the cursor to the newly shown command. Currently If you dont move the cursor to the actual lane option, you might select the adjacent command instead.
 
As of recent patch (celeste release and maybe some hotfix) the accidental activation problem for me has subsided, the sluggishness is somewhat fixed but it is still slower than usual

I use 5.6k DPI with 0.48 ingame sens. also have the y-scaling to 0.90.

I feel like the sluggishness comes from the green "cursor" thing where you need to actually move the cursor to the wheel option instead of the old mouse movement selection. This also becomes a problem when you double back on your decision.

example is if you want to say "going in!" on the top of the wheel the you want to say "nevermind" instead on the bottom of the wheel, the cursor has to move all the way to the bottom part of the wheel instead of instantly selecting the bottom of the wheel when you move your mouse downwards.

double example is when calling out lanes. when the "headed to lane..." option is hovered and the three lane command shows, usually by moving the mouse up and down you could select which command you want, but now you have to move the cursor to the newly shown command. Currently If you dont move the cursor to the actual lane option, you might select the adjacent command instead.
yeah, this is the big hiccup for me.
 
Some people report sluggish movement while others report accidental activation.

Could y'all let me know what DPI your mouse is running?
1600 dpi. 1.25 in game sens. way harder to activate than before the old gods update.
I assume the main intention was to lock the cam while you are in the ping wheel, which I agree is a good idea, but there are a few problems:
1. The ping button seemingly needs to be held for longer now, or at just longer than I want, to switch from the normal ping to the ping wheel. -> Ideally this time window should be adjustable;
2. I might be wrong, but i think it used to input buffer the direction of the wheel you want to choose, i.e. you could move your mouse in the direction you want even before the ping wheel activated, while holding the ping button. All you needed to wait for was the time window for the ping wheel activation and the choice was already made. Even if it didn't actually use to work like that, I wish it did, since it'd be much smoother;
3. (???) a bug(?) that arises from 2 is that it will sometime bounce your choice in the opposite direction -> Not sure here since its inconsistent, might be just deeply ingrained muscle memory from the old system, where I needed to readjust the cam after using the ping wheel. added this just in case other people, more importantly newer or returning players, can confirm.
EDIT: i did a little test with different dpi and didnt seem to be the issue here, the ping wheel reticle speed was changing accordingly
 
I believe I found the problem, and have submitted a fix, and look forward to any other feedback.

Historically, we would re-center the cursor when the ping button was pressed, but not when the wheel opened - it opens after a very small delay, or due to significant mouse deflection, after pressing the ping button.

Recently, (for complicated reasons) the cursor would be reset _again_ just as the wheel was opened, throwing away the mouse movement _since_ ping was pressed. I believe this was causing the perceived sluggishness.
 
I believe I found the problem, and have submitted a fix, and look forward to any other feedback.

Historically, we would re-center the cursor when the ping button was pressed, but not when the wheel opened - it opens after a very small delay, or due to significant mouse deflection, after pressing the ping button.

Recently, (for complicated reasons) the cursor would be reset _again_ just as the wheel was opened, throwing away the mouse movement _since_ ping was pressed. I believe this was causing the perceived sluggishness.
thank you for the communication and clarity, hopefully its fixed!!
 
Back
Top