Razor18 Posted March 21, 2017 Share Posted March 21, 2017 Entering the cockpit (waiting until "zoom out" sequence ends), this is the default FOV I can't increase. I'm using Track IR. I can pause Track IR, and press RShift+RCtrl+Numpad /, FOV (or seat position) can't be pulled back any further. I can go closer to the instrument panel, but can't go back out more than this. As soon I unpause Track IR and press TIR Reset, FOV jumps back to this. Tried to delete Snapwievs.lua before adjusting, no joy either. Any advise? Link to comment Share on other sites More sharing options...
Rudel_chw Posted March 21, 2017 Share Posted March 21, 2017 Hi, There is a parameter that establishes the internal cockpit movement limits ... you can customize it by using Notepad++ (dont use Windows Notepad) ... the file is in your Saved Games\DCS\Config\View and its called Server.lua Within is a section for the Ka-50, that begins with this line: ViewSettings["Ka-50"] = { Within this section, this is the line that adjust the limits: limits_6DOF = {x = {-0.300000,0.450000},y ={-0.500000,0.200000},z = {-0.650000,0.650000},roll = 90.000000}, The one that established the front to back movement limits is Z= ... try my values and you will see the difference :) Backup the file before editing, just to be safe :D 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 More sharing options...
Razor18 Posted March 22, 2017 Author Share Posted March 22, 2017 (edited) Thanks for the help, but nothing changed. Even after deleting Snapviews.lua (Snapview saving being enabled on GUI). Any other suggestion? I overwrote the values with Windows Notepad tough, but I don't think this is the problem... Edited March 22, 2017 by Razor18 added content Link to comment Share on other sites More sharing options...
Rudel_chw Posted March 22, 2017 Share Posted March 22, 2017 Thanks for the help, but nothing changed. Even after deleting Snapviews.lua (Snapview saving being enabled on GUI). Any other suggestion? I overwrote the values with Windows Notepad tough, but I don't think this is the problem... It's very strange, my current normal FOV on the Ka-50 is this: and this is when I do a zoom out: I've had bad experiences using Windows Notepad to edit lua files, perhaps you should try again with Notepad++ .. its free and easy to use. Cheers 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 More sharing options...
The_Nephilim Posted March 22, 2017 Share Posted March 22, 2017 yes you have to use NotePad++ you can also edit this line: CameraViewAngleLimits = {20.000000,120.000000}, 120.0 to whatever you want I use 130.0.. this is under KA.50 in the server.lua.. ASRock Z590 Phantom Gaming 4/AC / Intel i7 10700K @ 5.1Ghz / Noctua DHS-14 Heatsinkw/Fan / Samsung 970plus m.2 1TB / eVGA FTW3 2080Ti / RipJaws - 64GB RAM @3200 / SoundBlaster Z / Reverb G2 VR / ThrustMaster HOTAS Cougar & MFD's / Buttkicker Gamer 2 Link to comment Share on other sites More sharing options...
Razor18 Posted March 22, 2017 Author Share Posted March 22, 2017 Thank You Guys, but @Naephilim: this is exactly what I have now for CameraAngleLimits, @Rudel: I can zoom out same as your image shows it with my Track IR leaning back, but when I press Track IR Center, it reverts back to the same relatively close up view as in my attached image. And can't pull back FOV any more w/ RShift+RCtrl+NP /. Link to comment Share on other sites More sharing options...
Deezle Posted March 22, 2017 Share Posted March 22, 2017 FOV is controlled with the zoom function, not your physical head position in the pit. Intel 9600K@4.9GHz, Asus Z390, 32GB DDR4, EVGA RTX 3070, Custom Water Cooling, 970 EVO 1TB NVMe 34" UltraWide 3440x1440 Curved Monitor, 21" Touch Screen MFD monitor, TIR5 My Pit Build, VKB Gunfighter Pro w/WH Grip, TMWH Throttle, MFG Crosswinds W/Combat Pedals, Cougar MFDs, Custom A-10C panels, Custom Helo Collective, SimShaker with Transducer Link to comment Share on other sites More sharing options...
Razor18 Posted March 22, 2017 Author Share Posted March 22, 2017 Except if you assign your Track IR to Zoom function instead of Axis Z in the Control settings. Works like a charm in A-10C, and can also adjust default viewpoint in A-10C, where my view jumps back all the time, when centering Track IR. Can adjust in Ka-50 too back and forth, just the whole adjustment zone is too close to the instrument panel. Farthest back as you see it on my initial attachment, and can only go closer, to literally "my nose touching the HUD" position. Link to comment Share on other sites More sharing options...
Rudel_chw Posted March 22, 2017 Share Posted March 22, 2017 @Rudel: I can zoom out same as your image shows it with my Track IR leaning back, but when I press Track IR Center, it reverts back to the same relatively close up view as in my attached image. And can't pull back FOV any more w/ RShift+RCtrl+NP /. Hi again, I went to check my facts, and found that for some reason the values of the Server.Lua located within my Saved Games folder are not being taken into account by the game (... its strange, because I remember that previously they did were taken into account; perhaps a recent DCS update has changed this behaviour) Instead, I edited (with Notepad++) the Server.lua file located on Program Files/Eagle Dynamics/DCS/Config/View ... and used these values for the Ka-50: limits_6DOF = {x = {-0.350000,0.350000},y ={-0.250000,0.250000},z = {-0.350000,0.350000},roll = 90.000000}, I tried them and now can move my virtual head all over the place :) ... please backup the file and then try it. Cheers 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 More sharing options...
firmek Posted March 22, 2017 Share Posted March 22, 2017 Hi again, I went to check my facts, and found that for some reason the values of the Server.Lua located within my Saved Games folder are not being taken into account by the game.... That may indicate an error (syntax?) in the file. Server.lua in SavedGames folder works fine for Ka-50. F/A-18, F-16, F-14, M-2000C, A-10C, AV-8B, AJS-37 Viggen, F-5E-3, F-86F, MiG-21bis, MiG-15bis, L-39 Albatros, C-101 Aviojet, P-51D, Spitfire LF Mk. IX, Bf 109 4-K, UH-1H, Mi-8, Ka-50, NTTR, Normandy, Persian Gulf... and not enough time to fully enjoy it all Link to comment Share on other sites More sharing options...
Rudel_chw Posted March 22, 2017 Share Posted March 22, 2017 That may indicate an error (syntax?) in the file. Server.lua in SavedGames folder works fine for Ka-50. OK, you are probably right ... I will rebuild the file and try again :) 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 More sharing options...
The_Nephilim Posted March 23, 2017 Share Posted March 23, 2017 that is weird I just tried adjusting with the lua it did not move.. I think ED changed where we set that again.. they did it in the past or either they locked us out to make FOV changes.. this I would like to know as I like a Wider FOV.. ASRock Z590 Phantom Gaming 4/AC / Intel i7 10700K @ 5.1Ghz / Noctua DHS-14 Heatsinkw/Fan / Samsung 970plus m.2 1TB / eVGA FTW3 2080Ti / RipJaws - 64GB RAM @3200 / SoundBlaster Z / Reverb G2 VR / ThrustMaster HOTAS Cougar & MFD's / Buttkicker Gamer 2 Link to comment Share on other sites More sharing options...
Isegrim Posted March 23, 2017 Share Posted March 23, 2017 Do you guys use Track ir Z as Zoom axis? If yes this is where the problem comes from. "Blyat Naaaaa" - Izlom Link to comment Share on other sites More sharing options...
Razor18 Posted March 23, 2017 Author Share Posted March 23, 2017 Do you guys use Track ir Z as Zoom axis? If yes this is where the problem comes from. I do, but very same method works flawlessly in A-10C as mentioned before. When I edited the .lua as described before, then I saw change in default point of view after starting. After the usual "zoom out then jump back" sequence, I found my head much closer to the dashboard, and could also adjust it, in and out, but as soon as I centered my Track IR, it jumped back to the position as shown on my initial screenshot attached. Link to comment Share on other sites More sharing options...
The_Nephilim Posted March 23, 2017 Share Posted March 23, 2017 Do you guys use Track ir Z as Zoom axis? If yes this is where the problem comes from. Hi Isegrim, I had mouse Z on Zoom Axis and cleared it and the view worked like it should so yes this is probally the trouble we had as it still can be able to change FOV with the line I said.. Thank you for this info.. ASRock Z590 Phantom Gaming 4/AC / Intel i7 10700K @ 5.1Ghz / Noctua DHS-14 Heatsinkw/Fan / Samsung 970plus m.2 1TB / eVGA FTW3 2080Ti / RipJaws - 64GB RAM @3200 / SoundBlaster Z / Reverb G2 VR / ThrustMaster HOTAS Cougar & MFD's / Buttkicker Gamer 2 Link to comment Share on other sites More sharing options...
Rudel_chw Posted March 23, 2017 Share Posted March 23, 2017 That may indicate an error (syntax?) in the file. Server.lua in SavedGames folder works fine for Ka-50. You are correct ... my file was somehow corrupt. Changing the 6DOF limits gives me a little more leeway when moving my virtual head inside the cockpit, as this short video shows: On 0:06 the zoom is reset to no zoom, thereafter I'm only moving my head, not touching the zoom at all :) Most planes have 6DOF just fine by default, but I've found that the Ka-50, the F-5 and the Mirage 2000, do benefit from a bit of manual tune-up :D Cheers. 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 More sharing options...
Razor18 Posted March 23, 2017 Author Share Posted March 23, 2017 Anything for me to utilize regarding my original issue? :-) Link to comment Share on other sites More sharing options...
The_Nephilim Posted March 24, 2017 Share Posted March 24, 2017 Anything for me to utilize regarding my original issue? :-) Do like I did remove anything from ZOOM Axis in the Controls section under Axis.. It works for me know like it used too.. I had mouse Z in Zoom Axis.. I removed it and the FOV I selected in Camerview works now like it should.. ASRock Z590 Phantom Gaming 4/AC / Intel i7 10700K @ 5.1Ghz / Noctua DHS-14 Heatsinkw/Fan / Samsung 970plus m.2 1TB / eVGA FTW3 2080Ti / RipJaws - 64GB RAM @3200 / SoundBlaster Z / Reverb G2 VR / ThrustMaster HOTAS Cougar & MFD's / Buttkicker Gamer 2 Link to comment Share on other sites More sharing options...
Recommended Posts