[solved] Mouse XY Translators not working. Choppy input.

[J2Kbr]

Its better, yes. But the MWII XY converter is still unusable for me. It's way to fast, it stutters, X movement is faster than Y movement.

Are you on Xbox One? The WWII Input Translator was made for PS4 and, in my tests, was the one of the best, really like playing on PC. The XB1 possible have different settings.

If I change the curve parameters the git is too big for internal memory slot???

if you open the "curve data table", there is an icon on the top-left to round the point vlaues, which reduces the size of the Input Translator and allow store in the internal memory slot.

[cabal2k]

I'm on PS4, the first model. Mouse Model: Razer Death Adder Elite (no onboard memory, so direct connection to T2 is not really an option for me).

Are you sure these XY translation things works for other mouse models than your G502?

I try to get one G502 for testing over the weekend to narrow the problem. Maybe its T2 hardware related?
I don't think so because my XB1 wireless controller works like a charm

[J2Kbr]

yes, the input translator should work for all mice. I tested with a very cheap optical Logitech, Razer Orochi (5000dpi) and now with the G502 (12000DPI), all with same results after configuring the correct DPI on Gtuner IV.

as you are experiencing too much sensitivity, please try INCREASE the dpi on Gtuner, like double it. for example, if you have it set to 3200, change to 6400. this will reduce the sensitivity.

If you have change to test with the G502, please let us know the results. ;)

[cabal2k]

I narrowed the problem to the "polling rate" of the razer mouse and KM Capture.

In Gtuner/T2 a lower polling rate seems to increase the sensitivity.
If I set the polling rate to 1000hz, there is a jittering but sensitivity seems OK.

If I lower the polling rate (to my default of 125Hz), the sensitivity increases and there are stops in movement.

If I connect directly to T2, its playable. I don't know what polling rate is default for this mouse. Because Razer has no onboard memory I can't set the parameters and use with that in T2 diectly.

All screenshots shows a straight horizontal movement.

16000dpi, 125hz polling KM Capture:

Image3.jpg (125.42 KiB) Viewed 1507 times

16000dpi, 1000hz polling KM Capture:

Image2.jpg (200.91 KiB) Viewed 1507 times

Unknown dpi, unknown polling (I guess its 16000dpi and 1000hz by default) direct connect:

[cabal2k]

Razer Settings:

[Sillyasskid]

if your unsure of the mouses polling rate you can use this script to find out.

Code: Select all

#define REPORTS  intervals - 1000
main {
  uint32 elapsed, intervals;
  intervals++, elapsed += elapsed_time(); 
  if (elapsed >= 1000){ 
    printf("Reports sent last second: %d", REPORTS‬);
    intervals = elapsed = NULL;
  }
}

Move your mouse around and look at the number being printed out. Also don't have any other device/controller connected to the T2. Only connect the mouse for an accurate reading.

[cabal2k]

Thank you for the script!

it shows me, that if I disconnect the mouse, it keeps the last setting This helps a lot.

T2 reports 125 for 125hz, 500 for 500hz and 500 (!) for 1000hz.

Setting GTuner and mouse to 16000dpi and 500hz results in a good translation with direct connection to T2.

The only problem that lasts is the jittering with KM capture now.
Maybe you should consider USB Hub support on T2, so people could at least use some of these USB switches to switch KM between PC and T2.

[J2Kbr]

Your results are similar to what I have with KM Capture. The Titan Two requires at least 500Hz polling rate mice, 1000Hz is recommended for reduced latency, but the Titan Two will still read the mouse at 500Hz, as you noticed. The mouse movement is read as speed and not as absolute traveled distance. This is needed for the best translation to console stick. So a consistent report time rate is very important, as it is used to calculate the speed.

When using the KM Capture with the mouse at 1000Hz, it is playable?

[cabal2k]

When using the KM Capture with the mouse at 1000Hz, it is playable?

No, it is not playable. These spikes

Image1.png (12.27 KiB) Viewed 1479 times

are leading to stuttering. It looks like having to less frames per second if you move the mouse. Giving you a very bad feeling when playing games with lots of mouse (camera) movement.

I noticed if I set 1000hz the KM capture tool shows in "reports last send" numbers between 0 and 580. No more than 600.
If this is the same like with the script above as i suppose, shouldn't there be numbers near 1000 or maximum 500?

[J2Kbr]

I see. You are right, this issue is possible related with sending more than 500 reports/sec. A new Gtuner release is planned for the upcoming days, I will work on the KM Capture to improve the data report delivery to fix/minimize these unwanted transients.