BUG - Default field-of-view too wide at max setting

[philstyle]

The default FoV setting for the spitfire results in fish-eye when at widest FoV.

 

 

It is only possible to prevent this by fiddling with one's server.lua or view.lua settings.

However, when flying online if the server host has not also fixed their own .lua file, then all clients have to put up with the defalt setting being too wide.

 

 

This should be fixed so that the FoV is the same as other aircraft, so that we don't havew the FoV Fish-eye problem. I don't experience this problem with the P51, the F86 or the Viggen (the three other aircraft I have).

 

 

This should be a very, very easy bug to fix, given that it is only a single value in a single line of Code. It's also something that could have been tidied up months ago......

 

 

For reference, this video explains the work-around that us customers have to employ in order to fix the product currently:

[Weta43]

The default view ? Set it to what you want, then press RALT + numpad zero

[philstyle]

The default view ? Set it to what you want, then press RALT + numpad zero

 

 

 

Nein! not the default view; but rather the default max FoV angle setting.

The problem is the line in the code which governs the default max and min limits of the FoV for the spitfire. Specifically, the default MAX FoV value.

 

See the video.

DCS has a default max FoV of 140 degrees in the Spitfire. This is too wide, and causes the Fish-eye effect.

When reduced below 120 degrees, the fish-eye effect is corrected.

 

 

140 degree visual field cannot be squeezed onto a 16:9 projection withouth major warping (i.e. the fish eye).

Edited September 15, 2017 by philstyle

[SUNTSAG]

Hi All,

 

Unfortunately the fix for this is not as simple as adjusting the default FOV values. I speak as a long term user having tried many view angle options over the years that suit me and my setup.

 

Therein lies the rub.....not everyone flies using a single monitor. I myself have used a three monitor setup in the past which requires a greater value setting than the standard 20 by 140. I now fly using a single monitor to improve FPS and my current settings are 20 by 98 as that feels about right for me as I hate seeing really elongated cockpits when zoomed out fully.

 

I realise that many will have their own preferences too so adjusting the default is not necessarily the ultimate fix. What does need to happen IMHO is that those running MP servers need to take into account the potential for personal preference and delete the view folder from their zipped mission. Quite a number of the MP mission builders won't even realise that this exists or indeed the impact it has on those joining their server. They won't know it contains their own view settings in game.

 

Now I rarely fly on MP servers because of this very issue. I fly with a group and we host on line sessions on a regular basis. As a long term mission builder for this group I make sure my missions are free of view settings thus catering for everyone. It is simply frustrating to join a server and find a horrendous cockpit view that you can do nothing about.

 

My settings are contained within my saved games folder so that updates do not have an impact by reverting my preferences. So in summary this is not a bug and the majority of aircraft in DCS have the default 20 by 140 camera view. I hope all this makes sense......Cheers :thumbup:

Edited September 15, 2017 by SUNTSAG

[philstyle]

My settings are contained within my saved games folder so that updates do not have an impact by reverting my preferences. So in summary this is not a bug and the majority of aircraft in DCS have the default 20 by 140 camera view. I hope all this makes sense......Cheers :thumbup:

 

 

 

OK, true, the "fix" might be more complex than I suggested.

However, I have no problem with other aircraf besides the Spitfire, so it is clearly fine for all the others already.

 

 

In addition, this shouldn't be something we need to edit lua files to "fix".

An option to control max and mic FoV in the settings would be nice. (this being quite a complex fix I admit)

[SUNTSAG]

I agree lua adjustment should not be the answer and a dual slider option would be great that also saves the settings for all aircraft in the config folder. However that would not fix the MP sever issue unfortunately

 

As I mentioned this has been a long term issue for many of us with no resolution and I have spent many Goldilocks hours getting it "Just Right" lol

[Pikey]

yep, the viewsettings.lua being in a mission file is a killer.