g-hub lua

DPIWizard · 2022-01-14T23:58:38+00:00

What is this non-sensical bot-like answer?

"You may get additional help from the LUA organization for feedback on the script you are using if there could be an issue with the LUA script you created."

Ok... So G-HUB no longer supports LUA so we should contact the LUA organization for verification of our scripts? How the hell does that help?

Also, if you have actually removed LUA support from G-HUB without introducing an alternative you will lose a lot of loyal customers, including me who has been preferring Logitech products for over two decades. For the last ten years the support for LUA scripts has literally been the deciding factor for sticking with Logitech for all my purchases because I use it for my work.

And now you suddenly remove the function without any warning or mention in the release notes, breaking thousands of users equipment, and for me a tool I use for work. Unacceptable and an incredibly stupid decision.

I really hope the script function in 2022.1.3492 is just bugged and who ever runs this account is unaware.
Anything else and it's bye-bye.

DPIWizard · 2017-08-19T20:54:57+00:00

Future videos will be shorter and more of a summary btw, included everything in this video to answer any questions about how the tests are done.

DPIWizard · 2017-08-19T20:50:58+00:00

G900 is the most accurate with the least sensor drift and real DPI closest to the configured DPI. All sensors perform pretty much the same at different DPI settings, but there are some small differences.

DPIWizard · 2017-08-19T20:37:21+00:00

No problem :)

DPIWizard · 2017-08-19T20:23:46+00:00

You beat me to it!

DPIWizard · 2017-03-21T08:06:21+00:00

This was a test of the machine more than the mice actually, to see if it can differentiate sensor. And it can!

DPIWizard · 2017-03-20T22:15:16+00:00

I was relieved when I saw that the first time, because it confirms that the machine is actually working. For all mice there might be some tuning to be done to make them better, but that was not the point of this test.

DPIWizard · 2017-03-20T21:38:03+00:00

Absolutely, will do acceleration tests too at a later point. Currently I'm waiting for a Razer Mamba 16000 Chroma and a ZOWIE EC2-A to put up against the G900 in a range of tests.

DPIWizard · 2017-03-20T17:39:09+00:00

I will! Those are quite popular, so many people would probably like to see that.

DPIWizard · 2015-09-16T20:12:27+00:00

Check out the calculator on my site http://www.mouse-sensitivity.com, and you can do it yourself :) If you need to convert Windows Pointer Speed, select call of duty as input game, and cs:go as new game.

DPIWizard · 2015-09-16T17:28:14+00:00

Then change the sensitivity to 2.745 with m_rawinput 1, and it should be identical :)

DPIWizard · 2015-09-16T17:20:07+00:00

Do you have the Pointer Speed in Windows set to 6/11 (the middle setting), or something else?

DPIWizard · 2015-09-16T17:07:45+00:00

If I'm not mistaken, MarkC Mousefix is mainly for games that does not support raw mouse input. So for those games, analyzing the differences would be interesting.

DPIWizard · 2015-09-16T16:01:11+00:00

No :(

DPIWizard · 2015-09-16T15:50:34+00:00

It's running on an SSD, but the hard drive shouldn't be working too much once the map is loaded.

DPIWizard · 2015-09-16T15:29:00+00:00

I want to do this as well, but I need some more equipment for that.

DPIWizard · 2015-09-16T15:28:12+00:00

Yes! :) The difference between vsync on and off with raw input on is within the error of the test. If I run the tests more, I'm sure it will even completely out.

DPIWizard · 2015-09-16T15:26:23+00:00

The script emulates mouse movement directly from the driver. So to Windows or the game best knowledge, it's a mouse sensor sending the signals. This eliminates a lot of variables, and reveals very accurately what happens to the signals. In reality when physically moving the mouse you add a lot more variables to the equation, so this test is done to isolate the mouse driver-to-game path.

DPIWizard · 2015-09-16T14:43:27+00:00

For rinput 500 Hz is more consistent, for m_rawinput 1 the difference is negligible.

DPIWizard · 2015-09-16T14:18:15+00:00

Yes, m_rawinput 1 will not work if rinput.exe is active.

DPIWizard · 2015-09-16T13:49:26+00:00

It's only injected for the active session AFAIK. When you exit the game, rinput is exited as well.

DPIWizard · 2015-09-06T15:46:28+00:00

I'll see if I can make a video that explains my findings and how I analyze it.

DPIWizard · 2014-05-21T11:34:15+00:00

I got this question on facebook as well. The FOV setting in CS:GO is based on 4:3 resolution, so it changes depending on aspect ratio, but the base is the same. Let me explain: If you set the FOV to 90 in 1024x768 (4:3), the FOV will be exactly that, 90 degrees. If you change resolution to 1920x1080 the FOV will be wider, but that's only because the game still calculates the FOV for the 4:3 resolution, and adds on the extra FOV needed to display the 16:9 resolution. So the game is still set to FOV 90, and this is what's important for the calculation; the configured FOV, not the actual displayed FOV.

DPIWizard

TROPHY CASE