bebeto

you can keep rawinput i reckon

Deadzone has been indeed fixed, no need to put max smoothing anymore.

i didnt bother requesting since it's on their side to fix but yeah there's noticeable controller deadzone when moving mouse very slowly

Just a heads up, STW and BR have the same sens now, it has been fixed in today patch 7.4 and tested it, no more smoothing on 1000hz in STW, finally.

I know we have both game mods here but to avoid confusions there should be a warning mentioning there're still inconsistencies in STW and therefore any sens STW calculation is spoiled by negative accel compared to BR. Even a few days ago someone posted about it in STW subreddit : https://www.reddit.com/r/FORTnITE/comments/a0f5zz/inconsistencies_within_br_and_stw_sensitivites/

BR is fine. In STW there's nothing to do, except playing at 125hz and maybe 500, so good. i think he was talking about STW

When you have time could you check again STW at 1000hz because even today, i have retried doing fast swipe vs very slow. Fast movement, crosshair always end ups shorter of where it should be. It will also help me determine if it's on my side or not.

For consistency, muscle memory across all games. You're not moving your mouse strictly on straight horizontal line but hey to each his own. No afaik these commands are obsolete and are server side now, it's useless to change them.

Of course this doesn't make sense, you need to multiply not divide

I meant that if you still want the least discrepancy for your sens it's still better to use the config editor (more precise), instead of the ingame sliders. This new update didn't change anything about that. I don't even bother using ingame sliders anymore now but now you said it with cursor it's indeed a pain to match X and Y

Do what poppe said, you don't delete X and Y, from now on you just edit them, mouseSens should be set to -1, if you don't like to have a 1:1 ratio just set up your X sens and use 0.7 of your X sens for Y. Note that the ingame sens sliders for X and Y are still inaccurate (decimals are not perfectly matching), if you want a perfect sens matched, you still need to use the configsetting editor. btw neg accel, polling rate has still not been fixed in STW after 4.4

They're talking about this post : Nope single monitor. At least i'm not alone Now i remember you already mentioned it and feels like it. Make sense when moving slowly i'm in the 150hz range roughly and fast near 1000hz. I'll wait for you to confirm.

Just tested and tried some random cm/degree back and forth in STW hipfire in my homebase. There's something wrong with fast movement. Let's say i do a 19cm/180° very slowly i end up with an accurate result matching the calculator but if i do the same thing with a fast swipe i end up doing only an approx 110° for 19cm like some kind of neg accel. Could you test and confirm you get different results too ? maybe a polling rate issue ? but there's definitely something wrong for me, maybe i need a fresh install. No problem in BR tho.

We have same hipfire sens in both gamemod now right ? just to make sure

Im unfamiliar with apps like aim hero but if you can replicate your same res/fov/sens it may help but fortnite BR has its own shooting mechanic (bullet spread/accuracy) that would be hard to replicate. Even fortnite STW is different (different sens and shooting). CSGO not really, different fov feeling and you always shoot from hipfire, fortnite you will ads more often. Honestly the best practice is to keep playing it over and over again.

Oh ok I thought USA was supposed to keep same cm/360 between hipfire and ADS but now you said yeah it's to keep same point among all the different ADS. Make sense edited my post thanks.

Indeed if you're used to USA. Dont use viewspeed or it will inevitably reduce your sens when ADS compared to hipfire.

You can only keep the same 360° rotation, but since fov are different for targeting and scope, it won't be the same sens feeling. If you do that, your scope sens will feel way too fast. You cannot keep the same sens 1:1 ratio when FOV are different, you can only match it to 1 point (monitor distance or viewspeed) In Fortnite since default 3rd person fov is pretty low, you woould use hipfire with 360° and every ADS/scope to viewspeed (safest choice) or monitor distance (if you know exactly the point you want to match) Viewspeed for hipfire in fortnite will probably mess up your hipfire aim in most other FPS game. FOV difference is too noticeable.

I cannot find Scope and Targeting for BR in the dropdown menu, only hipfire. has it been removed on purpose or an oversight ? edit : nvm, didn't realize it's only available in game settings and not config

Can't really give my opinion since i'm still using the old one and for my sens the difference between both is abysmal. Here's a quote from DPI Wizard : Edit : i just checked and yes V2 is what i said in first post

Don't quote me on that but i think V2 is the updated version from Drimzi that was previously on the alpha calculator

That line doesn't work anymore

When you have time, please don't forget to put back targeting sens for STW. Thanks

No, it still use hipfire sensitivity. but before you separated BR/STW in the calculator, there was the option with 45 fov targeting sensitivity for save the world

@DPI Wizard Will it be possible to re-add Targeting sensitivity (config, ingame) for Save the World ? as it's still using the same sensitivity as hipfire. i think you forgot to add it back with Hipfire sensitivity when you separated PVP/PVE. Thanks.