FOV and Sensitivty
Lax
Join Date: 2012-11-21 Member: 172731Members
Join Date: 2012-11-21 Member: 172731Members
Comments
Agree completely that sliders are useless compared to a definable value.
Didn't find a folder named "Roaming", but I found the system_options.xml in "%appdata%\Natural Selection 2"
No sensitivity.
All what's in there for fov is<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1--><fov-adjustment>1.000000</fov-adjustment><!--c2--></div><!--ec2--> which just changes to<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1--><fov-adjustment>0.000000</fov-adjustment><!--c2--></div><!--ec2-->when you set the slider all the way down.
Didn't know each lifeform had a different FOV, would you happen to have the values?
Also would setting the FOV adjustment to 0.000000 be default?
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->Default = 90°
Skulk = 105°
Gorge/Exo = 95°
Lerk = 100°<!--c2--></div><!--ec2-->
The adjustment slider adds up to 20° on top of that.
The resulting value is then converted into a vertical FoV based on a 4:3 aspect ratio and back into a corresponding horizontal FoV value based on the actual aspect ratio of your resolution. This means that 16:9 and 16:10 users will get even higher FoVs while 5:4 users will get a bit less.
For example, the default FoV (90°) will be anywhere between 106° and 125° on a 16:9 monitor based on the FoV slider, while the skulk's FoV will range from 120° to 137°.
The sensitivity value can be seen and set in game by using the 'i_sensitivity x' console command (leave the x out to see what your current value is).
The reason why many things do not have console variables in NS2 is that it takes time to implement (especially if you keep changing stuff around) and does not help development workflow as most things can be changed on the fly with Lua hotloading. In other games you need the console commands to actually try stuff out during development, but in NS2 it's just not necessary and leaves less time for more important things.
Also yes, sliders are useless, let us use a integer please.
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->Default = 90°
Skulk = 105°
Gorge/Exo = 95°
Lerk = 100°<!--c2--></div><!--ec2-->
The adjustment slider adds up to 20° on top of that.
The resulting value is then converted into a vertical FoV based on a 4:3 aspect ratio and back into a corresponding horizontal FoV value based on the actual aspect ratio of your resolution. This means that 16:9 and 16:10 users will get even higher FoVs while 5:4 users will get a bit less.
For example, the default FoV (90°) will be anywhere between 106° and 125° on a 16:9 monitor based on the FoV slider, while the skulk's FoV will range from 120° to 137°.
The sensitivity value can be seen and set in game by using the 'i_sensitivity x' console command (leave the x out to see what your current value is).
The reason why many things do not have console variables in NS2 is that it takes time to implement (especially if you keep changing stuff around) and does not help development workflow as most things can be changed on the fly with Lua hotloading. In other games you need the console commands to actually try stuff out during development, but in NS2 it's just not necessary and leaves less time for more important things.<!--QuoteEnd--></div><!--QuoteEEnd-->
wait.... so marine is 90fov with the slider all the way to the left?
Given that our FOV isn't constant, I'm not sure exactly what you'd want in a console command. but if you have a simple idea and if I have time I'll put it in.
Given that our FOV isn't constant, I'm not sure exactly what you'd want in a console command. but if you have a simple idea and if I have time I'll put it in.<!--QuoteEnd--></div><!--QuoteEEnd-->
Sorry for the late response.
I was just curious as to what my FOV was, maybe a number would pop up when you highlight the slider or just a number next to it.
Or if it was a console command just something like "fov 90", and it would just put the slider at 0.000000. This gives the person assurance that the fov is 90 without them adjusting the slider and wondering what it's really set at.
As of right now you can see the number of your sensitivity by typing "i_sensitivity" in console and change it by putting a number after it. (ex. "i_sensitivity 5")
You can also do this with acceleration by typing "i_accel" and change it the same way you change your sensitivity.
From what i'm told you should always use Raw Input if the game has it (unless of course you use accel and it doesn't allow you that option). It's more consistent and responsive because your mouse movements pass directly to the game instead of your OS.
Personally I like the same sensitivity for FPS because I play it a lot, it feels a lot better when you know moving your hand a certain distance will always put you at a certain part of the screen, but as with all sensitivity options they are preference.