dualshock-tools/dualshock-tools.github.io
1
0
Fork 0
mirror of https://github.com/dualshock-tools/dualshock-tools.github.io.git synced 2026-03-01 11:19:54 +03:00
Code Issues 9 Packages Projects Releases Wiki Activity

Calibration different since todays update #25

New Issue
Closed
opened 2026-02-10 18:43:30 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-10 18:43:30 +03:00
Owner
Copy Link

Originally created by @dackjaniels2001 on GitHub (Jan 19, 2025).

Following today's update the calibration of my ps5 dualsense sticks seems way off. I was getting around 6% error rate following calibration yesterday, it now sits at around 20% after calibrating. And the circularity test results in a square with rounded corners rather than a circle.
Is this a bug?

Thanks

Originally created by @dackjaniels2001 on GitHub (Jan 19, 2025). Following today's update the calibration of my ps5 dualsense sticks seems way off. I was getting around 6% error rate following calibration yesterday, it now sits at around 20% after calibrating. And the circularity test results in a square with rounded corners rather than a circle. Is this a bug? Thanks
OVERLORD commented 2026-02-10 18:43:32 +03:00
Author
Owner
Copy Link

@dualshock-tools commented on GitHub (Apr 4, 2025):

Hi, thank you for this report, can you post some screenshots of the issue?

@dualshock-tools commented on GitHub (Apr 4, 2025): Hi, thank you for this report, can you post some screenshots of the issue?
OVERLORD commented 2026-02-10 18:43:34 +03:00
Author
Owner
Copy Link

@dackjaniels2001 commented on GitHub (Apr 4, 2025):

I since found I had a damaged controller pcb so please ignore and I will
repost if it happens again.

On Fri, 4 Apr 2025, 10:22 dualshock-tools, @.***> wrote:

Hi, thank you for this report, can you post some screenshots of the issue?

—
Reply to this email directly, view it on GitHub
https://github.com/dualshock-tools/dualshock-tools.github.io/issues/58#issuecomment-2778053492,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA23BFNC3AKBQ4UVPCCJGQL2XZFN3AVCNFSM6AAAAABVOCOVACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZYGA2TGNBZGI
.
You are receiving this because you authored the thread.Message ID:
@.***
com>
[image: dualshock-tools]dualshock-tools left a comment
(dualshock-tools/dualshock-tools.github.io#58)
https://github.com/dualshock-tools/dualshock-tools.github.io/issues/58#issuecomment-2778053492

Hi, thank you for this report, can you post some screenshots of the issue?

—
Reply to this email directly, view it on GitHub
https://github.com/dualshock-tools/dualshock-tools.github.io/issues/58#issuecomment-2778053492,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA23BFNC3AKBQ4UVPCCJGQL2XZFN3AVCNFSM6AAAAABVOCOVACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZYGA2TGNBZGI
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

@dackjaniels2001 commented on GitHub (Apr 4, 2025): I since found I had a damaged controller pcb so please ignore and I will repost if it happens again. On Fri, 4 Apr 2025, 10:22 dualshock-tools, ***@***.***> wrote: > Hi, thank you for this report, can you post some screenshots of the issue? > > — > Reply to this email directly, view it on GitHub > <https://github.com/dualshock-tools/dualshock-tools.github.io/issues/58#issuecomment-2778053492>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA23BFNC3AKBQ4UVPCCJGQL2XZFN3AVCNFSM6AAAAABVOCOVACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZYGA2TGNBZGI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.*** > com> > [image: dualshock-tools]*dualshock-tools* left a comment > (dualshock-tools/dualshock-tools.github.io#58) > <https://github.com/dualshock-tools/dualshock-tools.github.io/issues/58#issuecomment-2778053492> > > Hi, thank you for this report, can you post some screenshots of the issue? > > — > Reply to this email directly, view it on GitHub > <https://github.com/dualshock-tools/dualshock-tools.github.io/issues/58#issuecomment-2778053492>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA23BFNC3AKBQ4UVPCCJGQL2XZFN3AVCNFSM6AAAAABVOCOVACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZYGA2TGNBZGI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.*** > com> >
OVERLORD commented 2026-02-10 18:43:35 +03:00
Author
Owner
Copy Link

@dualshock-tools commented on GitHub (Apr 11, 2025):

Hi, I'm sorry to hear that. The bug causing bad circularity test should be fixed now. If not, please open a thread on #help-desk on our Discord server! Thank you.

@dualshock-tools commented on GitHub (Apr 11, 2025): Hi, I'm sorry to hear that. The bug causing bad circularity test should be fixed now. If not, please open a thread on #help-desk on our Discord server! Thank you.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dualshock-tools/dualshock-tools.github.io#25
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?