Red Dead Redemption 2

I'm still a little confused on converting... sorry if this isn't the right place to post (please move if so).

trying to convert from Aim Hero  3 sens, 1600 dpi, 63 FOV (~95 Horizontal)

changing to 400 dpi for RDR since it seemingly cant convert at 1600.  I play on max FOV in RDR.  The settings I'm getting are 9 lookspeed and 2 aim for third person.  But it feels totally different.  

2 минуты назад, xPeoplesChamp сказал:

I'm still a little confused on converting... sorry if this isn't the right place to post (please move if so).

trying to convert from Aim Hero  3 sens, 1600 dpi, 63 FOV (~95 Horizontal)

changing to 400 dpi for RDR since it seemingly cant convert at 1600.  I play on max FOV in RDR.  The settings I'm getting are 9 lookspeed and 2 aim for third person.  But it feels totally different.  

But 360 same? Just try monitor distance to monitor distance, it will be not same 360,but will feel good

On 11/17/2019 at 3:52 PM, Beto said:

DirectInput or RawInput after the deadzone fixing patch?

you can keep rawinput i reckon

Something still seems wrong with the input in this game. Every movement i make is either too slow or too fast, so far nothing else i play has made me feel so much like I have to place my crosshair in wait of my target to intersect themselves with it. Anyone else feeling like they have some issues? I can't hit a train from horseback, i know that much.

It is off, yes. I can feel that the deadzones are fixed but it just seems like i can't move precisely enough at low DPI and moving quickly is extremely fast. Feels akin to that of acceleration or inconsistent counts or something. Smoothing all the way to the left is off, yes? Because on playstation some of those bars were disabled when moved all the way to the right in the controller section. At this point its hard to tell if things are made better or worse by making changes.

Edit: I've also tried raw input and direct input under all the conditions of each change i've made. It just feels horrendously floaty and untrustworthy. they also introduced some obvious camera oscillation in third person with no weapons drawn with the deadzone patch.

Here's a question, have you noticed it feeling different in Red Dead Online when compared to single player? If you've tried that is.

19 hours ago, Feedingwolves said:

Here's a question, have you noticed it feeling different in Red Dead Online when compared to single player? If you've tried that is.

Online is noticeably harder because you don't get the slowdown of Dead Eye and hitting people who constantly do animations to bob and weave, combined with your screen shaking, makes hitting anyone quite difficult and annoying.

It's not the mechanics that are making it difficult for me, no, i was specifically referring to the behaviour of the input. I guess part of the issue is low dpi for small targets as well as terrible sensitivity range.

so running a glorious model o .

dpi is bottomed out at 400 (can't reduce it further) i play cs at 2.3 x 400 and dam rd2 wont let me drop the sens that far. 
any recommendations? any mods for the game or mods for my mouse that anyone can think of?  

Yeah rockstar has had this issue since the beging. They have no idea what they are doing when it comes to coding mouse. Sens is always off, no consistancy between any of the sights, it's a mess.

Aim Sensitivity is the same for all weapons? or each weapon have a different zoom? What gun is it calculated for?

Is it possible to edit the sensitivity more precisely using something like Cheat Engine to use higher DPI?

Could you please revisit Red Dead Redemption 2 and correct the calculations? It would be greatly appreciated!  When I select "first person aim" on your calculator I see that sensitivity is relevant to the fov of the game, but no matter what value I insert for the fov the rest of the calculations don't change.

On 9/20/2021 at 4:41 PM, DPI Wizard said:

It does change depending on the FOV, can you share an example where it doesn't change?

If I change the calculator settings for ADS for 360 distance. Then choose convert from CSGO and insert 1.5 sens@1600dpi. Then choose convert to rdr2 and choose "aim first person" or "aim third person", then, no matter what value I choose for rdr2 's fov the new calculated sensitivity stays the same. I can choose values from 0 to 1000 for the fov but the sensitivity stays the same according to the calculator of course...

8 hours ago, DPI Wizard said:

The FOV for the aim is locked, it does not change when you change FOV. Only the first person look is actually affected by the FOV change.

Thank you for the reply. Last question about the fov values in the calculator. Does "0" fov in the calculator mean that you put the fov bar in the game to its lowest setting? I am asking because if I put the fov to say 60, then I get a message from the calculator that I have way too high mouse dpi and that with the current dpi the sensitivity in the game should be "-3"( Note: I use 1.5@1600 sens in csgo). I see the notes about the fov in the calculator but it's a vague oneliner... Thank you in advance.

Is it possible to still add to this?  There are three different mouse modes, Raw Input, Direct Input, and Windows Mouse.  And I found that trying to calculate my Desktop sensitivity (WPS 4 at 1450) to RDR2 I couldn't do it because my sensitivity was in the negatives.  So, what I did in game was put all my sensitivities to 0 (the lowest it can go) and found it was still faster than my I usually play with, and so I tried using the Windows Mouse mode and found that it felt slower than my usual mouse sensitivity as I'm usually able to do at least 1 360 turn using my entire mousepad, but couldn't do just one.  So, what I'm concluding from this is that you are able to calculate to your accurate mouse setting using Windows Mouse mode, but I personally do not know how to and was wondering if you could implement a way on how to do it.