lanmancz Posted April 4, 2014 Posted April 4, 2014 (edited) Did you try the Snapview.lua?PeterP has a fix for it..worked for me in 1.27.:thumbup: You can edit every snapview FOV in there, right ? I'm more interested in increasing the max "zoom in" limit (min fov) if that's possible because I use freetrack so I don't really use snapviews at all. Edited April 4, 2014 by lanmancz [sIGPIC][/sIGPIC] Gigabyte Aorus Z390 Elite, Intel i9 9900K, Fractal Design Kelvin S36, Zotac GTX 1070 8GB AMP Extreme, 32GB DDR4 HyperX CL15 Predator Series @ 3000 MHz, Kingston SSD 240GB (OS), Samsung 970 EVO 1TB M.2 NVMe (sim), Fractal Design Define R5 Black Window, EVGA SuperNOVA 750 G2, Win 10 Home x64, Thrustmaster Warthog HOTAS, Saitek Pro Flight Rudder Pedals, Thrustmaster MFD Cougar Pack, TrackIR (DelanClip), 3x 27" BenQ EW2740L, Oculus Rift S
Eldur Posted April 5, 2014 Posted April 5, 2014 Bump, anyone please figured out how to change the default min 20 deg FOV ? I'm now flying Su25A a lot and I'd really like to tweak this a little but, as mentioned earlier, editing the DCS World\Config\View\Server.lua CameraViewAngleLimits parameter doesn't do the trick. I just tried editing that in 1.2.8 openbeta which was completely fresh. And it worked, as expected. ViewSettings["Su-27"] = { Cockpit = { [1] = default_fighter_player({ CockpitLocalPoint = {7.959000,1.419000,0.000000}, CameraViewAngleLimits = {30.000000,90.000000}, })-- 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["Su-33"] = ViewSettings["Su-27"] Edited section: [1] = default_fighter_player({ CockpitLocalPoint = {7.959000,1.419000,0.000000}, CameraViewAngleLimits = {30.000000,90.000000}, })-- player slot 1 Do that for all planes. But I severely suspect this won't work in Multiplayer as the host's Server.lua is taken - and this is what I don't like here. I don't need 150° view angles, ist just useless. Maybe it looks cool once while flying through a canyon, but then it's complete nonsense. As you can see, I set my limits to 30° and 90°, and I tend to use 3 keys: Zoom in fast = 30° Reset zoom = 60° Zoom out fast = 90° This is closest to what I'm used to after flying Il-2 for over a decade :D I also had a slider mapped to the zoom, but I just used min, max and center position, so it's easier just to use these keys. But the whole thing gets broken if the min/max angles are different. I can understand that these are being given by the server, to prevent zoom exploiting (I won't call it cheating), as it's possible to set the min value to like 3° and have some nice virtual binoculars. Actually, I did exactly that back in LOMAC and FC1 when flying the A-10, because the real crews also use(d) binocs. And it's not easy to find things nevertheless, so I don't see it as a real advantage (maybe for being able to see if it's a Gundish or something else from like 5-10mi, but it has never been advantageous in air-air engagements for me at all), more a convenience thing. I think the best place for this setting would be in the menu where all the other settings are set. And there, we could have hard-coded limits like no less than 20° and no more than 150° so noone can exploit it.
Recommended Posts