Jump to content

Pyroxia

Premium Members
  • Posts

    313
  • Joined

  • Last visited

  • Days Won

    7

Posts posted by Pyroxia

  1. there is a way for applying raw input in wow and also it stops freezing camera problem on fast swipes. I'm writing the method down below it fixed my freezing camera in fast swipes problem. also can be updated for raw input in calculator ^^

    There is a config CVar "rawMouseEnable" we could test here.

    To check if it's enabled type or copy - then ctrl + v this into a chat box.

    /script print(GetCVar("rawMouseEnable"))

    That will show a single 0 if off or a 1 if on.

    Now to enable it use:

    /script SetCVar("rawMouseEnable", 1);

    To double check that the script worked go to the Wow folder > WTF - look for the Config file. Open with notepad. This should be at the bottom of CVar list:

    SET rawMouseEnable "1"

    (Alternately you could just add that setting using notepad exactly as it is here. Copy/Paste would be your friend - I have it enabled that is my copy paste)

  2. 1 hour ago, DPI Wizard said:

    I have added these now, but noticed that they also change depending on weapon type, and both the FOV and sensitivity for these are all over the place. There's absolutely no logic behind it, but the calculations are accurate providing it's the correct weapon and scope.

    I've also updated the FOV calculations for hipfire slightly, so it's more accurate now.

    They are a lot faster indeed.

    Thank you so much wizard.

  3. Sorry for necroing but I sensitivity formula used in bo3 is really confusing. Looks like thermal scope exactly using %0 mdv since both hipfire and scope sens are same (correct me if I'm wrong) I understand there is no ads slider but which I heard some scopes are not using focal length scaling. I totally avoid using anything different than focal length since it brokes my aim for other games that I play. (It really impacts my aim huge) so I just want to ask can you add some more scopes like thermal scope so we can check which one is using which Monitor Distance percentage @DPI Wizard that would be so cool. Cuz sniping in this game is hella fun compared to other shooters. Atleast reflex sight, locus default scope,recon scope and elo would be crazy good. Thank you anyways wizard. 

  4. 9 minutes ago, TheNoobPolice said:

    I don't play Valorant, but I only use MDD for in-game ADS / zoom scaling changes. I'd pretty much always set hipfire to 360 distance so my navigation feels familiar. 

    Val is a lot more about holding angles though, so maybe the navigation is less important than the crosshair speed. I don't know, not my thing honestly.

    Thanks a lot for answer.

  5. On 3/13/2022 at 5:53 PM, DPI Wizard said:

    The original idea behind the current Jedi's Trick implementation was that it does horizontal and vertical at the same time. This obviously only works if the game supports vertical sensitivity, and it will only be 100% correct for hipfire.

    So I'll add a vertical option in the next update.

    So when transferring sensitivity from windows to game setting horizontal to %100mdh from windows and setting vertical to %100mdv from windows is the most correct way am I right? Because when I match both axis with %100mdh it doesnt feel natural but with that method I feel my sens is natural.

  6. 16 hours ago, MacSquirrel_Jedi said:

    You can do it manually. I updated my previous post. This is really uniqe needs. And it is not necessary to implement it. Because it is practicaly individual adjusting. And for that there is standard monitor distance method.

    In that video yes. But coefficient is changing depanding on your input and output (Win/Hipfire/ADS/Scope). You can imagine coeficient as a reference point on your monitor. And you can always find a position from which other Aims will have less deviation in sensitivity than from another position.

    And you can do it by changing coefficient in game if implemented, or by changing sensitivity of each Aim separately

    Great job! Mission completed :) I made a quick check in CS:GO and works good. Now it's perfect :) 

    If you are playing more games, first option is better (360° for Hipfire)

    I will share with you guys little philosophy behind the vertical methods. As you play, you will focus most on the area of the screen around the crosshair. And of course you want the minimum difference in sensitivity here. Rather than having zero deviation in sensitivity at the edge of the screen, for example (MD 100%). I prepared some examples below for you.

    Jedi’s Trick - Vertical (Recommended) 

    Web_62.png.b9dc33496baddc8b508a8b4a34205581.png

                           Settings 1                                                 Settings 2                                               Settings 3

    As you can see vertical method have lower deviation between points in focused area which is represented by orange square (VFOV = HFOV = "1:1"). 

    Jedi’s Trick - Horizontal 

    Web_63.png.485145054edf1972f7f68f93448b70e2.png

                           Settings 4                                             Settings 5                                               Settings 6

    Horizontal method will find lowest deviation in sensitivity for whole horizontal field of view. But differences in focused area are bigger.

    Can u show deviation for Jedi's trick vertical for Y horizontal for X axis @MacSquirrel_Jedi

  7. 16 hours ago, MacSquirrel_Jedi said:

    You can do it manually. I updated my previous post. This is really uniqe needs. And it is not necessary to implement it. Because it is practicaly individual adjusting. And for that there is standard monitor distance method.

    In that video yes. But coefficient is changing depanding on your input and output (Win/Hipfire/ADS/Scope). You can imagine coeficient as a reference point on your monitor. And you can always find a position from which other Aims will have less deviation in sensitivity than from another position.

    And you can do it by changing coefficient in game if implemented, or by changing sensitivity of each Aim separately

    Great job! Mission completed :) I made a quick check in CS:GO and works good. Now it's perfect :) 

    If you are playing more games, first option is better (360° for Hipfire)

    I will share with you guys little philosophy behind the vertical methods. As you play, you will focus most on the area of the screen around the crosshair. And of course you want the minimum difference in sensitivity here. Rather than having zero deviation in sensitivity at the edge of the screen, for example (MD 100%). I prepared some examples below for you.

    Jedi’s Trick - Vertical (Recommended) 

    Web_62.png.b9dc33496baddc8b508a8b4a34205581.png

                           Settings 1                                                 Settings 2                                               Settings 3

    As you can see vertical method have lower deviation between points in focused area which is represented by orange square (VFOV = HFOV = "1:1"). 

    Jedi’s Trick - Horizontal 

    Web_63.png.485145054edf1972f7f68f93448b70e2.png

                           Settings 4                                             Settings 5                                               Settings 6

    Horizontal method will find lowest deviation in sensitivity for whole horizontal field of view. But differences in focused area are bigger.

    What about matching vertical for Y axis horizontal for X axis?

  8. 17 minutes ago, fortunate reee said:

    grafik.png.f56faae187a395de3b3e77975115153a.pngim assuming that this could be achieved using the repsective multipliers in rawaccel or custom curve ( at least for hipfire)

    When you change it xy ratio with raw accel you also change windows pointer speed because of this you need to match Y axis again. It will be same cm/360 but different monitor distance.

    EDIT:

    Let me explain when you set your vertical sens 0.77 which is %100 MDV for 1600 DPI 3/11 from windows and set horizontal to 0.62 (%100 MDH for 1600 DPI 3/11 from windows). Now let's try to simulate it for games doesn't have x-y axis option.

    keep horizontal ratio at 1=1600 DPI and set your sensitivity 0.62 in game now for vertical sens adjust your xy ratio it must be 1980 DPI at vertical axis. now you changed your windows pointer speed too and it's not same anymore.

  9. 2 hours ago, Quackerjack said:

    should be also possible if your mouse can be set to different x y dpi steps.

    Example:

    Dpi of 1600 = 100% MDV as you said you want match horizontal 100% = 178% MDV

    so: 178%*1600/100% = 2848 new dpi on x axis. (i guess if iam right not sure )

    But i wonder why you wrote it only works for hipfire? Cause when you change the horizontal axis to a different sensitivity the ads sensitivity will also get affected.

    You still need to match y axis if u change dpi for windows to game also %178 mdv already out of monitor vertically. If u didn't match vertical "zoom" sensitivity for correct value any % above %100mdv is out of monitor. For example soldier vertical sensitivity bfv is 1.250000 if u keep your soldier vertical "zoom" sensitivity at 1 you are matching vertical point out of your monitor. You need to make your soldier "zoom" sensitivity 0.750000 (1.000000 - 0.250000)

×
×
  • Create New...