koraynilay

Name: Cloudpunk
Website: https://store.steampowered.com/app/746850
Status: released
Release date: 23/04/2020
Availability: Purchase (now on sale until the 2nd of august)

There was quite a lot of changes here, I've updated it now and added the different zoom levels

Just added a new feature for advanced and advanced plus modes where you can see your pixel to count ratio.

Default mode will show the maximum for any aim, while advanced mode will show details for each aim.
A pixel ratio of 1 means that your crosshair moves exactly 1 pixel for every count:

Going lower means an even smoother movement, like 0.5 pixels/counts:

Or 0.25:

Ideally you should not be over 2, as that theoretically means you are unable to aim directly at something on the pixel you skip. Shown here as 2 pixels/count:

And 4 pixels/count:


Now as mentioned this is theoretical, the reality is that even at 2 pixels/count variations such as bullet spread will in most games far outweigh this pixel you can't aim at. Also for this to have any real impact you have to aim at something 100-150+ meters away without a scope.
So the bottom line is that it certainly doesn't hurt to make sure the pixel ratio is below 1, but it is by no means critical. Over 2 should be avoided.

Added both of these!

Added!

Name: ULTRAKILL
Website: https://store.steampowered.com/app/1229490/ULTRAKILL/
Status: Demo
Release date: Summer 2020
Availability: Free Demo for Steam Festival

Name: Diabotical
Website: https://www.diabotical.com/
Status: Closed beta
Release date: N/A
Availability: Sign up, but you have to be selected
The beta starts on the 28th of February. More info on the website.

Name: Diabotical
Website: https://www.diabotical.com/
Status: Closed beta
Release date: N/A
Availability: Sign up, but you have to be selected
The beta starts on the 28th of February. More info on the website.

Name: Diabotical
Website: https://www.diabotical.com/
Status: Closed beta
Release date: N/A
Availability: Sign up, but you have to be selected
The beta starts on the 28th of February. More info on the website.

Name: Diabotical
Website: https://www.diabotical.com/
Status: Closed beta
Release date: N/A
Availability: Sign up, but you have to be selected
The beta starts on the 28th of February. More info on the website.

Name: Diabotical
Website: https://www.diabotical.com/
Status: Closed beta
Release date: N/A
Availability: Sign up, but you have to be selected
The beta starts on the 28th of February. More info on the website.

Name: Disintegration
Website: https://store.steampowered.com/app/536280/Disintegration/
Status: Open Beta starts today!
Release Date: 2020
Availability: Free(Open Beta)
Edit by @DPI Wizard: There's some acceleration in this game so it can't be added in the current state. But I'll keep it in the list and check back when it's released.

Added.

This is my first post in here, so HI EVERYONE!!!
 
For some reason* I'm testing around with Linux (Ubuntu 16.04.1 LTS 64-Bit) as a gaming machine.
 
While doing so, I have noticed that linux' mouse speed is drastically different from that one of windows. There is a slow base speed and a fast acceleration. I couldn't even find a checkbox for "acceleration" in its control panel, only a slide bar for mouse speed with continuous sliding and without any numbers. I also notices that the mouse sped in my favourite game Wolfenstein - Enemy Territory also is completely different (of course I've adjusted ingame "sensitivity" setting).
 
So I started googling for how to set linux mouse speed to windows mouse speed, and I've found 3 kinds of answers:
- use the slide bar.
- There is a console command to adjust base speed, acceleration threshold and acceleration scale.
- You should not wonder that a different OS has a different mouse behaviour as another OS. It is not possible to adjust linux's mouse behaviour to that one of windows. You'll get used to that (even MUCH better) one of linux.
 
I don't find these answers very satisfying. And for knowing the kind of device we are talking about (a computer mouse...), I know that it is just a "camera" detecting movement of the device on a surface, translating it to movement in dots in x- and y-direction, sending it to a pc, whose operating system then translates the raw dot input into movement in pixels on the screen. I don't know why the fuck it should not be possible to adjust the mouse behaviour of one operating system to exactly represent that one of another OS, no matter what god damn dots-to-pixels translation function the operating system uses by default.
(sorry for my upset selection of words... I am really sick of people telling me "this is not possible" and tired of showing them "it is".)
 
 
 
So, after this unsatisfying googling, I thought the best place to ask how to do so, would be in this forum. You show how to adjust mouse speeds of different games to match each other, so who else should better know how to adjust Ubuntu's mouse speed to that one of Windows as you?
 
I have a Logitech MX Revolution
with 800 DPI (The SetPoint slider is in the middle, so the driver/hardware based dpi scaling should not be applied)
and a WPS of 6/11 (I have never touched it, so it should still be 6/11 which means 1:1 dot-to-pixel translation, when I remember right).
 
 
 
Thanks in advance for your answer!
Best regards, Rhino
 
 
 
*I have a self-made gaming-pc from 2009. It has full XP support. But my new graphics card (R9 390) doesn't have XP drivers anymore. On the other hand, my motherboard doesn't have Windows 10 support, which leads into messy errors (there is an input delay; sound/video starts to stutter/microfreeze when I press a button on a PS/2 keyboard; I have a performance loss to ~60% in W:ET). In Ubuntu I have 162 fps by playing back a demo which plays with 90-104 fps in windows 10, so it could be a good replacement for that one game.

50% is the middle ground, the video isn't explaining it very well either and i don't think anyone but only 2 people understand what's really going on.
That's why i will take the time and explain this once and for all!
 
It's a very common mistake to think that you can match your desktop sens with a FPS game, because you cannot.
The best you can do is 50% and i will try to explain why.
 
Every FPS game uses the rectilinear projection methode to visualize the environment, this is because you need to create peripheral vision and the perception of depth but because you are projecting this image on your flat 2D monitor display, it's impossible too create real depth at all.
So to accomplish this perception they are "bending" the image creating a cylindrical shaped image and that's the arc that you see in the video.
 
A high FOV like in FPS games means forcing the image to bend because your display can't project the whole environment with a flat image the only solution is to bend it too create more space. but when you overdue the FOV increase the image will start to distort and somewhat collapse at a certain point. 
It feels like the image is bowed inwards like someone pushes a needle or pin into the center.
That’s why this effect is also called “pincushion distortion” which makes objects at the edge of the display unnaturally large in scale and will tend to misestimate the size and shape of objects, giving misleading visual information since the objects will rescale and significant decrease in size when turning towards them.
 
So, the in-game image is bent and your desktop surface image is not, even so they both are projected on the same evenly sized display. 
This means that the in-game image is in fact larger the the desktop image when it would be projected flat like the desktop image.
 
But since it's projected cylindrical, every object needs to "rescale" to fit on your display and that what's causing the "pincushion" effect and your mouse movement will act by it, meaning that when you turn towards an enemy at the edge of your display, your mouse movement will go faster then your desktop movement and your enemy will look bigger, but once you past the "50%" mark of your display (50% = pixel number x-axis: 480 / y-axis: 540 on a 1920-1080p counting from bodem left) the mouse movement will start to go slower then your desktop movement and your enemy will rescale and be smaler.
 
So your in-game mouse movement is not linear but your desktop mouse movement obviously is, meaning it's impossible to match your desktop mouse movement with your game across the whole line, but only at one point.
50% matching means that you synchronize your desktop mouse movement with your in-game mouse movement at pixel number x-480 and 1440  / y-540.
So the distance your mouse will travel to reach this pixel is the same between game and desktop. (but only at that point!)
Since this is the middle between the center and the edge of your display it's the best you can do too bring the deviation to a minimal across the whole line.
 
If you would take 100% match it would mean that the synchronization is at the edge of your display.
So the deviation between 0% and 74% will be larger then when you sync at 50%.
100% match will only be more accurate then 50% match once you past the 75% mark,
50% covers more of the spectrum then 100%, and that's why you need to sync at 50% and not at 100% for the most accurate result
 
Amen to that!

Just added this now.

Hired Ops is added!

Name:  Hired Ops
Website: https://store.steampowered.com/app/374280/Hired_Ops/
Status: Early Access
Release date: October 21, 2016
Availability: Free 2 Play on Steam

Name:  Hired Ops
Website: https://store.steampowered.com/app/374280/Hired_Ops/
Status: Early Access
Release date: 21 października 2016
Availability: Free 2 Play