fortunate reee

@DPI Wizard this + check your emails to see if you are in the closed beta

the game itself feels somewhat off to me , since ubi hasn't mentioned fixing this error id assume as muchh

siege just rounds differently it uses the ini fov , we are in te .00001 region so rounding wont actually impact you in any noticeable fashion

you will still have to relearn all other scopes + movement wont feel the same. this topic has been chewed out ages ago and it has been very conclusive 360 just isnt up to par when it comes to scopes and there are far better options that combine the actual hipfire match with decent uniformity. that thought of yous is about 5 years old and wasnt very good back then either (inspired by some latam players spread by reddit)

there is a solid reason why no one with a grasp of the topic would suggest using 360 distance for anything but hipfire, that being the perceived visual change in rotation speed . unless yu match the exact fov at that zoom level and hip fire at the same time you will not have the same "feeling " even if you match the distance. what works great would be matching the hipfire fov (73.74 vdeg ) and said distance with csgo and using mdv 133.33% for the scopes giving you the same scale to get used to. pretty sure the instructions mention all of this

set this to vdeg and select whatever fov you are using in siege set ads in siege to 50 for all scopes if you aren't already using that https://www.mouse-sensitivity.com/?share=bcd5011fb518a8fdd88f85c9d3e8fad1 should end up looking like that

if you want uniform acceleration id suggest using one of the many external options like raw accel , its faceit / vanguard approved ( the video below has most links in its description)

worked well back when some games had different x and y axis defaults ,think arc used to be that way wasnt it

tbf while this option is great it is somewhat dependent on dev support . if i were to use different x and y values id likely use either raw accel or my mouses internal x and y axis dpi feature to change one axis since those aren't affected when a game doesn't support x and y axis modification.

both games use the same default scale for ads / scopes its best if you stick to 50 on all scopes (if you desire the most consistent experience that is ) https://www.mouse-sensitivity.com/?share=70ea63162d1f60874178fc4591b9066c this would perform identical although it kind of misses the point of focal length.

share your conversion

the only way to get 1:1 distance to feel the same is to remove the fov aspect and just not have any zoom to begin with (if there is no change in fov the same distance will feel the same) ^since this isn't achievable and not actually desirable the only other option as far as consistency goes you cant really beat the 0% match , its just something that one kind of has to get used to the nice thing is once you are used to it you end up just kind of feeling where/ how to move instead of rotating a set distance every time

1.https://www.mouse-sensitivity.com/forums/topic/6396-instructions/ (if you are matching 360 distance make sure to cal it 1:1 distance, not sens this could cause confusion) 2. legacy changes your fov values thus your speed will feel different the calculator offers this option it is however not recommendable since it doesn't actually benefit you. something that is generally ore advisable would be which would end up being 0.000 multiplier at 1.0 ads and scope which is 1:1 tracking with all scopes (changes distance based on fov changes ) for a more extensive explanation id suggest

if you match the hipfire fov and ant the same hipfire 360 this would be viable , in theory 0% on all 4 will give you the same result when you have the same fov and match if you don't so its the safer bet 0% = 1.0 ads in apex the .004935 is there due to a rounding error in the game (its the games default scaling so yes getting the same values is intentional)

that 1.3 thing doesn't even give you the exact same 360 distance its just the closest possible ads value one can set in game to match their hipfire 360 to their 1x scopes / smg ads. this doesn't apply to AR, LMG, Sniper ads, those are closer to 1.4 it will also mess with the re45 since that gun has the same 360 distance at 1.0 due to the fov not changing when right clicking and focal length at the same fov is 360 dist ------ tldr : don't parrot stuff like that especially since its not necessarily the best choice

its generally advisable to set ads multipliers to 1.0 and then use either 1.333 or 0.000 multiplier depending on your preference (if i am not incorrect ) legacy should in theory be similar to 0,0000 1.0 multiplier with ads affected

there is a way to stretch apex using autoexec and you can match both the fov as well as the sens pretty closely using the config file so matching hipfire would likely be your go to (if you want to rely on crutches like stretched in the first place that is)

<-all if you quote a post you are referring to that might just make it easier to help you with whatever you are looking at highly suggest the

works perfectly and you even separated the sens from the link to that aim trainer double win in my books i can now copy and paste values without launching the site by accident

noticed this happening the past couple of days whenever i open the site it does not properly load my saved values , works fine after reentering a value https://www.mouse-sensitivity.com/?share=300688773e0886306acd33aa881a2a73 @DPI Wizard

correct green/yellow just means that the discrepancy isn't all that important while darker red is a more significant discrepancy ( i wouldn't worry about it all that much tho since very few games match perfectly and our brain is great at adapting to stuff like that on the fly)

why would the vast majority of r6 players use 83 ads for ads thinking that it gives them 1.1 sens when in reality it only matches the 360 distance for the 1x scope while giving you random distances on all other scopes. (as you might have found out by now pros are mostly humans like you and me.) obviously they spend alot more time in the game they play when compared to your average player and some are simply mechanically gifted. that doesn't turn them into an all knowing entity most of them just copy what worked for others ( for example the change in ads sens to a value that isn't 83 (mostly lower)after shaiko started doing well in the second phase of his pro career) using a lower sens the initial reason for many pros to use 4.3 stretched is them coming from a cs back ground where it was used to lower the fov / making the char models bigger and simply having gotten used to using it. (if you have already played a decade being on 4.3 stretched you might as well stick to it ) an alternative reason would be the good old "i heard it is good and x uses it so i just use it " when in reality there is no substantial evidence that stretched res actually makes you better just like there is no substantial evidence that stretched res is hurting our performance (besides not being able to switch between non stretched and stretched fps games as easily as if you'd have played native in both ) https://youtu.be/R0_OK2yEed4 ( if you know what you are doing you don't really need crutches) tldr: both ways have their advantages, native is just less messy to get into and easier to stay uniform with when playing more than one game and aim training using something like kovaaks tldr+: pros aren't all knowing creatures most of the time they just don't know whats good or what is the most viable option/ what things do this one is another great example of half baked knowledge about gsync( man still thinks that it introduces noticeable input lag which is factually incorrect) from a man that has played counterstrike for most of his career and happens to have no idea what hes talking about in this case. ----------------------- great example would be f1 you wouldn't ask a formula 1 driver how to calculate the best possible speed to go into each corner you'd ask the mechanics / designers that put the actual math in the car and its several finely adjusted parts. that doesn't mean the drivers aren't great at driving and it by no means makes them less valuable. it just set boundaries we just kind of lack days --------------------------- you just need to know what you have on hand for your specific use case and use it to the best of its abilities if you play 16:9 with 90 vdeg you essentially have 120 fov that wont help you unless you stand right in front of someone using a more reasonable fov matching your native res is actually a smart choice (106 - 110 )can work wonders

btw @DPI Wizard that rounding thing that you mentioned , is it in any form correlated to the slight fov variation present in the in game fov slider ? would be pretty interesting if that was an intentional method of correcting an error

you can in theory match one axis, it still messes with the diagonal as well as either the x or y axis depending on what you tried to match the 360 distance should stay identical while causing a different feel due to the change in fov as well as the stretched pixels 16.9 4.3 stretched the vertical sens shouldn't be affected ! however we never strictly move 100% vertical / horizontal and both diagonal as well as horizontal would get impacted by this change ! targets / your cursor would appear to move faster on the x axis than they should ------------- stretched is a mess generally not worth getting in to