Jump to content

Arena Breakout: Infinite

Hipfire is added, aims coming soon!
Read more...

Project L33T

See the game notes for instructions on how to disable smoothing.
Read more...

Twilight Town: A Cyberpunk FPS

Just added.
Read more...

Contain

See the game notes for instructions on how to disable smoothing.
Read more...

Vomitoreum

Just added.
Read more...

Unreal Tournament 4


DPI Wizard

Now added!


User Feedback

Recommended Comments



The calculator for UT4 is not correct anymore.

 

A lot has been fixed regarding FOV and mouse input in the last weeks. Would be nice if it gets an update :) Also: Where is UT99? :D

Link to comment
  • Wizard

Hey, did you manage to re-analyze UT4? Its the game i need this awesome site for the most :)

Stupid question, but where do I find the alpha releases? Do I need dev kit access?

Link to comment

Stupid question, but where do I find the alpha releases? Do I need dev kit access?

 

You can download the Unreal Engine Launcher and if you have a UnrealTournament.com forums account, the game will show in the launcher, from there its just a click to install the newest build :)

Link to comment
  • Wizard

the distance calculator doesn't work for me. "Recommended new max DPI: 87550 DPI"

I see there's an error, searching for the root cause now!

Link to comment

Hey, thanks for looking into it but it still seems wrong. About 5cm off. Setting everything in advanced mode with the right FOV and resolution and everything and trying to get 35 cm for 360° but testing the setting it spits out ingame gives me about 30cm for 360°.

 

Same test with other games is on point though. Something isn't right :(

Edited by rePete
Link to comment
  • Wizard

Hey, thanks for looking into it but it still seems wrong. About 5cm off. Setting everything in advanced mode with the right FOV and resolution and everything and trying to get 35 cm for 360° but testing the setting it spits out ingame gives me about 30cm for 360°.

 

Same test with other games is on point though. Something isn't right :(

Yeah, there's a problem with the FOV portion of the calculation. I know what's wrong, just need a bit of programming to fix it!

Link to comment
  • Wizard

Hey, thanks for looking into it but it still seems wrong. About 5cm off. Setting everything in advanced mode with the right FOV and resolution and everything and trying to get 35 cm for 360° but testing the setting it spits out ingame gives me about 30cm for 360°.

 

Same test with other games is on point though. Something isn't right :(

This is now fixed, and is 100% correct :)

Link to comment
  • Wizard

Think this is broken again seems vastly off the mark.

Tested with the latest release now, and it seems to be right on the spot still.

 

Be sure you are using the right calculation, as there is one for the in-game setting, and one for the setting in the config file! :)

Link to comment
Guest

Posted (edited)

UT feels off for me too.. I can do a 360 turn in UT with less distance.

 

1800 DPI

 

Is this the right conversion ? I set in both game/config.

 

Current Game
 

Quake Live - Hipfire
Sensitivity: set sensitivity "1.25"
 360° rotation: 7.2727 inches
 Discrepancy: 0 inches
 Actual HFOV: 115.63 degrees 2.018186 radians
 Config HFOV: 100 degrees 1.745329 radians
 VFOV: 83.58 degrees 1.458775 radians
 HFOV Ratio: - 2.593378 ratio
 
New
  
Unreal Tournament 4 - Hipfire (in-game)
Sensitivity: Mouse Sensitivity 1.025579
 360° rotation: 7.2727 inches
 Discrepancy: 0 inches
 Config FOV: ConfigDefaultFOV=100
 VFOV: 67.67 degrees
 
Unreal Tournament 4 - Hipfire (file)
Sensitivity: AxisConfig=(AxisKeyName="MouseX",AxisProperties=(DeadZone=0.000000,Sensitivity=0.014807,Exponent=1.000000,bInvert=False))
 360° rotation: 7.2729 inches
 Discrepancy: 0.0002 inches
 Config FOV: ConfigDefaultFOV=100
 VFOV: 67.67 degrees
Edited by jolty
Link to comment
  • Wizard

Thanks, found the error. There is a problem with the FOV portion of the calculation (again!). The formula is correct, but it's using the wrong FOV value. Looking into it now.

Link to comment

Thanks, found the error. There is a problem with the FOV portion of the calculation (again!). The formula is correct, but it's using the wrong FOV value. Looking into it now.

Awesome thanks alot.

Link to comment



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...