Cockpit View Angle settings in the GUI

Hi - It's me again! :)

- encouraged by Viper I decided to open this wish-thread

>>> http://forums.eagle.ru/showthread.php?p=1530794#post1530794

I ask for a function to manipulate the View angles settings directly in the GUI instead of fiddling around with the

DCS World\Config\View\SnapViewsDefault.lua

or have to set-up own snap-views while the simulation is running.

(there are many,many threads of people asking where these functions are hidden).

What I have in mind should look similar like this following edited screen-capture and should be available for each plane separately - I think its self-explanatory but feel free to ask for details:

Let me explain - what is working nice on a 1280x1024 screen can look awful at 2560x1440 - and much worse and unusable at a Triple head setting.

Also please think at all the customers that use a second screen with Helios and MFCD exports...

- this is when the Vertical View Angel slider comes into play -

... they may want to look a little more up - as they don't need having the half screen filed with the cockpit avionics.

That's why they have their exports for.

I hope you catch my point and see the benefit in this.

:)

Edit:

this relates :

Here are some tests and a explanation:

Would someone please be so kind as to post before and after screenshots as per my previous post detailing why the procedure leads to an unacceptable result, keeping in mind a resolution greater than 1920x1200 (as it has been shown to be favourable on said resolution and I am assuming will stay so on lesser too. If not why not, with attendang screenshots please) with a single-monitor setup which I assume is the more generally prevalant amongst the majority of users.

 

 

Zoom in to out DCS World 1.2.0 A-10C.txt :

Ten tests of zoom "in" to "out" at mission start with time duration

Tests where made with DCS:World with the default view angle limits and snapviewsettings of the A-10C.

 

 

1a before 1024x768

1b after 1024x768

1 seconds - 4:3

 

2a before 1280x1024

2b after 1280x1024

0 seconds - 5:4

 

3a before 1360x768

3b after 1360x768

4 seconds - 16:9

 

4a before 1400x1050

4b after 1400x1050

1 second - 4:3

 

5a before 1680x1050

5b after 1680x1050

5 seconds - 16:10

 

6a before 1920x1080

6b after 1920x1080

4 seconds - 16:9

 

7a before 1920x1200

7b after 1920x1200

5 seconds 16:10

 

8a before 2560 x 1440

8b after 2560 x 1440

4 seconds - 16:9

 

9a before 3840 x 1024

9b after 3840 x 1024

7 seconds - 15:4 (3x 5:4)

 

10a before 5760 x 1080

10b after 5760 x 1080

10 seconds - 16:3 (3x 16:9)

 

 

15-08-2012

 

-PeterP

Download: http://www.mediafire.com/?yxqf62a1qji68kk (9.7 MB)

and further:

 

Ta Peter

 

OK - Humour me for a second: Apart from the obvious problem that it causes with 3840 x 1024 and 5760 x 1080 (which I am sure falls into the very lower minority of users bracket), what exactly is the problem for the majority of users, apart from a couple of seconds wait? How does one justify allocation of valuable Dev time to a feature that on the face of it does not need change/has little benefit?

 

Don't get me wrong: I'm neither for or against. I am however at a loss as to how to formulate a constructive and more importantly, a persuasive argument to put to the devs in requesting a feature-change.

 

 

 

I pull out the 16:9 example - please use my attached screens to compare and bring them to full-screen at you Monitor or use also the 1:1 pixel-size to understand fully what follows:

 

It's like this:

 

on a 16:9 1360x768

the actual zoom level is at the edge what is usable during a mission - you don't want to zoom out any further in normal use as the HUD becomes to fuzzy/small to read properly. - you will end up often to change your zoom/FOV during combat employment.

 

on 16:9 1920x1080

it is OK - HUD is good readable and you can make out details in the terrain without excessive use of zoom/FOV.

 

 

on 16:9 2560x1440

you will have the feeling that your head is in the HUD.

You want to zoom out further to a FOV of around 120° (instead of the default) the HUD will be as good readable as on 1920x1080 but you will profit from the higher immersion and situation awareness - you simply have enough pixel to "spend".

 

 

So I think what the people bugs most is that most of them don't know how to edit the Default [KP-Enter] FOV/set up their own cockpit view - to get instantly to their preferred FOV and they simply wait first once that the image has stabilised and than have to adjust their FOV to a value that they can use.

 

Excellent suggestion.

Rich

I'd like this.

I'd add a tick box to that for enabling the saving of Snapviews too.

Nate

+1

I would agree with all of the above, but would be happy with a 'Guide to DCS Configuration Lua Files' from the devs. ;)

I would agree with all of the above, but would be happy with a 'Guide to DCS Configuration Lua Files' from the devs. ;)

...well - that's another wish....;)

feel free to post/subscribe here :

Annotation in frequently user-changed Files

I think that comes close to your wish.

:)

Here here!

Or is that Hear hear!

Either way, let it be so ED.

Word.

I'd add a tick box to that for enabling the saving of Snapviews too.

 

Nate

AMEN!

I'd like...

I like your suggestion PeterP! That's what I ask for:smilewink:

'Guide to DCS Configuration Lua Files' is a good idea.

It sorts out the "advanced" users needs and keeps things uncomplicated for the newbies

Yes - and adding the possibility to do a walk-around before entering the cockpit is a good idea too.

...

But it is not the topic of this wish.

As I wrote already Cichlidfan in post #7:

Want to make yourself heard and reach the DEVs - open a appropriate wish with a meaningful Title.

Most of the Devs are native Russian speaker and I wouldn't expect them to catch up every single post in the "wish" - I would considering myself lucky if they read the first 10 postings.

To make my self clear:

Everyone is free to post more wishes in another "wish" thread... but you shouldn't expect that this get noticed by the Developers when it is not directly relating to the thread topic.

further:

I will catch up some of the already mentioned suggestions and edit posting #1 to interoperate them and bump this thread every time a new DCS version is released and don't have any of this wishes included.

+1

Regards

Terrorvogel

Extremely well presented. I would love for this feature to be added!

For all that stumble across this thread and want to change some settings and don't want to wait until this "feature" is implemented in the gui:

Get a proper Editor (Notepad++) and edit it to your needs :

The min/max FOV (aka zoom) for each plane is controlled by the

DCS World\Config\View\View.lua

starting at line #124 >

CameraViewAngleLimits = {}

CameraViewAngleLimits[su_27] = {20.0, 120.0} -- {Min°, Max°}

...

The Vertical View angle is controlled in

DCS World\Config\View\SnapViewsDefault.lua and/or the SnapViews.lua if you have set

UseDefaultSnapViews = false in the View.lua

And this list helps you to identify the cockpit snap-views "[?][13]" for each plane:

taken from the View.lua line #8 =

PlaneIndexByType = -- indices in snap views table

{

[su_27] = 1,

[su_33] = 2,

[su_25] = 3,

[su_25T] = 4,

[su_39] = 4,

[MiG_29] = 5,

[MiG_29G] = 5,

[MiG_29C] = 5,

[MIG_29K] = 6,

[A_10A] = 7,

[F_15] = 8,

[KA_50] = 9,

[A_10C] = 11,

[P_51D] = 12,

A-10C

#1060

Snap[11][13]["viewAngle"] = 75 -- FOV for [KP-Enter]

#1065

Snap[11][13]["vAngle"] = -23 -- Vertical view

Ka-50

#960

Snap[9][13]["viewAngle"] = 89.777544238285 -- FOV for [KP-Enter]

#958

Snap[9][13]["vAngle"] = -15.592758472369 -- Vertical view

P-51D

#1074

local default_viewAngle = 80 -- FOV for [KP-Enter]

#1073

local default_vAngle = -9.5

Su-25T

#430

Snap[4][13]["viewAngle"] = 90.0 -- FOV for [KP-Enter]

#435

Snap[4][13]["vAngle"] = -18.382137298584 -- Vertical view

And so on...