Jump to content

How to set FOV limits now?


Recommended Posts

So I've been away from DCS for a long while, and want to try out this newfangled 2.5 whatsit. Many things are new... but some old things are still there. I still hate the stupidly fisheyed default FOV limits, and want to adjust them.

 

Back in the day, I would have edited server.lua, but that no longer works. Or I would've edited the individual plane's Views.lua, but that no longer works.

 

I tried searching this forum, only to find a ton of threads from the past several years, no longer relevant.

 

Please, how do I fix this? :helpsmilie:


Edited by White Owl
broken formatting
Link to comment
Share on other sites

Yup, some "sharp" knife (if you know what I mean) decided that most view related files should be IC protected nowadays...

 

Thanks God we can still use snapviews to customize FoV, however! Create your own custom snapviews.lua, set the preferred FoV in your airplane's "default view" entry (some trial and error is going to be required it seems) and put the file in Saved Games\DCS\Config\View location, as per Skate's instruction here:

https://forums.eagle.ru/showpost.php?p=3435783&postcount=3

 

Obviously, don't forget to turn on snapviews in the game options to make this stuff work at all (been there, done that :D).


Edited by Art-J

i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.

Link to comment
Share on other sites

If you have the zoom assigned to an axis, you can limit the saturation in the response menu.

i9-13900K @ 6.2GHz oc | ASUS ROG MAXIMUS Z790 HERO | 64GB DDR5 5600MHz | iCUE H150i Liquid CPU Cooler | 24GB GeForce RTX 4090 | Windows 11 Home | 2TB Samsung 980 PRO NVMe | Corsair RM1000x | LG 48GQ900-B 4K OLED Monitor | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5

Link to comment
Share on other sites

Alright, so it's not just me forgetting how to do things. That's a little reassuring. I've never used snapviews because I use TrackIR. I'll take a look at the axis tuning, see if I can make it do what I want.

 

Thanks very much. :)

Link to comment
Share on other sites

Oh, I don't use them per se either (TrackIR here too). The idea is to enable them to get any editable file, which allows FoV customization. A workaround for defunct server.lua and views.lua files.

i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.

Link to comment
Share on other sites

  • 3 months later...

HI

 

 

I wonder how now to restric default FOV like i used it before ( edited view and lua files long time ago)

 

 

Some planes like FC planes got accurate maximum FOV but some planes got too wide view which is absurd - 140 degres instead about 100-120. It is totaly unrealisitc.

 

 

How now in 2.5 restric these FOV from 140 to 120 or 100?

 

 

I dont have axis for zoom only use buttons.

 

 

Any help?

Link to comment
Share on other sites

I think it's the server.lua in the Config\Views folder

 

I can't remember whether it's a global setting or plane-specific, though.

 

edit.....scratch that - if you just need a default FOV to bounce back to after a zoom then it's in the Snapviews.lua - each aircraft have 13 snap-views and if I remember correctly you need to edit the FOV in number 12. Also, when you first enter the cockpit you need to do a zoom and let it snap back to your desired FOV.


Edited by Lixma 06
Link to comment
Share on other sites

You can also permanently store an FOV by pressing RAlt + Numpad Enter once you have the desired zoom amount.

 

 

Will you see a change in the Snapviews.lua using the RAlt + Numpad Enter technique?

 

[13] = {--default view

viewAngle = 75.000000,--FOV

hAngle = 0.000000,

vAngle = -23.000000,

x_trans = 0.360000,

y_trans = -0.041337,

z_trans = 0.000000,

rollAngle = 0.000000,

A Co, 229th AHB, 1st Cav Div

ASUS Prime Z370-A MB, Intel Core i7 8700K 5.0GHz OC'd, RTX 3090, 32GB DDR4, 1TB SSD, Win 10

Samsung 65" 4K Curved Display (Oculus Rift occaisionally), Track IR5, VoiceAttack, Baur's BRD-N Cyclic base/Virpil T-50CM Grip, UH-1h Collective by Microhelis & OE-XAM Pedals. JetSeat & SimShaker for Aviators.

JUST CHOPPERS

 

Link to comment
Share on other sites

Will you see a change in the Snapviews.lua using the RAlt + Numpad Enter technique?

 

[13] = {--default view

viewAngle = 75.000000,--FOV

hAngle = 0.000000,

vAngle = -23.000000,

x_trans = 0.360000,

y_trans = -0.041337,

z_trans = 0.000000,

rollAngle = 0.000000,

 

It should.

 

Also, once you're happy with the FOV go back to the .lua and ensure the hAngle is set to 0.00000 or else you'll be looking slightly left or right.

Link to comment
Share on other sites

It should.

 

Also, once you're happy with the FOV go back to the .lua and ensure the hAngle is set to 0.00000 or else you'll be looking slightly left or right.

I typically adjust the snapviews.lua default manually by trial and error. Didn't know bout the R Alt - Numpad Enter deal.

Cheers.

A Co, 229th AHB, 1st Cav Div

ASUS Prime Z370-A MB, Intel Core i7 8700K 5.0GHz OC'd, RTX 3090, 32GB DDR4, 1TB SSD, Win 10

Samsung 65" 4K Curved Display (Oculus Rift occaisionally), Track IR5, VoiceAttack, Baur's BRD-N Cyclic base/Virpil T-50CM Grip, UH-1h Collective by Microhelis & OE-XAM Pedals. JetSeat & SimShaker for Aviators.

JUST CHOPPERS

 

Link to comment
Share on other sites

  • 1 year later...

This topic is more than a year old, but no answer to the actual question is given.

 

Speaking of the FOV limits I found the following. In Server.lua there is default_fighter_player function. Changing CameraViewAngleLimits in this function will affect the FOV limits for all aircraft which use this function (listed in the file).

 

To apply the changes to the other aircraft which are not listed in the file (like Spitfire, P-51D, I-16, ...) I created ViewSettings for one of them and copied the settings for the others.

 

So, in my case I the second values of CameraViewAngleLimits to 100.0

 

function default_fighter_player(t)
local res = { 
	CameraViewAngleLimits  = {20.000000,100.000000},

 

... and then added the following code at the end of file.

 

ViewSettings["SpitfireLFMkIX"] = {
Cockpit = {
[1] = default_fighter_player()-- player slot 1
}, -- Cockpit 
Chase = {
	LocalPoint      = {4.259000,3.819000,0.000000},
	AnglesDefault   = {180.000000,-8.000000},
}, -- Chase 
Arcade = {
	LocalPoint      = {-12.041000,6.419000,0.000000},
	AnglesDefault   = {0.000000,-8.000000},
}, -- Arcade 
}
ViewSettings["I-16"] = ViewSettings["SpitfireLFMkIX"]
ViewSettings["Bf-109K-4"] = ViewSettings["SpitfireLFMkIX"]
ViewSettings["P-51D"] = ViewSettings["SpitfireLFMkIX"]

 

This worked for me. :pilotfly:

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

  • 2 weeks later...
This topic is more than a year old, but no answer to the actual question is given.

 

Speaking of the FOV limits I found the following. In Server.lua there is default_fighter_player function. Changing CameraViewAngleLimits in this function will affect the FOV limits for all aircraft which use this function (listed in the file).

 

To apply the changes to the other aircraft which are not listed in the file (like Spitfire, P-51D, I-16, ...) I created ViewSettings for one of them and copied the settings for the others.

 

So, in my case I the second values of CameraViewAngleLimits to 100.0

 

function default_fighter_player(t)
local res = { 
	CameraViewAngleLimits  = {20.000000,100.000000},

 

... and then added the following code at the end of file.

 

ViewSettings["SpitfireLFMkIX"] = {
Cockpit = {
[1] = default_fighter_player()-- player slot 1
}, -- Cockpit 
Chase = {
	LocalPoint      = {4.259000,3.819000,0.000000},
	AnglesDefault   = {180.000000,-8.000000},
}, -- Chase 
Arcade = {
	LocalPoint      = {-12.041000,6.419000,0.000000},
	AnglesDefault   = {0.000000,-8.000000},
}, -- Arcade 
}
ViewSettings["I-16"] = ViewSettings["SpitfireLFMkIX"]
ViewSettings["Bf-109K-4"] = ViewSettings["SpitfireLFMkIX"]
ViewSettings["P-51D"] = ViewSettings["SpitfireLFMkIX"]

 

This worked for me. :pilotfly:

 

Yes, this thread and others gives truth that there is an issue with FOV that are easily addressed within the game interface.

 

QUESTION: What is the complete path to the "Server.ula" file you referenced here? I am looking in the path "C:\Users\Username\Saved Games\DCS" and I do not see a Server.ula


Edited by Gpruitt54
Link to comment
Share on other sites

Looks as if I stumbled upon a solution to my specific issue with Ka-50 FOV.

 

  • Starting with the file path "...\Eagle Dynamics\DCS World\Config\Views". Make a copy of the Server.ula file.

  • Open the filed named "Server.ula"

  • I located the details for the Ka-50 (See the code below)

  • The line reading "CameraViewAngleLimits = {20.000000,120.000000},". I changed the value "120.000000", to a new value of "180.000000".

  • When I restarted DCS, and started the Ka-50 module, I had a better FOV, in that I can now see the HUD and a few instruments.

 

ViewSettings["Ka-50"] = {

Cockpit = {

[1] = {-- player slot 1

CockpitLocalPoint = {3.188000,0.390000,0.000000},

CameraViewAngleLimits = {20.000000,120.000000},

CameraAngleRestriction = {false,60.000000,0.400000},

CameraAngleLimits = {140.000000,-65.000000,90.000000},

EyePoint = {0.090000,0.000000,0.000000},

limits_6DOF = {x = {-0.020000,0.350000},y ={-0.150000,0.165000},z = {-0.170000,0.170000},roll = 90.000000},

},

Link to comment
Share on other sites

  • 4 weeks later...
Any changes in the Views.lua file not permited.

After changes values CameraViewAngleLimits = {20.000000,140.000000} F/A-18C and L-39 modul are not shown in the menu of game. WTF ???

 

 

https://forums.eagle.ru/showthread.php?p=4216371#post4216371

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

..SavedGames/DCS.openbeta/config/View> Server.Lua doesn't works :mad:

 

Strange, it works fine for me :huh:

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

..and fhat is the statement and setting for L-39C and L-39ZA ??? ViewSettings["L-39C"] = ???. I cant find the config text.

 

I use these lines on my Server.lua:

 

ViewSettings["L-39C"] = {
   Cockpit = {
[1] = default_fighter_player({ CockpitLocalPoint         = {3.04, 0.68, 0.0},
        CameraAngleLimits         = {200,-90.000000,90.000000},
        limits_6DOF               = {x = {-0.05,0.2},y ={-0.5,0.1},z = {-0.25,0.25},roll = 90.000000}}),
[2] = default_fighter_player({ CockpitLocalPoint         = {1.5, 1.0, 0.0},
        CameraAngleLimits         = {200,-90.000000,90.000000},
        limits_6DOF               = {x = {-0.05,0.2},y ={-0.5,0.1},z = {-0.25,0.25},roll = 90.000000}}),
   }, -- Cockpit 
Chase = {
 LocalPoint      = {-5.0,1.0,3.0},
 AnglesDefault   = {0.000000,0.000000},
}, -- Chase 
Arcade = {
 LocalPoint      = {-21.500000,5.618000,0.000000},
 AnglesDefault   = {0.000000,-8.000000},
}, -- Arcade 
}

ViewSettings["L-39ZA"] = {
   Cockpit = {
[1] = default_fighter_player({ CockpitLocalPoint         = {3.04, 0.68, 0.0},
        CameraAngleLimits         = {200,-90.000000,90.000000},
        limits_6DOF               = {x = {-0.05,0.2},y ={-0.5,0.1},z = {-0.25,0.25},roll = 90.000000}}),
[2] = default_fighter_player({ CockpitLocalPoint         = {1.5, 1.0, 0.0},
        CameraAngleLimits         = {200,-90.000000,90.000000},
        limits_6DOF               = {x = {-0.05,0.2},y ={-0.5,0.1},z = {-0.25,0.25},roll = 90.000000}}),
   }, -- Cockpit 
Chase = {
 LocalPoint      = {-5.0,1.0,3.0},
 AnglesDefault   = {0.000000,0.000000},
}, -- Chase 
Arcade = {
 LocalPoint      = {-21.500000,5.618000,0.000000},
 AnglesDefault   = {0.000000,-8.000000},
}, -- Arcade 
}

:thumbup:

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

  • 4 weeks later...

Sorry, haven't been here for a while.

 

By default, Server.lua is in the game folder, like "X:\DCS World Beta\Config\View". But the readme.txt says:

DO NOT EDIT stock game files.
You local changes should go to C:\Users\<YOUR PROFILE>\Saved Games\DCS\Config\View\
Please, copy the file(s) to this folder (create if neccessary) and keep your changes there.

 

So you copy it to "Saved Games" and then edit.

 

I've just re-installed my OS and completely forgot about saving my configs, so now need to set up everything again :cry: :sad_2:

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...