Pyroxia

So if we make jedi's trick vertical for Y axis horizontal for x axis is it makes sense more or am I doing something wrong with that?

I've been using this method and it works perfect for me. Improved my quake champions tracking. Other than BFV and BF2042 I recommend using 0 coefficient for scopes.

When is next update?

Name: Neon Boost Website: https://store.steampowered.com/app/1057850/Neon_Boost/ Status: released Release date: 20 May 2019 Availability: Free

3d windows is my dream since years. I searched it everywhere.

How can I reach beta version? I want to try new features early lol.

It's awesome for scopes but when we match from windows I swear every method feels different in 3D. I hit %32 lg with %0 in quake champions, %38 with %100mdh from windows and %41-47 with %100mdh horizontal-%100mdv vertical sensitivity from windows. This results are not coming from just one game. I'm hitting them consistently which is why I say when I match from windows everythink feels different. Now there is another result for overwatch. When I play with tracer. %0MDV from windows to game make my accuracy %47-55 consistently. Other matching methods wont work for that game for me. Data I get from every method crazy different I really don't know what is practically or what is mathematically best anymore.

Anyway to add vertical sens? There is options like GstInput.VerticalSoldierMouseRatio 1.000000 GstInput.VerticalSoldierMouseZoomRatio 1.000000 in config file.

I tried every method, every monitor distance percentage I've been here since 3 years. Only method I like to use is %100MDV for Y %100 MDH for X axis from windows to game. Sadly most of games doesn't have vertical multiplier support. I recommend everyone to try this method in games like cs:go quake champions, quake live, Team fortress 2, pubg, rainbow six EDIT: USE %0MDV For scopes.

NVM

I don't understand one thing how can u find deviation?

is he using %0 ? My point is tracking pGTI on my own not others.

Ok I tried enough and I can say nothing special about this method for me. It's just another monitor distance percentage. Sorry jedi but correct method should track PGTI in kovaak's naturally for me. Sadly no method can do this because of projection issues. When u look up sensitivity feels slower when u look down sensitivity feels slower it's the flaw of the 3D game in a 2D plane.

NVM I understand now

I want to use ur method but everything looks so complicated. Can you gave me sensitivity yaw, DPI and WPS for 1920x1080 cs go?

uuugh my bad just checked my settings up and I saw my scope sensitivity matching to %100MDH Calculator is correct.

Yes 48 default actually game has a focal length option if u touch the triangle in zoom sensitivity slider and it shows 0.37 is focal length for my settings but m-s.com calculator shows 0.45. Game itself doesnt require calculator for focal length scaling but I just wanted to notice you.

calculations seems off for zoom sensitivity.

Best title ever. "BORING GAME"

%0 Tracking in apex %100 Tracking in apex first minutes of video

If ur method integrated in any calculator I'd use it until then I can't try ur method but if I remember correctly u said deviation is less with %100mdv on 1920x1080. I'll respect any method since I used viewspeed vertical and can say it feels different than mdh %70 for me. Nowadays I'm changing between %100-180MDH from windows. Also tried accel for a while and I can say it's not that scary works well in some situations.

%0 works amazing in Overwatch %100 mdh works well on quake champions. This is my opinion thats why I recommend everyone to try which is best. I change my method so much and I'm not good player so don't mind me.

right its faster

I would recommend everyone comparing %100 mdh and %0 MDV in quake champions. Try each of them 3 days. Play with just LG. Highest accuracy wins!

Name:Redmatch 2 Website:https://store.steampowered.com/app/1280770/Redmatch_2/ Status: Released Release date: 25 June 2021 Availability: FREE