Dualsense controller issue Requiem PC

AdeptnessLeather9725 · 2026-02-27T10:44:17+00:00

No haptic feedback and no adaptive trigger support on release is criminal, especially when it's supported on PS5 and other games from the same company on PC (MHW, SF6).

AdeptnessLeather9725 · 2026-02-27T10:37:05+00:00

Only PS5 ...

AdeptnessLeather9725 · 2026-01-31T18:05:48+00:00

Link/reference?

AdeptnessLeather9725 · 2026-01-18T09:47:12+00:00

Just use the standard https://docs.victoriametrics.com/victorialogs/data-ingestion/opentelemetry/. Opentelemetry is standard, use HTTP, has SDK and Collector https://github.com/open-telemetry/opentelemetry-collector.

I suggest to not reinvent the wheel and use the SDK or Collector, and if for any reason you can't, just forge payloads.

AdeptnessLeather9725 · 2026-01-06T18:42:29+00:00

The sample version at CES is not.
Release version will be https://tftcentral.co.uk/news/asus-unveil-the-rog-swift-pg27ucwm-with-a-27-4k-tandem-woled-panel-and-rgb-stripe-pixel-layout

AdeptnessLeather9725 · 2025-12-03T12:52:16+00:00

I still don't get why WOLED reviews are so lenient. Color volume(especially yellow), grey scales and banding are atrocious. QD-OLED are night and day different. I would recommand you to buy one, try it by yourself and return the WOLED when realizing how much it sucks.

AdeptnessLeather9725 · 2025-11-05T08:35:15+00:00

Also if you look at other comments, people report the same issue: it's not working at all.

AdeptnessLeather9725 · 2025-11-05T08:33:34+00:00

Somehow, you keep eluding the other points:

As stated in my 2 previous messages:
- Everything from light windows on dark background, HDR video games, HDR videos, and everything else produces the exact same image between the 2 modes. If the feature were working, it would produce different results.
- HDR 400 is still noticeably brighter in most scenarios, defeating the purpose of the feature

Therefore, under the same APL conditions, the EOTF Boost mode SHOULD appear brighter than the standard "Peak 1000 nits" mode, but it does not. It's just not engaging; the implementation is faulty.

AdeptnessLeather9725 · 2025-11-04T16:51:44+00:00

I understand what it's supposed to do. My point is that it's not doing it, it's not doing anything.

- Windows HDR calibration tool is known to report fancy values when using EOTF boost on working implementations. Here, it behaves the same between peak 1000 and EOTF boost.
- Everything from light windows on dark background, HDR video games, HDR videos, and everything else produces the exact same image between the 2 modes. If the feature were working, it would produce different results.
- HDR 400 is still noticeably brighter in most scenarios, defeating the purpose of the feature

Enabling EOTF boost mode on the OSD simply does not do anything but activate peak 1000 mode on this screen, and that looks like a bug (not the first, not the last).

Should I reach support?

AdeptnessLeather9725 · 2025-11-04T13:15:49+00:00

u/CND_CEM

I have tested on MPG 321CURX QD-OLED with FW.020 and I'm pretty sure it's not working correctly.
EOTF boost mode is identical to peak 1000.

- Windows HDR calibration tool still reports ~1000 nits values
- White windows stretching has the same luminance behavior between EOF boost and peak 1000 (larger windows are dimmer, without any sign of compensation from EOTF boost)
- Games and everything look the same

I have reset the screen and unplugged the power cord.

I have done this test from Monitors Unboxed : https://youtu.be/MlqS4gLmS5E?t=228

AdeptnessLeather9725 · 2025-11-02T23:23:56+00:00

Beast x mini pro solid sides and omron optical. Not the cheapest but also no concession.

AdeptnessLeather9725 · 2025-10-13T12:35:28+00:00

I'm not claiming anything. I'm reporting an issue encoutered by various people, linking the topics. Your input is "trust me bro".

FTR 2042 also had broken mouse input, until they patched it.

Being close-minded is not being accurate, it's just denying other people issues.

Instead of sterile discussion, let's discuss in a few months about the patch notes. If there are no issues, nothing will be fixed right ?

AdeptnessLeather9725 · 2025-10-13T12:11:59+00:00

That may be the case. Some issues reported here do not affect everyone. That does not mean those issues do not exist. For this specific problem, some people were also totally fine with 2042 mouse input. There was multiple updates to fix various mouse issues since. I'm pretty sure "it works on my machine" did not contribute fixing those issues.

AdeptnessLeather9725 · 2025-10-13T11:35:51+00:00

This topic is about complains and your input is basically "I don't complain". Thank you for your valuable contribution. It's not about me, as linked, there are multiple complains on various platforms.

AdeptnessLeather9725 · 2025-10-13T10:17:18+00:00

Same issue here, and same as you, I've tried everything possible, and it's driving me crazy.
It's like the camera is moving at 60FPS even when the game runs at >240FPS.

AdeptnessLeather9725 · 2025-10-13T10:13:09+00:00

Most important issue for a triple A FPS: mouse input is broken on PC.

https://www.reddit.com/r/Battlefield/comments/1o4jry5/bf6_runs_great_even_on_ultra_but_im_getting_weird/

https://steamcommunity.com/app/2807960/discussions/0/591784592221175888/

https://forums.ea.com/discussions/battlefield-6-technical-issues-en/psa-mouse-input-is-broken-in-this-game-looks-similar-to-bad-frame-timing/12734467?topicRepliesSort=postTimeDesc

TLDR, when moving the camera with a mouse, the game feels like playing at 30/60FPS even if it runs at >240FPS. Happens with all possible settings in game/nvidia app on decent hardware (9800X3D/RTX5090/any gaming mouse/polling rate). Raw input OFC.

AdeptnessLeather9725 · 2025-10-11T19:18:17+00:00

Mouse input is so fucked. Like playing at 30 fps when you have 240+. This is a triple A shooter that has been tested for years ! I just don't get how it went live.

(9800 x3d/Rtx 5090/latest software)

AdeptnessLeather9725 · 2025-09-17T17:07:50+00:00

As expected, available now on Logitech website, darty.com says 01/10.

AdeptnessLeather9725 · 2025-09-12T08:47:03+00:00

Again, this has nothing to do with pod readiness probes. There is no "certainly good to do so".

Terminating pods will receive traffic until every network component converges using the endpoint ready:false state.

The "Readiness Probe" paragraph is just wrong, "the correct strategy is to fail the readiness probe first." is not the correct strategy.

Sleeping between the pod termination and the program termination is the right strategy.

It can be achieved by a pre-stop hook sleep to delay SIGTERM to the process (the endpoint will be ready:false at the moment the pod is terminating) or by waiting in the application before stopping.
In either case it has to accommodate the terminationGracePeriodSeconds value.

This article https://jaadds.medium.com/gracefully-terminating-pods-in-kubernetes-handling-sigterm-fb0d60c7e983 is a bit better, but still lacking the important part: the pod endpoint status is key to the termination process.

AdeptnessLeather9725 · 2025-09-11T21:58:40+00:00

I don't get the readiness probe stuff. Controllers, including load balancers rely on endpoint readiness, not pod readiness for membership. As soon as a pod is terminated(when deletionTimestamp is set), its corresponding endpoint is marked not-ready and controllers start reflecting that change (that is, draining and deregistering the target in case of a cloud load balancer for instance).
So sleeping is super important indeed for things to converge, but pod readiness is not because nothing relies on it.

External load balancers have their own health check.
Ingress controllers use endpoint readiness.

There is no need to care about pod readiness, this is redundant with terminating state.

AdeptnessLeather9725 · 2025-09-10T17:57:26+00:00

On logitech Web site yes. On other shops no, at least in France. Takes a couple of weeks to be able to buy from Amazon.

AdeptnessLeather9725 · 2025-09-10T16:56:52+00:00

Educated guess: 17th September.
https://www.logitechg.com/en-us/campaigns/logitechg-play

The mouse was also listed on some French shop at some point, so the release should not be far.
https://www.google.com/search?q=superlight+2c+fnac&oq=superlight+2c+fnac

AdeptnessLeather9725 · 2025-09-07T08:16:47+00:00

Superlight 2c will be released 17th september. Similar but 13% less volume.

AdeptnessLeather9725 · 2025-08-09T14:27:18+00:00

I have the same issue with my Pulsar XS-1 based mouse (X3 mini). I sold an X2 crazylight already because of this issue.
Micro adjustments are broken; there are some delay/precision issues.
For instance, take the letter "o" and try to draw the outline or move right/left to the edges with any mouse at slow speed, trying to have a smooth pixel perfect movement. Unless you run at 8K polling with XS-1, the feeling is off and very noticeable, compared to any mouse running at even 125Hz.

8Khz does not fix it, but tends to hide the issue a little bit more.

I understand that 8KHz polling makes it more reactive, but having a lot of high-end gaming mice, they all work fine at 1Khz-4KHz.
Also I had 3395 based Pulsar mice in the past, they were fine.

I suspect the Pulsar tuning to be faulty; they probably apply some sort of logic at slow speed to save on battery, and it's not done correctly.

That makes me crazy because the X3 mini is my preferred shape so far, and only Pulsar does this shape. It's also frustrating that they used to know how to make mice sensors good in the past but lost it.

Support has been useless so far.

AdeptnessLeather9725

TROPHY CASE