MoistGeorgeBush

Name: DeadPoly Website: https://store.steampowered.com/app/1621070/DeadPoly/ Status: Full Release Release date: Jan 12, 2022 Availability: 20.00

This is strange, but has anyone else's FOV stopped impacting their sensitivity? I booted up today and my sens felt off, after some testing it seems like FOV has no impact on my sensitivity anymore. If I use the calculator with default FOV of 90 I get an accurate sens, but then when changing FOV my sens stays the same (this isn't how it has worked for tiny tinas or borderlands 3). Can't figure out what has changed since I last played.

Ahh I see. Well thanks happy I got it figured out!

No I figured it out, I was measuring correctly, but there is something inconsistent about the slider in game. According to the calculator 3 in game sens, 700 DPI and 109 FOV should give me 20.2 inches 360 distance. I was getting around 22 inches or so. When I changed from 3 in game sens to a different sens and exited the menu, then changed back to 3 in game sens I was getting the 20.2 360 distance. The strange thing is that when I repeated the process sometimes I would get the "correct sens" and sometimes I would get the 22ish sens. Just plain weird, but Tiny Tina's does have janky M&K support. I know that may sound like I'm just measuring inconsistently or something like you suggested, but I've matched my sens for dozens of FPS games I promise that isn't the issue.

@DPI Wizard something seems way off with the calculator for this one unless I'm brain farting and missing something. According to the calculator for 800dpi, 3 sens in game, and 110 FOV, my 360 distance should = 17.5342 inches. But when I measure it myself with a tape measure it is much closer to 20.10-20.30. I tried turning on the mouse smoothing in game to see if that's where the discrepancy came in, but that wasn't accurate with the calculator either (and I assume this would be turned off anyways along with acceleration which I have off). I'm not sure if I'm missing something simple or if there's another setting somewhere affecting my sensitivity, but as far as I can tell the calculator isn't accurate.

I have it off, but have tried with it both on/off. It feels even more inconsistent with the setting turned on. I also tried turning the FOV based sensitivity scaling to off, but the issue seemed to persist (and it throws off the calculator). In all cases there seems to be some type of aim deceleration or aim slowdown while sprinting. It reminds me of the Sprint Sensitivity Reduction setting in Risk of Rain 2. During the first few years of early access in Risk of Rain 2 there was something you had to modify in the config to get rid of aim slowdown while sprinting. Now there is an in game setting in Risk of Rain 2 called "Sprint Sensitivity Reduction" that completely eliminates the issue. Here is a thread about it from a few years ago https://steamcommunity.com/app/632360/discussions/0/1768133742959740962/

Everything from the calculator seems to match up, but I'm feeling a good bit of deceleration while sprinting, any way to disable this?

@DPI Wizard I'm not sure if i'm doing something wrong with this game or if the sens settings have changed, but I changed the in game sens then set my sens in the config file as described, but it seems massively off. Calculator says to set to set Human.Aim{ sensScale:r=0.034609 in the config file to get a 360 distance of 20.2017 inches (800dpi, 100fov), but my 360 distance is probably about 200 inches lol, I'm not sure if I'm missing something here? Any chance you can look and see if it is still accurate? Also completely unrelated question, but I'm guessing aim acceleration should be set to zero?

OK after playing a few games I definitely notice a difference after changing these two settings. The steam controller support one seemed to make the most difference. The difference isn't as obvious with easy to use weapons like the AR or BR, but I did much better with the sidekick which I've always struggled with. I have no idea how you found these settings haha

Ya I just tested after restarting the game and I might notice a little more responsiveness but hard to tell for sure. I'll have to get some games in in a bit to really see. Did you notice any difference from disabling the vehicle setting mentioned ?

Weird I tried it and couldn't tell a difference maybe I need to restart my game in between turning it on off?

I know when NV Control panel first added and FPS limiter this was the consensus, but things have been mixed as far as what is the best option since then. I've just read different takes so I'm not sure. Maybe check this link out and tell me what you think.

Maybe? I know I've had global frame rate capped at 143 on 144hz monitor with global vysnc and gsync enabled as well since I started playing - and I've never noticed any aiming issues.

Hmm this seems weird. I feel like if there was this big of an acceleration issue I would feel it. I'm pretty anal about mouse acceleration/deceleration and I've felt nothing but raw input so far. I wonder if this issue could be tied to something in game ?

This post looks like it's entirely about controller? I guess it's anecdotal on my part but I definitely haven't noticed any differences horizontal vs. vertical on M&K.

Ya I'm 100%, but last flight 800dpi 1.1 gave me a 360 distance of 19.8348 which is what the calculator still says, but when I've measured after the beta launch it seems closer to 17.5-18 inches. Once I drop down to 1.0 it seems to measure something over 19 or so. I'm not sure maybe @DPI Wizard can check this out?

Did something change slightly from the flight to the beta release today? I was playing 800dpi 1.1 in the beta, but now a similar sens seems to be 800dpi 1.0.

So does this mean the issue of mimicking analog input was actually fixed?