Keyinator

Do you know by any chance how to disable that the config is reset everytime I change a setting ingame?

Yeah that was the case. It displayed csgo but after reselecting it it was fixed

When converting from cs:go to windows I get: Select game to convert from Windows / Desktop DPI: INF Distance: - Base length: 0 cm Discrepancy: NAN% (0 cm)

187187 133737

Chrome

But the value is the same everytime? (Ofc with the same fov type)

Does this work on every game or does it depend?

But isn't this one example of doing it manually? First I set my game I'm converting from to CS:GO with a sens of 1.685. Then I set the game I want the sens to be converted to Fortnite (for this example). I lloked up the sens it gives me for Monitor-Distance (33%) (0.010872) and V2 (0.011868). (A difference of 0.000996) Now that the Monitor-Distance is lower I increased FOV so it get's higher. New fov: 82 New Values: M-D (0.011244) and V2 (0.012214). (A difference of 0.00097) New fov: 86 New Values: M-D (0.012015) and V2 (0.012916). (A difference of 0.000901) Then a test if I can get the difference lower: New fov: 85 New Values: M-D (0.011819) and V2 (0.012739). (A difference of 0.00092) (Get's higher) New fov: 87 New Values: M-D (0.012215) and V2 (0.013094). (A difference of 0.000879) (Get's lower) So... New fov: 90 New Values: M-D (0.012829) and V2 (0.013632). (A difference of 0.000803) (Get's lower) So we go higher New fov: 92 New Values: M-D (0.013253) and V2 (0.013995). (A difference of 0.000742) (Get's lower) I made a jump to see where the turning-point is New fov: 98 New Values: M-D (0.014603) and V2 (0.015106). (A difference of 0.000503) (Get's lower) Another jump New fov: 110 New Values: M-D (0.017726) and V2 (0.017414). (A difference of 0.000312) (Get's lower) New fov: 111 New Values: M-D (0.018017) and V2 (0.017611). (A difference of 0.000406) (Higher than with fov 110) New fov: 105 New Values: M-D (0.016347) and V2 (0.016439). (A difference of 0.000092) (Get's lower) New fov: 106 New Values: M-D (0.016613) and V2 (0.016633). (A difference of 0.00002) (Get's lower) So in theory you have a more constant similiar distance to CS:GO with sens 1.685 when using an fov of 106 in Fortnite (When I made this I was a little bit under time-pressure so please excuse any writing-errors or unnecessary fov's.)

I found a bug: Played CS:GO (the first training option). Time was over but if you spam p it goes on and your score increases.

You can now change sens for Aiming and Scoping. Would nice if it would be updated here

Trove pls. It's on steam for free I think.

But CS:GO ignored WPS when I tested it with Raw Input disabled

OK, but wouldn't it be better / more accurate to use the "real" multiplier (the one I get from the console)?

I am not sure how you mean that. Could you do this and send me a screenshot, pls?

But this wouldn't give me the same ratio as from CS:GO, right?

I don't know if I am totally wrong here but shouldn't your fov for fortnite be 50,53 since you can't adjust it.

100% does not mean it's the best one. It only means your aim is 100% the same at 100% of your screen (total right and left) everywhere else from the point it will get more inaccurate. But it's not a big problem.

And couldn't you make a convert-mode that gives you FOV and sensitivity so the crosshair sesnitivity is exaclty the same as the sensitivity from the game you are converting from no matter how far you turn?

Also is it normal that my sensitivity for ADS in PUBG is lower when my Aim is Hipfire than Zoomed (Ratio 1) (Monitor Distance 10%)?

Is Viewspeed ment to be ignoring WPS on the first game?

Helped me alot. But how would you compare viewspeed to monitor distance and 360°? (from one calculation it matched arround 60% Monitor Distance. Is this right?)

You should use the sensitivity from the game you played most (your aim is best). And you should pick the convertion-method depending to how you act in the game. As the FOV and other stuff changes from game to game most of the time the sensitivity calculation just goes close to your other-games-sensitivity but only perfectly matches it in one point. So the methods kind of change the point it matches. 360° Distance = if you have to do a 360° to get to your target (not often needed). Viewspeed v1 is for movements at about 70% and v2 at about 75% of your desktop. (What I mean by the percentage is explained in the video ↓) And on Monitor Distance you can decide where it should match. Here is a tutorial on the Monitor Distance: (Since I am also new to mouse-sensitivity I could be wrong in some things but I hope I explained it accurate enough)

How does the calculation with monitor distance work and what does "Match at XY" mean in that case?

The Path of the normal MC-Launcher is .minecraft but I guess for other Launchers it variies