spyder256

Name: Mass Effect Website: https://store.steampowered.com/app/17460/Mass_Effect/ Status: Released Release date: May 28, 2008 Availability: Purchase I know this is in the unsupported section. But maybe you could try it with this mod. Claims to make the game use raw mouse input and remove acceleration. https://www.nexusmods.com/masseffect/mods/82

Name: Call of Duty: Modern Warfare Remastered Website: https://store.steampowered.com/app/393080/Call_of_Duty_Modern_Warfare_Remastered/ Status: released Release date: Jul 27, 2017 Availability: purchase Not sure if it uses the same sens as one of the other games or what

So... everything 2x and up is red dot? And below 2x is iron sights???

I still don't understand the difference, they all have red dots

Calculator is bugged? actual fov is higher than the inserted fov now for some reason

One of the best games ever what you talking about haha

So... I am suspecting this game of mouse acceleration. I am having troubles getting a consistent measurement in this game, I seem to be getting different measurement depending on how fast or slow I move the mouse, almost 1cm difference sometimes. Whereas I boot up Battlefield 4 and Overwatch and I get the same measurement every time regardless of how fast or slow I move the mouse. Am I just just crazy or what? Should I just keep playing the game and pretend there's no problem? I'm using an Endgame Gear XM1 at the moment for reference. Edit: And Destiny 2 as well. Again in these other games it doesn't matter if I creep the mouse as slow as possible or fling as fast as possible, the most difference I can see is maybe 1mm if I measure really sloppy or something. But in Paladins I can't get a consistent result. Oh and I'm on a Glorious Helios hard mouse pad so no dpi difference based on pressure like on cloth pads and etc.

Name: Slime Rancher Website: https://store.steampowered.com/app/433340/Slime_Rancher/ Status: Release Release date: Aug 1, 2017 Availability: purchase

Okay so this would be correct for black bars? If so, this is where my confusion lies, why do you need to account for parts of the game that you can't see?

Okay... so what would be the correct way to convert from Overwatch 21:9 (no stretch or black bars) to Paladins 16:9 with black bars (or stretch), for example? And this all still applies to Monitor Distance 0%, correct?

So I've learned from this post: That apparently you have to account for black bars in the sensitivity calculation. Making the sensitivity higher on 16:9 on a 21:9 with black bars vs a 16:9 monitor. (38.8275 cm vs 29.0878 cm for instance) Whereas if you stretch that 16:9 to fill the 21:9 screen then the sensitivity can stay the same. If the black bars are not part of the games field of view, why do they need to be accounted for in the calculation? And why does the stretch not affect things? I'm having troubles understanding this concept.

God, it boggles my brain that this is even an issue that exists. Like how does this even happen?

https://steamcommunity.com/ogg/707030/announcements/detail/1569993750896946269 They just added a check box to disable mouse smoothing!

For some reason, with these settings I get closer to about 49cm. Edit: Well I just booted it up again and got anywhere from 40cm to about 42cm sooooo yeah idk. And now I'm getting around 48cm to around 51cm again. I'm confuse

No *Regerts And I second this! Can't wait to play once my slow internet finishes downloading. Postal 2 is one my favorite games, so much stupid fun I don't know why it's called 4 though, I mean there is no Postal 3

Name: Wasted Website: https://store.steampowered.com/app/327510/WASTED/ Status: released Release date: Jun 7, 2016 Availability: purchase

Could the calculator be updated to work with the Halo Mouse Tool v7? The calculator has minimum of 1 where the tool can go as low as 0.01.

So, for some reason when I use the calculator my sensitivity is about double what it says it should be. For example when I put in these settings. I get about 16.9something cm. But if I put in 1.8107735 for sensitivity it's about where it should be. (33.8cm) I have set X scale to 0.50 and Y to 1.00. (in game, still doesn't show in config file for some reason). This goes for Ion Fury as well, obviously.

Name: Ion Fury Website: http://www.ionfury.com/ Status: Release Release date: August 15, 2019 Availability: Purchase Also maybe Eduke32 while you're at it since it's the same engine. (supposedly)

No such thing as too high or too low. Just what works for you. Also what game and fov makes a difference as well. 60cm/360 in Overwatch is not the same thing as CS:GO for instance. (55.51 vfov vs 73.74 vfov) It would feel slower in Overwatch and faster in CS:GO

Could maybe add EDuke32? And maybe Duke Nukem Forever? Just for shits and gigs

Right, so first I boot Overwatch to make sure there's not some other problem besides the game. And in Overwatch I get the same result no matter the speed I move the mouse. So it's not the mouse or the system. And in Borderlands before I press F9 for the custom sensitivity, with the default settings I also get the same result no matter what speed. But after I enable the custom settings, results become inconsistent. Higher sensitivity the faster I move the mouse so it appears to enable acceleration for some reason. So am I crazy? retarded? Or what?

So um... the custom sensitivity commands from the calculator, this specifically: Seems to be causing mouse acceleration. Moving the mouse slowly yields a higher cm measurement, and and moving fast gets a higher cm measurement. And there's no consistency, naturally. Yet, measuring with the default settings, I can't detect any acceleration... so, yeah idk I'm still experimenting but that's what I've found

From MarkC "Windows_7_MouseFix_TextSize(DPI)=100%[email protected]": I guess 7 has different smooth X curve

Oh so you didn't make it then, mkay. Didn't catch that