Rainbow six siege xim apex issue?

[JonSnow]

I have come looking for answers. disclaimer: this is an issue i have been experiencing for months and have just been playing with it, and it regards rainbow six siege.

I currently run the latest firmware and manager for my xim apex, on smart translator 4.9. For a long time, i have been unable to deduce why my sensitivity feels so foreign and off. To put into perspective. I currently run this sensitivity and it feels EXTREMELY fast.
Vertical: 100
Horizontal: 100
Deadzones: 10, 10
In game ads: 68, 100, 101, 102
Xim apex sensitivity: 125 hip 40 ads, 800 dpi, default - also change between 32 hip 10 ads default 3200 dpi
Devices: logitech g403 hero
Royal kludge rk61
Dualshock 4

How could a sensitivity be so shaky and fast. At some point i will attempt to record a video depicting my predicament.  My old sensitivity used to be 60 hip and 25 ads. What could have possibly gone wrong. I know people will claim that because of siege and the ST updates that it could have changed the sensitivity so drastically but i have done my research and everyone plays on relativity similar sensitivities prior and post updates

I deduced that the issue could be either my xim apex internal software/structure being compromised, maybe i have changed my my plug in for my xim at some point, because i know that affects the registering of mouse movement (i have my mouse plugged into the slot with 1 dot, controller into slot with 3 dots and keyboard into slot with 2 dots) OR something completely different/foreign to me.

Is there a way to COMPLETELY reset the xim apex with no firmware, sort of like a troubleshoot solution? Could my xim apex be plugged in wrong? If not, what could the issue possibly be? Thank you for your time.

[antithesis]

What XIM APEX Response Rate are you running?
Which Sync setting are you using?
Have you tried to add Smoothing to remove jitter?

It's not likely to be failing software or hardware - XIMs are solid state devices that either work properly or not at all. Performance won't degrade over time, it'll simply stop working if defective.

It's possible that your Siege config has been corrupted (XIM will flash white if the FW or ST are corrupt), in which case setup a new one from scratch and don't import your old settings. This can happen if there's a version mismatch between a game config backup and a new Smart Translator.

Performing a Factory Reset using a firmware updater is the only way to reset an APEX. Again, if you're concerned about game config corruption, don't restore a backup.

[JonSnow]

I play on 1000 hz. I also use LAN to LAN for my remote play (lan on pc and another lan cable on my ps5). I have also tried what you stated. I reset to an older firm ware and then upgraded back to the most recent firmware. I also created a xim configuration from scratch, and the inconsistent and weird aim feel is still there. Not that it matters but i have been xim for around 3 years now. Also here is the trace log for a minute or 2 of t hunt just aiming and shooting.

[00969] Q[0] E[0] M[0] | S[0] C[29] T[0] I[0] R[  68,  73,1000] U[50] [14] *^
[00970] Q[0] E[0] M[0] | S[0] C[29] T[0] I[0] R[  70,  76,1000] U[50] [17] *^
[01348] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[  68,  76,1000] U[50] [20] *^
[01349] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 122, 332,1000] U[50] [15] *^
[01350] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 228, 348,1000] U[50] [29] *^
[01351] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 272, 334,1000] U[50] [28] *^
           UI[00] BT[00] HR[04] HT[03] TR[13] DV[01] TW[00] EN[00]
    T0[157] | [157] | [  4] [C-MK]
      P4[129] GK[128] GM[130]
[01352] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 256, 359,1000] U[50] [30] *^
[01353] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 259, 355,1000] U[49] [31] *^
[01354] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 287, 354,1000] U[50] [30] *^
[01355] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 248, 352,1000] U[50] [30] *^
[01356] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 271, 339,1000] U[50] [28] *^
           UI[00] BT[00] HR[04] HT[03] TR[18] DV[01] TW[00] EN[00]
    T0[157] | [157] | [  2] [C-MK]
      P4[132] GK[131] GM[130]
[01357] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 227, 354,1000] U[50] [28] *^
[01358] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 214, 348,1000] U[50] [27] *^
[01359] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 271, 338,1000] U[50] [29] *^
[01360] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 239, 363,1000] U[50] [30] *^
[01361] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 245, 373,1000] U[50] [26] *^
           UI[00] BT[00] HR[04] HT[03] TR[17] DV[01] TW[00] EN[00]
    T0[161] | [161] | [  4] [C-MK]
      P4[133] GK[132] GM[131]
[01362] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 222, 353,1000] U[50] [28] *^
[01363] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 273, 334,1000] U[50] [29] *^
[01364] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 249, 365,1000] U[50] [27] *^
[01365] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 238, 341,1000] U[50] [30] *^
[01366] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 245, 347,1000] U[50] [25] *^
           UI[00] BT[00] HR[04] HT[03] TR[17] DV[01] TW[00] EN[00]
    T0[159] | [159] | [  3] [C-MK]
      P4[133] GK[132] GM[130]
[01367] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 213, 355,1000] U[50] [28] *^
[01368] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 229, 346,1000] U[49] [25] *^
[01369] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 277, 358,1000] U[50] [29] *^
[01370] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 245, 357,1000] U[50] [31] *^
[01371] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 243, 350,1000] U[49] [25] *^
           UI[00] BT[00] HR[05] HT[03] TR[17] DV[01] TW[00] EN[00]
    T0[162] | [162] | [  4] [C-MK]
      P4[133] GK[132] GM[130]
[01372] Q[0] E[0] M[0] | S[0] C[43] T[0] I[0] R[ 273, 339,1000] U[50] [31] *^
[01373] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 286, 370,1000] U[50] [32] *^
[01374] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 244, 372,1000] U[50] [28] *^
[01375] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 246, 346,1000] U[50] [30] *^
[01376] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 275, 360,1000] U[50] [27] *^
           UI[00] BT[00] HR[04] HT[03] TR[18] DV[01] TW[00] EN[00]
    T0[157] | [157] | [  4] [C-MK]
      P4[132] GK[131] GM[130]
[01377] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 198, 370,1000] U[50] [27] *^
[01378] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 209, 347,1000] U[49] [24] *^
[01379] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 272, 334,1000] U[50] [30] *^
[01380] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 248, 367,1000] U[50] [30] *^
[01381] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 268, 353,1000] U[50] [28] *^
           UI[00] BT[00] HR[04] HT[03] TR[17] DV[01] TW[00] EN[00]
    T0[158] | [158] | [  5] [C-MK]
      P4[132] GK[132] GM[130]
[01382] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 219, 347,1000] U[50] [28] *^
[01383] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 283, 344,1000] U[50] [30] *^
[01384] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 293, 365,1000] U[50] [31] *^
[01385] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 225, 364,1000] U[50] [26] *^
[01386] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 230, 360,1000] U[50] [26] *^
           UI[00] BT[00] HR[04] HT[03] TR[18] DV[01] TW[00] EN[00]
    T0[162] | [162] | [  4] [C-MK]
      P4[134] GK[133] GM[135]
[01387] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 231, 341,1000] U[50] [29] *^
[01388] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[ 191, 344,1000] U[50] [21] *^
[01389] Q[0] E[0] M[0] | S[0] C[44] T[0] I[0] R[  70,  76,1000] U[50] [20] *^

[antithesis]

Are you using the screen connected to PS5 to view gameplay? Watching the video feed in the PS Remote Play app will be laggy.

Also, PS Remote Play runs at only 20 to 80Hz. So your 1000Hz input is mostly ignored and may feel delayed. You’re better off dropping your APEX Response Rate, or using a Beloader via LAN which should be capable of 1000Hz (depending on chipset of Beloader and LAN adapter).

That’d be my guess as to why it feels weird. If you’re using Sync Off with 1000Hz, you’ll also induce jitter more often than not and Sensitivity values will change. Try Sync Default instead.

[JonSnow]

I have been playing on remote play ever since it became a requirement to play xim on ps5. I only noticed this issue as of recently (the past 3 months). Ever since updating my ST from 4.8 to 4.9, I have been unable to fine tune and find a proper sensitivity. I also already play on default sync.

I have tried 125,250,500, and 1000 hz and 1000 hz still feels the best, but in regards to all those other polling rates, they dont really help. It is hard to explain but all sensitivies feel off for me. Maybe when I get the chance, I will record a video to put in perspective. On 3200 dpi with 10 ads on  default with the in game sensitivity above, with one mouse swipe, I can do almost a 360 while ads (this is on ps4 config on a ps5). Prior to this issue, I couldnt even do a 180 while adsing on 25 ads on default).

I dont see any white color or indicator that the xim is corrupted. I am just looking for maybe differing opinions or a potential answer.

[antithesis]

It might be how Remote Play interprets the output of XIM. Try connecting the XIM direct to the console and seeing if it behaves the same.

More likely, it may be that the turn speed limit was increased in one of the Siege updates, which was reflected in an ST update.

It could also simply be that the PS4 and PS5 look mechanics are different for Siege. A similar example is Destiny 2 has a much higher turn speed on Series X than Xbox One. That may not be fixable until XIM offers direct support for PS5. Or try setting the framerate in Siege on PS5 to 60FPS rather than 120FPS.

In short, your XIM is probably fine and it’ll be either Remote Play or a game update that makes the sensitivity feel different. If XIM was faulty, it wouldn’t work at all.

[Golden Amoda]

u jusf may be playing on updated Rotation