R6 Raw input TURN ON is bugged

[Saikokyari]

When turned on it makes the sens inconsistent, like overshoot under shoot ect, and with it off. Alot of other people are reporting that this is the case via tweeter, I'm having the same problem but In general im just reporting the problem here for possible hot fixes or something if its hardware related. I can post the tweeter post here if needed. 

[Saikokyari]

Its also worth noting that the new season just came out and compressed the game download, along with new servers and ect, and ubisoft is notorious for making mistakes and producing more bugs then fix with each update. 

[DPI Wizard]

I tested this a bit now, and it seems to be an issue with only the Vulkan version. Are you using Vulkan?

[Saikokyari]

Nope but my sens feels much better on raw input off then on, may just be a placebo effect tho. 

[Saikokyari]

I dont really have a way to test it myself.

[Saikokyari]

o heres the tweeter post https://twitter.com/search?q=raw input&src=typed_query

[DPI Wizard]

Ok, cause I could definitely see an issue with Raw input on in the Vulkan version, it dropped a lot of reports from the mouse. It might be that this issue also is on the regular version in certain cases, I'm not sure.

[Saikokyari]

Could any nividia settings effect it? like low latency mode ect

[DPI Wizard]

1 minute ago, Saikokyari said:

Could any nividia settings effect it? like low latency mode ect

Perhaps, I don't use that myself. And Vulkan have some built in support for it I think so it might be why it's working without Vulkan here.

[m1Lo.Q]

Am 2.12.2020 um 21:03 schrieb Saikokyari:

Could any nividia settings effect it? like low latency mode ect

Yes, I tested it myself and found out that when you turn Low Latency on, it affects your sensitivity negatively, or causes the CPU bug to occur.

[Saikokyari]

7 hours ago, m1Lo.Q said:

Yes, I tested it myself and found out that when you turn Low Latency on, it affects your sensitivity negatively, or causes the CPU bug to occur.

affects your sensitivity negatively in what way, because ik siege has nivida reflex and as of the moment i use that on + boost + nivida low latency. And im not getting the cpu bug to occur (as in no stutters ect) but im wondering more of the sens, like do you have a example or proof that it effects it? not doubting i just want to know how i can find out myself on my system

[fortunate reee]

1 hour ago, Saikokyari said:

affects your sensitivity negatively in what way, because ik siege has nivida reflex and as of the moment i use that on + boost + nivida low latency. And im not getting the cpu bug to occur (as in no stutters ect) but im wondering more of the sens, like do you have a example or proof that it effects it? not doubting i just want to know how i can find out myself on my system

the cpu bug (if we are speaking of stuttering as in 100%cpu bug which is a known issue in siege especially on intel chips i7 7700k 8700k etc *which to this day hasnt been fixed*  ) is more siege related  than it has to do with a single setting (2 links if you want to read )

the raw input thing in question has been fixed in the last patch

----

if any of you notice cpu based  sturreing id suggest using a limiter like rtss to cap your fps slightly above your monitors hz 144hz = 160fps cap

in my experience this gets rid of must stutters in games liek apex / siege at no significant input lag

----

on another note if you arent noticing stutters / issues there generally is no need to witchhunt potential bugs the whole windows optimisation stuff going around is 90% bogus

Edited July 15, 2021 by fortunate reee
added text references