wait.. ARE YOU HIM??

👏😁

I'd say about 90%+ of the relative information is publicly available.. for people willing to take the time to look for it (unpack it). With most of it quite literally being among client-side. What remains is information that only money can provide a gateway to😅

Literally, via THEIR battery.xml: <?xml version="1.0" encoding="utf-8"?> <powermodel vid="0x46d" pid="0x40be"> <battery> <capacity watts_per_hour="1.173"/> </battery> <!-- Power Blocks --> <blocks default_unit="milliwatts" nominal_voltage="3.91"> <sensor model="jupiterev2" power="1.279"> <!-- Report Rate can override default value --> <report_rate hertz="8000" power="9.314" /> <report_rate hertz="4000" power="4.332" /> <report_rate hertz="2000" power="2.267" /> <report_rate hertz="1000" power="1.279" /> </sensor> <mcu model="nrf54h20" power="1.796"> <!-- Report Rate can override default value --> <report_rate hertz="8000" power="1.796" /> </mcu> <roller power="0" /> <hybrid power="0" /> <low_latency power="0" /> <analog type="switch" power="0.608"> <!-- Report Rate can override default value --> <report_rate hertz="8000" power="1.216" /> <report_rate hertz="4000" power="1.216" /> <report_rate hertz="2000" power="1.216" /> <report_rate hertz="1000" power="0.608" /> </analog> <haptics> <intensity level="5" power="0.440" /> <intensity level="4" power="0.311" /> <intensity level="3" power="0.189" /> <intensity level="2" power="0.152" /> <intensity level="1" power="0.126" /> <intensity level="0" power="0" /> </haptics> <report_rate> <interval milliseconds="0.125" power="19.928" /> <interval milliseconds="0.25" power="10.340" /> <interval milliseconds="0.5" power="8.543" /> <interval milliseconds="1" power="4.272" /> <interval milliseconds="2" power="2.136" /> <interval milliseconds="4" power="1.068" /> <interval milliseconds="8" power="0.534" /> </report_rate> </blocks> </powermodel> Logitech G can give their sensor, specifically what version, whatever name they want internally.. cause it helps them delegate future pushes to software/firmware updates, while not confusing the architecture that's needing the update. Externally is delegated by Rev. labels.. for later builds of the same mouse. As far as the MCU.. it doesn't make sense to label it as something else, internally. Cause it's the one component that isn't necessarily proprietary to the competition. Labeling it different externally (NxLOGI) makes sense, cause that aspect simply serves as an aesthetic. It's not periodically changed, with it being physical, until a new mouse is released.

LOL.. indeed it is! All it wants to do is simply make a connection!😅

Yes it does.. lol. Those depots, and the contents extracted from them, are inherently orchestrated by Logitech G. Of course it also takes Windows to do their part, with how and where it's extracted. The information taken directly from those depots, not to mention also containing the firmwares and the very data pipeline endpoints.. isn't just made up lol. The only aspect that prevents this is the devs encrypting that information through encoded Mojibake.

That's not the point. Own up to your mistake.. cause Accountability DOES matter. Transparency isn't a must when proprietary is a significant variable.. but can later on be faithfully revealed.

I only wish I would have kept all the hardware I owned since back then.. talk about nostalgia. Respect goes to you, for persevering👏😌

Lol.. so true. With cursive it almost doesn't matter even how badly it's written. Legibility is universal to all who can write in it🤭

You can't possibly believe that my post was in all seriousness.. And also, are you going to accept the fact that YOU made a bullshit claim about what MCU the NxLOGI was? And I'm not a fanboy. It's merely called Respect. Something you should learn to exert.

And OMG.. I just noticed you have a gif pfp. What a LEGEND, among few😮

There is a Sleep Mode, and it is interrupted by motion. But that doesn't separate the fact that.. no one should be leaving their mice on just because. And especially when turning off your PC.. like why leave the mouse on after doing so?

They could be NPC's, that somehow learned to navigate the peripheral space. 🤔 And that's actually scary.. cause WHO trained THEM⁉️

It can depend on where at on the button, that you're clicking. Also try it with RT On. All values at 1.

The travel distance to actuation, on the X3.. is half that. Or even less than half that, btw😉😉

🤷

They always ask, "What float?" ..and never "Where..?", or "How float?"🫵😟🫴

That's why they call it an "Improvement Test"🫵😉 (not a Latency *Measurement* Test)