January 23Jan 23 Author Wizard 3 minutes ago, drawdel said: do you mean that 0.75 ADS mimics the screen distance sensitivity of hipfire CS? Shouldn't it simply give a number for 1:1 within marvel rivals? For example if you enter your hipfire sens in the "convert from" section, it tells you your OW widow ADS should be 37.89 and your CS AWP first scope should be 0.818933, etc. For marvel rivals currently it just says 1.00 for every ADS sensitivity which must be false. Rivals uses MDV 0% to scale the sensitivity, which matches the default setup of the calculator. This is why you get 1.0 if you convert from Rivals itself or a game with the same hipfire FOV, which is correct. If you convert from CS2, you convert from a different FOV, which is why the scope sensitivity is different, it now matches the hipfire sensitivity and FOV in CS2 instead of Rivals. Join the community on Discord!
January 23Jan 23 40 minutes ago, DPI Wizard said: Rivals uses MDV 0% to scale the sensitivity, which matches the default setup of the calculator. This is why you get 1.0 if you convert from Rivals itself or a game with the same hipfire FOV, which is correct. If you convert from CS2, you convert from a different FOV, which is why the scope sensitivity is different, it now matches the hipfire sensitivity and FOV in CS2 instead of Rivals. Does this imply that if I find black widow scope too fast on 1.00, really what's happening is my hipfire is also too fast and I haven't really noticed? My hipfire/look should be monitor distance instead of 360° distance?
January 23Jan 23 Author Wizard 59 minutes ago, drawdel said: This is what I mean The aim sensitivity for all these will be different, ideally you should only use one game as a source and select the game you are converting to in the "Convert to" section. Join the community on Discord!
March 6Mar 6 @DPI Wizard why do you think the sensitivity increases when you cut on "center mouse in background" and could you add that option in the converter as well.
March 6Mar 6 Author Wizard 25 minutes ago, Angelofthefallen said: @DPI Wizard why do you think the sensitivity increases when you cut on "center mouse in background" and could you add that option in the converter as well. This option causes acceleration for some reason (i.e. the sensitivity is not accurate), so it has to be turned off. Join the community on Discord!
March 18Mar 18 @DPI Wizard Hi, Any idea why enabling raw input setting causes mouse movement to feel slower? my friends and I have confirmed the same experience, they all thought it felt different with it on compared to without. Does it change the sensitivity somehow or does it resolve mouse smoothing issues that were previously there, because it's almost certainly not the same feel. Thank you
March 18Mar 18 Author Wizard 1 hour ago, AAtheaimer said: @DPI Wizard Hi, Any idea why enabling raw input setting causes mouse movement to feel slower? my friends and I have confirmed the same experience, they all thought it felt different with it on compared to without. Does it change the sensitivity somehow or does it resolve mouse smoothing issues that were previously there, because it's almost certainly not the same feel. Thank you Some options like "center mouse in background" caused acceleration, so if they had this on then turning raw input on will make the mouse slower (but correct and accurate). Join the community on Discord!
March 18Mar 18 Author Wizard Just now, Angelofthefallen said: @DPI Wizard So we should have on raw input and center mouse in background? Raw input yes. Center in the background, now that raw input fixes the acceleration issues with this setting, I say have it on as it is meant to prevent negative acceleration in certain cases. Join the community on Discord!
April 14Apr 14 I would like to report something that I found about Marvel's mouse input behavior.When using kovaak's sensitivity tester, the distance of raw input off and on are exactly the same.When I tested using physical mouse distance across my pad, raw input off is significantly faster. (1.5 800 dpi cs2 to 1.86 800 dpi) the distance seemed consistent enough, but I am subject to human error.edit: Disabling center mouse on background cancelled the behavioredit2: rinput off + mouse center on = faster. rinput off + mouse center off = the same Edited April 14Apr 14 by SeikoPotato
April 14Apr 14 4 hours ago, SeikoPotato said:I would like to report something that I found about Marvel's mouse input behavior.When using kovaak's sensitivity tester, the distance of raw input off and on are exactly the same.When I tested using physical mouse distance across my pad, raw input off is significantly faster. (1.5 800 dpi cs2 to 1.86 800 dpi) the distance seemed consistent enough, but I am subject to human error.edit: Disabling center mouse on background cancelled the behavioredit2: rinput off + mouse center on = faster. rinput off + mouse center off = the sameidk why for me rinput off feels way better when it should be the opposite
August 12Aug 12 why does the sensitivity feel so slow when raw input is on? but a lot better when its off? what do you recommend players should do? what settings to make the aim feel natural?
August 12Aug 12 Author Wizard 1 hour ago, Angelofthefallen said:why does the sensitivity feel so slow when raw input is on? but a lot better when its off? what do you recommend players should do? what settings to make the aim feel natural?The calculations should be correct for raw input on, if you turn off you will get a lot of acceleration. Join the community on Discord!
Create an account or sign in to comment