Fakum Posted July 21, 2016 Share Posted July 21, 2016 Thanks, good move on setting it up with JSGME,, thanks for the tip! Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle Link to comment Share on other sites More sharing options...
Activity Posted October 6, 2016 Share Posted October 6, 2016 Here's a fix for the UH-1H co-pilot view (not gunners): ViewSettings["UH-1H"] = { Cockpit = { [1] = default_fighter_player({ CockpitLocalPoint = {0,0,0}, limits_6DOF = { x = {-0.2,0.4}, y = {-0.2,0.18}, z = {-0.2,0.8}, roll = 90}}), [2] = default_fighter_player({-- player slot 2 CockpitLocalPoint = {2.0,0.6,-1.35}, limits_6DOF = { x = {-2,2}, y = {-2,2}, z = {-2,2}, roll = 90}}), [3] = {-- player slot 3 CockpitLocalPoint = {-1.0,0.6,-1.35}, CameraViewAngleLimits = GlobalCameraViewAngleLimits, CameraAngleRestriction = {false,130.00,0.90}, CameraAngleLimits = {120,-90,15}, EyePoint = GlobalEyePoint, limits_6DOF = { x = {-0.200000,0.500000}, y = {-0.200000,0.350000}, z = {0.300000,0.800000}, roll = 90.000000}, }, [4] = {-- player slot 4 CockpitLocalPoint = {0.000000,0.000000,0.000000}, CameraViewAngleLimits = GlobalCameraViewAngleLimits, CameraAngleRestriction = {false,130.00,0.90}, CameraAngleLimits = {120,-90,15}, EyePoint = GlobalEyePoint, limits_6DOF = { x = {-0.200000,0.500000}, y = {-0.200000,0.350000}, z = {-0.800000,-0.300000}, roll = 90.000000}, }, Link to comment Share on other sites More sharing options...
TRITATUTTO Posted October 15, 2016 Share Posted October 15, 2016 Have a nice snapview settings for the FW190? AMD Phenom II x4 945 3.0ghz 8G Ram Windows 7 64bit ATI Radeon HD 5700 1G Link to comment Share on other sites More sharing options...
firmek Posted October 15, 2016 Share Posted October 15, 2016 NO ZOOM EFFECT WHEN ENTERING COKPIT - FIX!!! I've found a fix/workaround allowing to get rid of the zoom effect when spawning in the cockpit. There is one side effect which is that zooming out more than the default view is no longer possible. Zoom-in is not affected, it gets actually more precise as now the whole slider travel length is dedicated for zooming-in. The solution can be done by everyone: 1. Make sure that the default FOV set in user SnapViews is the same for all aircrafts (index [13], viewAngle value). The value can be set according to personal preferences. 2. Set the same value as the maximum allowed FOV - gCameraViewAngleLimits value in Server.lua. For convenience I've attached an updated version of the files: - HD: for 16:9, HD monitors - 90° FOV - WS: for 21:9, widescreen monitors - 107° FOV. Tested with 3440x1440 resolution. To change the FOV value to any other preferred one just run replace all "viewAngle = 90.000000" or "viewAngle = 107.000000". - MPZoom - FOV is calibrated in a way that middle position equals default FOV. It's done to match the middle detent on the TM Warthog throttle slider. This version does not fix the zoom out effect when entering the cockpit. - NoZoom - max FOV is same as default FOV, removes the zoom-out effect. It's recommended that the configuration is used by simmers knowing how to modify the view configurations. Installation: 1. Backup your original files! 2. Remove prefixes 3. copy "SnapViews.lua" and "Server.lua" to DCS folder, Config\View in user SavedGames: - 2.x alpha - C:\Users\@user_name\Saved Games\DCS.openalpha\Config\View - 1.5.x beta - C:\Users\@user_name\Saved Games\DCS.openbeta\Config\View Aircrafts included are listed below. Since I don't have/fly all of them those that are tested in 1.5 beta and 2.0 are marked with bold: A-10A A-10C F-15C Hawk Ka-50 MiG-29A MiG-29G MiG-29S P-51D TF-51D Su-25 Su-25T Su-25TM Su-27 Su-33 Mi-8MT UH-1H C-101EB M-2000C MiG-21Bis MiG-15bis F-86F SabreHD - SnapViews.luaHD-MPZoom - Server.luaHD-NoZoom - Server.luaWS - SnapViews.luaWS-MPZoom - Server.luaWS-NoZoom - Server.lua 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...
firmek Posted December 21, 2016 Share Posted December 21, 2016 Updated with Spitfire and latest changes (gunners) for Mi-8.Server.luaSnapViews.lua 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...
klem Posted December 22, 2016 Share Posted December 22, 2016 Updated with Spitfire and latest changes (gunners) for Mi-8. Thanks. TBH I thought proper neck had been incorporated into DCS. klem 56 RAF 'Firebirds' ASUS ROG Strix Z390-F mobo, i7 8086A @ 5.0 GHz with Corsair H115i watercooling, Gigabyte 2080Ti GAMING OC 11Gb GPU , 32Gb DDR4 RAM, 500Gb and 256Gb SSD SATA III 6Gb/s + 2TB , Pimax 8k Plus VR, TM Warthog Throttle, TM F18 Grip on Virpil WarBRD base, Windows 10 Home 64bit Link to comment Share on other sites More sharing options...
firmek Posted December 22, 2016 Share Posted December 22, 2016 (edited) I don't know what is the history. Long story short, the files are just a configuration of what DCS is doing, with a difference that for every single module in DCS there is a different setup of shoulder size, eye point (neck length), max/min zoom as also few other things. The benefit of using Server.lua stored in user files is that you're getting the same configuration of mentioned things for every single module. Additionally with proper synchronization of FOV and max zoom values between Server.lua and SnapViews.lua it's possible to get rid of annoying zoom-out effect when entering the cockpit. As for SnapViews.lua I'm editing it to make sure that every single module has the same default field of view (zoom). This file is really optional, actually it may be better to edit your own rather than using attached one - the instruction is in one of the posts somewhere above. Edited December 22, 2016 by firmek 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...
klem Posted December 22, 2016 Share Posted December 22, 2016 I don't know what is the history. Long story short, the files are just a configuration of what DCS is doing, with a difference that for every single module in DCS there is a different setup of shoulder size, eye point (neck length), max/min zoom as also few other things. The benefit of using Server.lua stored in user files is that you're getting the same configuration of mentioned things for every single module. Additionally with proper synchronization of FOV and max zoom values between Server.lua and SnapViews.lua it's possible to get rid of annoying zoom-out effect when entering the cockpit. As for SnapViews.lua I'm editing it to make sure that every single module has the same default field of view (zoom). This file is really optional, actually it may be better to edit your own rather than using attached one - the instruction is in one of the posts somewhere above. Yes I understand the theory. I just compared the standard files with the ProperNeck files in my Saved Games and no, it isn't incorporated into DCS. Because the ProperNeck files have always been there I was fooled into thinking it was now in DCS. Stupid Boy as they say. I don't want to use a universal FOV. With my screen layout I create individual FOVs (using RALT + 0) for each aircraft which are all very similar. They only vary because in one cockpit an instrument may be partially cut off between upper and lower screens and then I will have a similar problem in another so I set them individually. But they are all within a few degrees of eachother. klem 56 RAF 'Firebirds' ASUS ROG Strix Z390-F mobo, i7 8086A @ 5.0 GHz with Corsair H115i watercooling, Gigabyte 2080Ti GAMING OC 11Gb GPU , 32Gb DDR4 RAM, 500Gb and 256Gb SSD SATA III 6Gb/s + 2TB , Pimax 8k Plus VR, TM Warthog Throttle, TM F18 Grip on Virpil WarBRD base, Windows 10 Home 64bit Link to comment Share on other sites More sharing options...
Kenta Posted February 14, 2017 Share Posted February 14, 2017 Thanks. TBH I thought proper neck had been incorporated into DCS. I can confirm it has been "implemented" for Ka-50. But I don't see it "working" in the A-10C. Failure is the mother of all success. Link to comment Share on other sites More sharing options...
Sniper_402 Posted February 25, 2017 Share Posted February 25, 2017 (edited) I have been trying to play around with the FOV but whenI try to do a find and replace on viewAngle so as to change the vale as per the post by firmek I am not finding any entries for viewAngle. Have things changed now that we are on version 1.5.6 ? Also am I missing something or can you not set your own custom Snap views? (Sorry for what might seem a basic question but I am new to DCS) Edited February 25, 2017 by Sniper_402 Rig:- NZXT H 440 Razer Special Edition Case - Asus Maximum VIII Formula MB -Intel i7 6700K @4.6Ghz - 64GB Corsair LED DDR4 3000Mhz - Samsung 512 GB M.2 (OS & Games) - 2 x 500GB Samsung 750 EVO SSD (Data) - Win 10 Pro 64bit - 12GB Nvidia Titan-X - 3 x Asus ROG Swift PG279Q 2560 x 1440p Monitors - Razer Black Widow Chroma, Naga Epic Chroma, Orbweaver Chroma - TM Warthog HOTAS + 2 x MFCD's - Saitek Pro Combat Pedals - TrackIR 5 w/ProClip - Sades SA-926 Headset - Obutto R3volution Rig :thumbup: Link to comment Share on other sites More sharing options...
firmek Posted February 25, 2017 Share Posted February 25, 2017 (edited) 1. Check if there is a "SnapViews.lua" file in "C:\Users\@your_user_name\Saved Games\DCS.openbeta\Config\View" folder. 2. If not, save any view using snap views saving - http://en.wiki.eagle.ru/wiki/Snap_views. Simplest case - jump into any plane. Pause TrackIR. Hit Num5, next RAlt+Num0, exit game. Now the file should be created. 3. Edit the file a.) find the section for plane you want to set the FOV for - "SnapViews["module_name"] b.) Modify viewAngle value at index 13 to change the default FOV [13] = {--default view viewAngle = 107.000000,--FOV hAngle = 0.096307, vAngle = -14.985352, x_trans = 0.267599, y_trans = -0.027049, z_trans = -0.001030, rollAngle = -0.005687, }, c.1.) Optional - change other viewAngle settings. Its a personal preference but I've set the same FOV for all of my modules. Edited February 25, 2017 by firmek 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...
firmek Posted February 25, 2017 Share Posted February 25, 2017 (edited) Updated version included. Added Viggen, Bf 109, Fw 190 and L-39 (both variants). SnapViews.lua - obviously optional. Version with all views configured as default in DCS but with modified, same FOV = 107 set for all views, including default as also quick views (107 works nice for wide-screen monitors). Easy to change the FOV - just run replace "viewAngle = 107.000000," selecting your own value. Complete list of suported modules: A-10A A-10C F-15C Hawk Ka-50 MiG-29A MiG-29G MiG-29S P-51D TF-51D Su-25 Su-25T Su-27 Su-33 Mi-8MT UH-1H C-101EB M-2000C MiG-21Bis MiG-15bis F-86F Sabre SpitfireLFMkIX Bf-109K-4 FW-190D9 AJS37 L-39C L-39ZAServer.luaSnapViews.lua Edited February 25, 2017 by firmek Added list of supported modules. 2 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...
Haukka81 Posted February 25, 2017 Share Posted February 25, 2017 Will this work with Oculus rift ? Sent from my iPhone using Tapatalk Oculus CV1, Odyssey, Pimax 5k+ (i5 8400, 24gb ddr4 3000mhz, 1080Ti OC ) [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
firmek Posted February 25, 2017 Share Posted February 25, 2017 Don't have a VR set so I haven't had a way to test it. Give it a try to see if it works. Just backup the original files. 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...
AbortedMan Posted April 16, 2017 Share Posted April 16, 2017 Updated version included. Added Viggen, Bf 109, Fw 190 and L-39 (both variants). SnapViews.lua - obviously optional. Version with all views configured as default in DCS but with modified, same FOV = 107 set for all views, including default as also quick views (107 works nice for wide-screen monitors). Easy to change the FOV - just run replace "viewAngle = 107.000000," selecting your own value. Complete list of suported modules: A-10A A-10C F-15C Hawk Ka-50 MiG-29A MiG-29G MiG-29S P-51D TF-51D Su-25 Su-25T Su-27 Su-33 Mi-8MT UH-1H C-101EB M-2000C MiG-21Bis MiG-15bis F-86F Sabre SpitfireLFMkIX Bf-109K-4 FW-190D9 AJS37 L-39C L-39ZA Any hopes of getting this working with the SA342 Gazelle? Link to comment Share on other sites More sharing options...
maxxs Posted April 16, 2017 Share Posted April 16, 2017 hello. srry 4 my english. i want to sit deeper in pit. i use edtracker and i cant good see the hud in ajs37 viggen. witch code i must change? can u help me? thx [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Beamscanner Posted April 21, 2017 Share Posted April 21, 2017 Can we get the f-5 as well? Link to comment Share on other sites More sharing options...
firmek Posted April 21, 2017 Share Posted April 21, 2017 Guys sorry but I don't have F-5 and Gazelle. I could add them if someone owning the modules would provide me with the needed information. I'm not at home so I can't check where exactly to look for it. Next, someone would have to help to test it and there will be an maintenance issue as I'll not be able to periodically check if anything didn't change in the original files. 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...
SDsc0rch Posted April 25, 2017 Share Posted April 25, 2017 Can we get the f-5 as well? ^ 2nd this i7-4790K | Asus Sabertooth Z97 MkI | 16Gb DDR3 | EVGA GTX 980 | TM Warthog | MFG Crosswind | Panasonic TC-58AX800U [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Sn8ke Posted July 27, 2017 Share Posted July 27, 2017 Can it be confirmed this mod works with the latest DCS updates? Just curious because I just reinstalled DCS after a new build and the mod sets the default view very close to the instrument panel unlike before. Asus ROG Maximus X Apex//Core I7 8700K @ 5.3Ghz //32GB DDR4 RAM//Asus 3090 RTX//4K monitor w/ TrackIR 5 Link to comment Share on other sites More sharing options...
Wizard1393 Posted September 6, 2017 Share Posted September 6, 2017 Is there some one who got the F-5E to read settings from server.lua? I don't get that to work. GPU: PALIT NVIDIA RTX 3080 10GB | CPU: Intel Core i7-9700K @ 4,9GHz | RAM: 64GB DDR4 3000MHz VR: HP Reverb G2 | HOTAS: TM Warthog Throttle and Stick OS: Windows 10 22H2 Link to comment Share on other sites More sharing options...
SDsc0rch Posted September 6, 2017 Share Posted September 6, 2017 +1 i7-4790K | Asus Sabertooth Z97 MkI | 16Gb DDR3 | EVGA GTX 980 | TM Warthog | MFG Crosswind | Panasonic TC-58AX800U [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
firmek Posted October 8, 2017 Share Posted October 8, 2017 Couldn't resist the recent sale and finally got F-5 - yet another great module which most probably I won't be able to devote the time it deserves. Anyway, so far enjoyed it a lot - it's super simple. On negative side - something seems to be strange with the sounds, like the engine sound would be really muted with a lot of white-noise on top of their audio cue. Anyway, I've added F-5 to server.lua.Server.luaSnapViews.lua 1 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...
Buckeye Posted October 20, 2017 Share Posted October 20, 2017 (edited) So in VR I am using firmek's last update and it's working great (thanks, firmek!) but I want to move my head back just a tad to include my FOV in the cockpit. Which lines do I need to change? I changed FOV from 107 to 117 and nothing changed. I just need to be able to see a bit more for visual reference in formation. Sent from my iPhone using Tapatalk Edited October 20, 2017 by =Buckeye= typo VR Cockpit (link): Custom Throttletek F/A-18C Throttle w/ Hall Sensors + Otto switches | Slaw Device RX Viper Pedals w/ Damper | VPC T-50 Base + 15cm Black Sahaj Extension + TM Hornet or Warthog Grip | Super Warthog Wheel Stand Pro | Steelcase Leap V2 + JetSeat SE VR Rig: Pimax 5K+ | ASUS ROG Strix 1080Ti | Intel i7-9700K | Gigabyte Z390 Aorus Master | Corsair H115i RGB Platinum | 32GB Corsair Vengeance Pro RGB 3200 | Dell U3415W Curved 3440x1440 Link to comment Share on other sites More sharing options...
firmek Posted October 20, 2017 Share Posted October 20, 2017 (edited) If you would like to change the default head position in the cockpit (not the FOV), there are two ways how it can be done: 1. Use the user snap views by chaning the head position in cokpit, as described here: http://en.wiki.eagle.ru/wiki/Snap_views 2. Edit the SnapViews manually, change the default setting (index 13): [13] = {--default view viewAngle = 107.000000,--FOV hAngle = 0.000000, vAngle = 0.000000, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, I think it's one of the x_trans or y_trans - would have to do a small triall and error to see which one exactly and how much to change it. The other point are the cockpit head movement limits which are controled by 6 DOF setting in the server.lua. Correct me if I'm wrong as I don't have a VR but as far as I understood from the forum those are not applicable for VR. Edited October 20, 2017 by firmek 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...
Recommended Posts