Remnant: From the Ashes

To get 1:1 X and Y sensitivity do you calculate them separately or will just doing Horizontal be enough and matching the Vertical value?

DPI Wizard ur my hero

GG dude! thanks

Seems pretty limited as far as sensitivity options goes, is there only hipfire sensitivity? The base sensitivity at 0 is a little high too for 1000+ dpi. Looks pretty interesting otherwise though so might have to give it a go anyway since there's not many shooters that have caught my attention lately.

2 minutes ago, DPI Wizard said:

ADS added as well, scope next!

0 is quite high, but far from the worst I've seen. The game has ADS and scope sensitivity too. No FOV option though, locked to 90 hdeg.

Thanks, sounds good. Yeah, I suppose it's not too bad, doesn't seem you have to use the menu for much so an auto loaded dpi profile should be just fine to get some more range at reasonable dpi levels. I remember Warframe was one of the games I didn't even bother with since I would've had to use <400dpi to get a somewhat accurate conversion.

Wow for me the game has some serious negative acceleration. If i go very slow the 360/cm is correct if I go fast doubles it at least.

EDIT: Found the fix. I put these lines into Input.ini and set to read only (just in case)

[/script/engine.inputsettings]
bEnableMouseSmoothing=False
bViewAccelerationEnabled=False

I'm having issues with the sensitivity. I'm using a program called "Sensitivity Matcher" by Kovaak to check if the cm/360 is correct, and the values from this site is indeed correct. But the sensitivity doesn't match when using the mouse, it's much slower. Nvm, it was the acceleration, put the settings in the wrong file.

On 8/18/2019 at 3:48 PM, Bebe said:

Wow for me the game has some serious negative acceleration. If i go very slow the 360/cm is correct if I go fast doubles it at least.

 

EDIT: Found the fix. I put these lines into Input.ini and set to read only (just in case)

[/script/engine.inputsettings]
bEnableMouseSmoothing=False
bViewAccelerationEnabled=False

super useful thx

On 18/08/2019 at 22:48, Bebe said:

Wow for me the game has some serious negative acceleration. If i go very slow the 360/cm is correct if I go fast doubles it at least.

 

EDIT: Found the fix. I put these lines into Input.ini and set to read only (just in case)

[/script/engine.inputsettings]
bEnableMouseSmoothing=False
bViewAccelerationEnabled=False

screwed up my tracking hard before seeing  this  post time to rebuild

On 8/18/2019 at 11:48 PM, Bebe said:

Wow for me the game has some serious negative acceleration. If i go very slow the 360/cm is correct if I go fast doubles it at least.

 

EDIT: Found the fix. I put these lines into Input.ini and set to read only (just in case)

[/script/engine.inputsettings]
bEnableMouseSmoothing=False
bViewAccelerationEnabled=False

Omg thank you, I immedietly noticed something was wrong, negative acceleration is very strong in this one.

@DPI Wizard Todays patch just added a FOV slider. Quite a nice and detailed changelog of other fixes as well, should fix Ace disappearing after rerolling amongst other annoying little things like that by the looks of it. The slider goes from 0.5 to 1.5 with 1.0 being the default, no idea about the actual degrees though. 1.5 has some serious distortion though so it should be well over 100 hfov.

I didint understand How to make the sensibility 1:1 what do u mean calculate with ALL option? In fact i don t even know How i should make tem equal since i don t know How the game considers them.

3 hours ago, Guipe said:

I didint understand How to make the sensibility 1:1 what do u mean calculate with ALL option? In fact i don t even know How i should make tem equal since i don t know How the game considers them.

 

<-all

if you quote a post you are referring to that might just make it easier to help you with whatever you are looking at 

highly suggest the 

I'm pretty sure the 'aim' sensitivities are wrong, since it makes aiming rotates more than non-aiming.

where is this option my dude?

On 5/22/2022 at 6:49 PM, DPI Wizard said:

Do you have a specific example? Use the purple share button

This is an old question that wasn't responded to, but I have a similar issue.

https://www.mouse-sensitivity.com/?share=663d4502e0679071c1aa7623c333b1df

The Aim Sensitivities are faster both using kovaak's sensitivity matcher and manually 360'ing with my mouse on 125hz

50 minutes ago, DPI Wizard said:

Thanks for the link, I see the issue now. Working on fixing it!

You are doing God's work

1 hour ago, DPI Wizard said:

Thanks for the link, I see the issue now. Working on fixing it!

There is also an issue with my mouse movement even on 125hz. I'm not sure if the mouse movement is tied to fps or cpu usage. Kovaak's Sensitivity Matcher seems inconsistent