Roblox sensitivity is different with the updated launcher

[bread94]

Hi,

 

Firstly I'd like to apologise if I'm posting this in the wrong place. As the title suggests, the new roblox launcher has a different sensitivity scale to the old one (which is the one used in your calculator). I've tried to use percentages to calculate the different sensitivity as I know 0.1 in the old launcher is equivalent to 0.45 in the new one but I've had no success. Perhaps this is because I'm not the best at maths, I'm not sure.

I was wondering if you could update the calculator to include an option for the new roblox launcher please as I have been having to guess and measure my sensitivity manually in it for months now. It would be a massive help.

 

Here is a pictures of the new roblox for clarity.

 

[DPI Wizard]

I don't have the new UI now, so I won't be able to test.

But I had it before (it reverted to the old one for me for some reason) and have a few games added to it, so if you can check if it seems correct that would be great.

It's a new option under Location called "In-game (New UI)". A lot of games will be grayed out as they haven't been added to the new UI calculation yet.

[bread94]

6 hours ago, DPI Wizard said:

I don't have the new UI now, so I won't be able to test.

But I had it before (it reverted to the old one for me for some reason) and have a few games added to it, so if you can check if it seems correct that would be great.

It's a new option under Location called "In-game (New UI)". A lot of games will be grayed out as they haven't been added to the new UI calculation yet.

Sure. I've checked Bad Business and that is way off from what I can tell. I'll start with all my settings relevant to sensitivity:

DPI - 3200

FOV - 115

camera sensitivity - 0.1

hipfire - 89

aim sensitivity - 120

scope - 130

 

This equates to a measured 34cm for hipfire and 52cm for 1x ADS. I don't know what the scope cm/360 is - never tried to measure (probably don't have enough mousepad for it).

According to the calculator for the new UI, these settings would be in the single or low double digits which is way, way off.

I've also checked Recoil as that's another game I play and the calculator doesn't work for that. It updates my camera sensitivity in the 'Calculations' section when I change that but it doesn't update the in-game sensitivity values so you don't get any usable info from it.

I could send you my Roblox install so you get the version with the new UI though I understand you probably wont want to do that for obvious reasons.

Good luck with this and a word of advice: if you try and get this new UI version, backup your old install version first as you can't go back. Or, at least, there is no way I have found to go back.

[bread94]

6 hours ago, DPI Wizard said:

I don't have the new UI now, so I won't be able to test.

But I had it before (it reverted to the old one for me for some reason) and have a few games added to it, so if you can check if it seems correct that would be great.

It's a new option under Location called "In-game (New UI)". A lot of games will be grayed out as they haven't been added to the new UI calculation yet.

Also, when you try and calculate via distance, it doesn't get close to the distance... not sure what's going on there.

[DPI Wizard]

47 minutes ago, bread94 said:

Also, when you try and calculate via distance, it doesn't get close to the distance... not sure what's going on there.

Thanks for checking! I've hidden the new UI location now since it seems to be wrong. When I tested about a year ago you could only set a sensitivity between 0 and 10 in the new UI, without any decimals, I guess this has change now?

I don't think it's enough for you to send me your Roblox account, it will probably still launch on my install. The new/old UI separation seems to be random. I found some old guides with tips on how to enable the new one, but none of them worked here.

Either way, the config file should be the same, albeit a bit more work to edit.

[bread94]

49 minutes ago, DPI Wizard said:

Thanks for checking! I've hidden the new UI location now since it seems to be wrong. When I tested about a year ago you could only set a sensitivity between 0 and 10 in the new UI, without any decimals, I guess this has change now?

I don't think it's enough for you to send me your Roblox account, it will probably still launch on my install. The new/old UI separation seems to be random. I found some old guides with tips on how to enable the new one, but none of them worked here.

Either way, the config file should be the same, albeit a bit more work to edit.

For me the install is as follows %APPDATA%/Local/Roblox/Versions then there will be a folder in there named Versions that will have a string of letters and numbers on the end of it. And yes, you can now use decimals. My current camera sensitivity in the new UI is 0.1 and I think this will help you a lot... I've found that to be equivalent to 0.02917 in the old UI (although I should note that this number is likely off marginally by a negligible amount. As you can see from this SS, the calculator recommends a sensitivity of 90 to get 32cm/360 hipfire whereas it actually needs to be 89 in practicality. I haven't measured super precisely, just as close as I can get with reasonable effort and the naked eye.

 

 

Not my Roblox account but the actual folder I've just quoted the location of. This is the only way I can imagine there is of changing between the two versions as I have tried a bunch of methods recommended to me and that I've found by searching the internet but none have worked. I've been trying to get someone to send my their install of the old Roblox but for some reason struggling.

[DPI Wizard]

Thanks for the info! I've managed to launch the new UI now, and have updated the calculations.

So check again, it should be spot on

[bread94]

9 hours ago, DPI Wizard said:

Thanks for the info! I've managed to launch the new UI now, and have updated the calculations.

So check again, it should be spot on

It looks as though the sensitivity it gives is roundabout right but the cm it shows is wayyyy off still.

 

Also, bit of a separate note... I don't know why but most of the time, the 360 distance in practise tends to be 2-4cm lower than what it should be so for example, a calculated distance of 32cm would turn out to be 34cm. Dunno why that is but thought it worth mentioning, although apologies if this isn't the best time, while we're discussing something else. 

[DPI Wizard]

18 minutes ago, bread94 said:

It looks as though the sensitivity it gives is roundabout right but the cm it shows is wayyyy off still.

Thanks, I think I see the issue so I will work on it

Removing them until I solve it.

19 minutes ago, bread94 said:

 

Also, bit of a separate note... I don't know why but most of the time, the 360 distance in practise tends to be 2-4cm lower than what it should be so for example, a calculated distance of 32cm would turn out to be 34cm. Dunno why that is but thought it worth mentioning, although apologies if this isn't the best time, while we're discussing something else. 

If this is for every game, it's your mouse sensor that it slightly off. It's not uncommon that they are off by 5% or more, so that will impact the actual distance you move, but it will be the same for every game so it will be consistent.

Have you checked it in the DPI Analyzer?

[bread94]

14 hours ago, DPI Wizard said:

Thanks, I think I see the issue so I will work on it

Removing them until I solve it.

If this is for every game, it's your mouse sensor that it slightly off. It's not uncommon that they are off by 5% or more, so that will impact the actual distance you move, but it will be the same for every game so it will be consistent.

Have you checked it in the DPI Analyzer?

Oh, I didn't know that. interesting. I think I've tried it once before but as I recall it was hard to do it with such a high dpi, any advice?

[bread94]

15 hours ago, DPI Wizard said:

Thanks, I think I see the issue so I will work on it

Removing them until I solve it.

If this is for every game, it's your mouse sensor that it slightly off. It's not uncommon that they are off by 5% or more, so that will impact the actual distance you move, but it will be the same for every game so it will be consistent.

Have you checked it in the DPI Analyzer?

Nevermind, I've done it and my sensor is pretty much spot on. A discrepancy of 0.15%.

[DPI Wizard]

34 minutes ago, bread94 said:

Nevermind, I've done it and my sensor is pretty much spot on. A discrepancy of 0.15%.

That's really low. Although possible, are you sure you measured correctly? The point of the analyzer is not to try to move the red crosshair to the blue target, you should only care about how far you are physically moving your mouse (the target distance), then check how close you are to the target.

[bread94]

1 hour ago, DPI Wizard said:

That's really low. Although possible, are you sure you measured correctly? The point of the analyzer is not to try to move the red crosshair to the blue target, you should only care about how far you are physically moving your mouse (the target distance), then check how close you are to the target.

In that case, I've done it completely wrong hahahaha. It' hard to do something accurate because it will only let me do like 3cm at most and then that measurement is going to be off by a couple of mm +/-, that's a significant chunk of 3cm. I'll give it another whirl though and see how it goes, thanks.

[bread94]

2 hours ago, DPI Wizard said:

That's really low. Although possible, are you sure you measured correctly? The point of the analyzer is not to try to move the red crosshair to the blue target, you should only care about how far you are physically moving your mouse (the target distance), then check how close you are to the target.

You were right. It's off by about 6-7%. Is it normal to be off by about this much? Does suing a higher DPI have any effect on the overall discrepancy? Because I'd have thought a G Pro Wireless would have had a top-notch sensor given they're $100+.

 

[DPI Wizard]

3 minutes ago, bread94 said:

You were right. It's off by about 6-7%. Is it normal to be off by about this much? Does suing a higher DPI have any effect on the overall discrepancy? Because I'd have thought a G Pro Wireless would have had a top-notch sensor given they're $100+.

It's usually in the same range +/- a few tenths with different DPI levels. It is quite normal that sensors are off indeed, so what you can do is to enter 2987 as you DPI instead of 3200 in the calculator, and the distance calculations should be spot on.

[bread94]

There we go, I've upped my DPI until the calculator said I was at 3200. This should make using your calculator go a lot smoother now... no more using a tape measure to fine-tune the sens perfectly, fingers crossed. I always thought it was odd that it was off by 2cm on a website that is so accurate. Thanks for bringing this to my attention, it's a big help

[bread94]

9 hours ago, DPI Wizard said:

It's usually in the same range +/- a few tenths with different DPI levels. It is quite normal that sensors are off indeed, so what you can do is to enter 2987 as you DPI instead of 3200 in the calculator, and the distance calculations should be spot on.

Yeah, I'm gonna do that. I've found using this new higher DPI, to be incredibly difficult to adjust to so I'm gonna keep it in the current one and adjust my calculations. Thanks again