Tribes: Ascend

 

Hey, thanks for adding it. Problem is, the sens calculation is incorrect. I have my sens measured out to about 27.3 cm without the calculator already using Mouse Sensitivity Exporter, but the calculation provided by your page is at least 5-7cm lower. (Don’t have measuring tape on me.) Tried out your calculator’s suggestion and it came out WAY TOO FAST. Any chance you could take a second look at it? My sens is as follows:

Quake Live (same as TF2 on your page as far as i know): 1.902426

PS2: .1206

Tribes Ascend (rough equivalence to the two above through trial and error with Mouse Sensitivity Exporter): 5.7480

Thanks.

 

Hey, thanks for the feedback, I’ll look into it. Tribes has some very weird calculations/bugs making the sensitivity a little unpredictable due to random packet drops.

 

Hey, thanks for adding it. Problem is, the sens calculation is incorrect. I have my sens measured out to about 27.3 cm without the calculator already using Mouse Sensitivity Exporter, but the calculation provided by your page is at least 5-7cm lower. (Don’t have measuring tape on me.) Tried out your calculator’s suggestion and it came out WAY TOO FAST. Any chance you could take a second look at it? My sens is as follows:

Quake Live (same as TF2 on your page as far as i know): 1.902426

PS2: .1206

Tribes Ascend (rough equivalence to the two above through trial and error with Mouse Sensitivity Exporter): 5.7480

Thanks.

 

I’ve looked at it now, what you are experiencing is actually unavoidable positive acceleration. The calculations are correct, but when the game gets more than 100 reports / second it starts accelerating the movement quite a lot, up to 30-40% it seems. If you move your mouse extremly slowly you should see that the calculations are correct. I’m not sure if moving this slowly is possible though, I’m doing the testing through scripts. Anyway, I’m thinking of adding an accelerated value or checkbox to the calculator as well, but I must look a bit closer on how to implement this, as acceleration is not consistent.

this is wrong tho

13.8cm/360 is 13-13.3 ingame

not 16.0697

800 dpi

I’ll check it out, but remember that Tribes has unavoidable acceleration, which is probably why your measurements don’t match the calculations.

Hi! I just tried your formula, and the results are very close to the calculator indeed! The correct formula is however a lot simpler All formulas are pulled from a database and calculated serverside as you figured out.

Unreal 3 games are pretty much all the same, but some are not affected by FOV, and some, like BioShock Infinite, are completely different.

I will make an explanation of some common formulas (like the well known Source engine one and Unreal 3) in an article later, but as an answer to you, the Unreal 3 forumla is simply:

Distance (inches) = ((65536/SENS)*(DFOV/FOV))/DPI

DFOV = Default FOV (usually 90).

Hope this helps

I will make an article explaining some of the concepts at a later point

Some formulas like the Source engine ones are well known, (360/(SENS*0.022))/DPI, but a lot of the others I have to reverse-engineer. Some are very complicated and literally takes days to get right and perfect!