New default FoV

[mkiii]

I don't really understand the problem, as long as you're using an axis you can set any max fov you want up to the limit just by changing the slider saturation. All this changes is how people with button zoom will have to deal with it.

 

Well I hope that you never have to "Deal with it". I get the feeling that anyone not using a wide screen setup seems to think that those who are, are getting above themselves or cheating in some way. Get over it guys, we are not all 15 year olds with no cash. Sometimes we want a decent setup, and have scrimped enough to buy more than one monitor ;)

 

I believe that the main problem is where the middle is rather than the min or Max.

 

The default FOV is usually 20 to 140, which gives a middle fov of 80 degrees. This is Fine on a single monitor, but this means that your face is up against the HUD in triple monitor setups.

 

For example, on my setup, a fov of about 137 to 140 degrees gives a fairly undistorted view, but to get that as the middle point (since I use a Warthog throttle slider - which is most stable at mid point - either side of that can cause jitter), the min and max need to be equidistant on either side, so assuming that a max FOV is no more than 170 to be sensible, then the min can be no more than 110 degrees. This works for me (I use 115 to 165) to give 140 mid range. Any tiny tweaks can be done in the lua or by setting a curve in the axis for the slider. Having said that, why on earth in the 21st century are we still having to tweak obscure script files to make this bleeding thing work? Come on Devs add options to the sodding GUI.

[Deezle]

I do this for all aircraft to get the proper default zoom level. Easy peasy.

 

[firmek]

Well I hope that you never have to "Deal with it". I get the feeling that anyone not using a wide screen setup seems to think that those who are, are getting above themselves or cheating in some way. Get over it guys, we are not all 15 year olds with no cash. Sometimes we want a decent setup, and have scrimped enough to buy more than one monitor ;)

 

I believe that the main problem is where the middle is rather than the min or Max.

 

The default FOV is usually 20 to 140, which gives a middle fov of 80 degrees. This is Fine on a single monitor, but this means that your face is up against the HUD in triple monitor setups.

 

For example, on my setup, a fov of about 137 to 140 degrees gives a fairly undistorted view, but to get that as the middle point (since I use a Warthog throttle slider - which is most stable at mid point - either side of that can cause jitter), the min and max need to be equidistant on either side, so assuming that a max FOV is no more than 170 to be sensible, then the min can be no more than 110 degrees. This works for me (I use 115 to 165) to give 140 mid range. Any tiny tweaks can be done in the lua or by setting a curve in the axis for the slider. Having said that, why on earth in the 21st century are we still having to tweak obscure script files to make this bleeding thing work? Come on Devs add options to the sodding GUI.

Setting a default FOV in a way that it middle slider position (Warthog has a detent there) is quite easy. You'll need the "server.lua" file placed in user folder.

Now edit the file and:

1. find gCameraViewAngleLimits

2. set the min/max values in a way that your required default FOV is exactly in between of them. For example if you want a default FOV 140, set max to 170 then min 110 (default - (max-default)). The line should be:

local gCameraViewAngleLimits = {110.000000, 170.000000}

 

Min FOV = max zoom-in. 110 will not allow to zoom-in a lot so you may need to increase the max value to be able to zoom-in more and keep the default FOV at center. However, I think there is also some hard limit for max FOV value.

 

3. find "SnapViews.lua" file in user folder.

Edit the file and find "SnapViews["MiG-21Bis"] = {" section.

In that section, locate settings at index [13]:

[13] = {--default view

viewAngle = 107.000000,--FOV

...

Change the "viewAngle" value to required default FOV. Using exampe: viewAngle = 140.00000,---FOV

 

At the end, just a suggestion. Consider giving up the zoom-out effect. Since I've got a wide screen I don't find it needed anymore. The advantages are that: it's possible to keep high zoom-in (no upper bound on zoom-out), no zoom-out effect when entering the pit (!), more precise zooming in control with the slider (full slider length). Example settings without zoom-out:

Server.lua: local gCameraViewAngleLimits = {20.000000, 140.000000}

SnapViews.lua: viewAngle = 140.00000,---FOV

 

Finally, using curves/saturation for setting zoom is a really bad idea. It'll work, more or less but: never will allow to set accurate FOV, requires a lot of trial/error and even if finally set all this fuss has to be repeated for another airplane.

[Deezle]

Finally, using curves/saturation for setting zoom is a really bad idea. It'll work, more or less but: never will allow to set accurate FOV, requires a lot of trial/error and even if finally set all this fuss has to be repeated for another airplane.

Limiting your max zoom to 110º is a bad idea. Tweaking the axis setting is easy. Whatever floats your boat I guess.

[firmek]

Limiting your max zoom to 110º is a bad idea. Tweaking the axis setting is easy. Whatever floats your boat I guess.

As I wrote, no need to limit the FOV as much as 110, those values were only examples. You can get it lower (would have to check how low). The problem is potentially only with high default FOV - as it gets close to max value (which again has to be confirmed). With FullHD you can easily keep min/default/max at 20/90/160 for middle detent on slider.

Note that by default in DCS every single module uses a different default and max/min FOV (if they use same it's a coincidence). Because of that the curve for middle detent from one module will most probably not work in others. Even if you find the curve value, the setting is "more or less" - chances of hitting exactly the precise value (140.0000 like in example) are close to 0. Another thing is that this way it's not possible to change the max/min FOV at all (ok, saturation can further limit them but not increase!).

It's not only a matter of personal preference, axis are just a limited workaround that will not set the default FOV value accurately nor allow to control fully all of the FOV settings.

The best solution would be a dedicated options in UI for setting the FOV. All underlying functionality is there and it's working in the background. This depends on ED however.

On the other hand however, once you do the setup of the files, changing the values takes a seconds - with all of the benefits of full control over your settings.

[Deezle]

As I wrote, no need to limit the FOV as much as 110, those values were only examples. You can get it lower (would have to check how low). The problem is potentially only with high default FOV - as it gets close to max value (which again has to be confirmed). With FullHD you can easily keep min/default/max at 20/90/160 for middle detent on slider.

Note that by default in DCS every single module uses a different default and max/min FOV (if they use same it's a coincidence). Because of that the curve for middle detent from one module will most probably not work in others. Even if you find the curve value, the setting is "more or less" - chances of hitting exactly the precise value (140.0000 like in example) are close to 0. Another thing is that this way it's not possible to change the max/min FOV at all (ok, saturation can further limit them but not increase!).

It's not only a matter of personal preference, axis are just a limited workaround that will not set the default FOV value accurately nor allow to control fully all of the FOV settings.

The best solution would be a dedicated options in UI for setting the FOV. All underlying functionality is there and it's working in the background. This depends on ED however.

On the other hand however, once you do the setup of the files, changing the values takes a seconds - with all of the benefits of full control over your settings.

You're making it sound like it's some kind of voodoo. For my setup, a negative curve of around 50 is good for all aircraft, takes a few seconds to tweak it and you don't have to exit the game and restart to see your changes, all while keeping the entire FOV range usable if needed.

 

I agree there needs to be more control in game, I do have to edit all the aircraft to have a max FOV of 160 for my setup, except the Mi-8 which has an FOV slider in the special options tab.

[mkiii]

Clearly it is confusing, since this has already been covered in previous posts.

 

Setting the slider curve to -39 is not going to put it at 140 degrees in the middle of its range. The default settings are (usually) 20 degrees min. to 140 degrees max, (depending on settings in server.lua or views.lua if there is one).

 

For example. The Ka-50 has a min of 20 deg and a max of 120 deg, and a middle of 70 deg, so no amount of curve setting is going to get the mid point of that range near to 140 deg UNLESS you tweak the lua files. You can get almost 120 if you set the curve to -100, but that means that there is no point to it, since all you can do is zoom in.

 

Do you see now, why we have to edit lua files?

Edited February 27, 2017 by mkiii

[Eldur]

For the people that use keys... I don't think there is a solution other than wait for an implementation of a feature like Mi-8 has.

 

I just looked into the options and saw the max FOV slider that goes from 90 to 160°. So awesome! Every module should have this as well as a minimum slider als well, ranging from 20 to, let's say 60°. ED could just take it and implement it as a general option that can't be overridden by a server. I just wonder why BST didn't add that to their other modules as well.

 

This is a prime example of "Doctor, it hurts when I do this." The answer for now is: "Then don't do that."

 

It's much better for people who need that wider FOV to have it available than it is for people that don't want it to be prevented from exceeding the FOV they want.

 

"Doctor, it hurts when I breathe." - Now what?

 

But you have a point, just how many of us use 140-160° of FOV actually? It's nice for airshows and maybe replays, but you can't see anything at that setting and the distortion kills the whole SA at once at least on a single screen. But I have to add that I never tried multi screen and just read about how it behaves here, so it seems to be very useful, if not even mandatory there as well as for those "Geordi La Forge visor" aspect ratio screens (something like 4k'ish x 1080). BST did a good job as mentioned above and with that option on each module, everyone could be happy.

 

And to get exact FOV angles on a keypress, I found a solution and described it here. Just read the "edit" part and the post linked in there. Just don't know if it's possible to exceed the given limits like having 160° when the maximum is 140°.

[blokovchan]

How you change default view, when Num5 is pressed?

I tried to modify file:03_views.lua in C:\steamc\steamapps\common\DCSWorld\Mods\aircraft\MIG-21bis\Entry,but no success.

 

I would like to have defaul view rotated down in vertical plane...

[majapahit]

How you change default view, when Num5 is pressed?

I tried to modify file:03_views.lua in C:\steamc\steamapps\common\DCSWorld\Mods\aircraft\MIG-21bis\Entry,but no success.

 

I would like to have defaul view rotated down in vertical plane...

 

 

http://en.wiki.eagle.ru/wiki/Snap_views

[blokovchan]

In video bellow man can rotate view (turn head backwards) more then default. If I turn head, I can barerly see tip of the missile, but he can see large part of the wing...

 

Where can I incraese this ''turning limit''?

 

Edited July 31, 2018 by blokovchan
typo errors

[erniedaoage]

In video bellow man can rotate view (turn head backwards) more then default. If I turn head, I can barerly see tip of the missile, but he can see large part of the wing...

 

Where can I incraese this ''turning limit''?

 

 

Go to x:\DCS World\Mods\aircraft\MIG-21bis\Entry\ and open 03_Views.lua There you can set Allow360rotation = true or just get rid of the shouldersize and set Shouldersize = 0 you have to try it out which one works best for you but i think when you enable 360 rotation you have to setup your track ir that you don't snap over your neck regularly.

[majapahit]

In video bellow man can rotate view (turn head backwards) more then default. If I turn head, I can barerly see tip of the missile, but he can see large part of the wing...

 

Where can I incraese this ''turning limit''?

 

 

 

I don't have the MIG 21

But in my

.. \Saved Games\DCS\Config\View\Server.lua

 

 

I bet you can also delete or rename this server.lua and a new one will be generated with default settings.

 

 

 

 

 

there's the list of installed addons and perhaps there is a MIG 21 added, then find:

CameraAngleLimits = {200,-80.000000,90.000000}, -- < 200 degrees)

Edited July 31, 2018 by majapahit