imacken Posted December 3, 2017 Posted December 3, 2017 I've noticed in F-5E that there is very little movement in the z-axis compared to all other modules I use. With the Spit, A-10C, etc. if I move forward or I can get really close to the instruments, etc., but not in the F5-E. Is there any particular reason for that? Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
Dino Might Posted December 15, 2017 Posted December 15, 2017 F5 models limitations from flight harness.
imacken Posted December 15, 2017 Author Posted December 15, 2017 Thanks, but if that is a serious response, then why the F5 and not all other aircraft that have pilot harnesses? Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
Rudel_chw Posted December 15, 2017 Posted December 15, 2017 I've noticed in F-5E that there is very little movement in the z-axis compared to all other modules I use. With the Spit, A-10C, etc. if I move forward or I can get really close to the instruments, etc., but not in the F5-E. Is there any particular reason for that? I dont know the reason, but it can be fixed ... see this: https://forums.eagle.ru/showthread.php?t=187155 :) 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 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
imacken Posted December 15, 2017 Author Posted December 15, 2017 (edited) Thanks for that link. Looks exactly what I want. Only trouble is, I don't have a 'server.lua' file anywhere! UPDATE: Found it. I was being a bit stupid! Edited December 15, 2017 by imacken Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
Rudel_chw Posted December 15, 2017 Posted December 15, 2017 Thanks for that link. Looks exactly what I want. Only trouble is, I don't have a 'server.lua' file anywhere! UPDATE: Found it. I was being a bit stupid! Not stupid, I've just found a mistake on what I wrote, stating that the file is in "Program Files\Eagle Dynamics\DCS World\Config" when its actually on "Program Files\Eagle Dynamics\DCS World\Config\View" Remember to copy it into your Saved Games folder, as explained on the readme.txt :) Best regards PD: This Mod is also useful and allows to more easily view the lateral instrument panels: https://forums.eagle.ru/showpost.php?p=3305863&postcount=687 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 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
imacken Posted December 15, 2017 Author Posted December 15, 2017 Thanks for that. Yes, it was the wrong path that confused me, but I got there. Just going to try it out now. Thanks for the heads up on the other mods as well. Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
Rudel_chw Posted December 15, 2017 Posted December 15, 2017 Thanks for that. Yes, it was the wrong path that confused me, but I got there. Just going to try it out now. Thanks for the heads up on the other mods as well. Another mistake on the guide is the meaning of the x, y and z parameters; their true meaning is: limits_6DOF = {x = {-0.20,0.45} ,y = {-0.55,0.175},z = {-0.65,0.65},roll = 90} Legend: x = backw & forw, y = down & up, z = left & right. 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 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
imacken Posted December 15, 2017 Author Posted December 15, 2017 Bit confused! Are you saying that x and z are not their normal meanings, i.e. left/right and backward/forward? Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
Rudel_chw Posted December 15, 2017 Posted December 15, 2017 Bit confused! Are you saying that x and z are not their normal meanings, i.e. left/right and backward/forward? Test it altering one axis at a time ... I'm not really sure and right now I'm not able to check on the sim. 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 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
Art-J Posted December 15, 2017 Posted December 15, 2017 Have you guys tried using the method in other planes as well? I tried it in F-86, which has an annoying vertical an lateral movement limit, copied the whole parameters section from MiG-15, but it didn't seem to work. It was a quick job, though, so I might have made some mistake in the procedure. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Rudel_chw Posted December 15, 2017 Posted December 15, 2017 Have you guys tried using the method in other planes as well? I tried it in F-86, which has an annoying vertical an lateral movement limit, copied the whole parameters section from MiG-15, but it didn't seem to work. It was a quick job, though, so I might have made some mistake in the procedure. Hi, You just need the limits_6DOF statement and put the name if the plane on the section ... dont touch anything else. It should look like this: ViewSettings["F-86F Sabre"] = { Cockpit = { [1] = default_fighter_player({ CockpitLocalPoint = {1.677, 1.151, 0.000000}, CameraAngleLimits = {200,-90.000000,90.000000}, limits_6DOF = {x = {-0.2,0.30},y ={-0.15,0.10},z = {-0.15000,0.15000},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 } 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 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
Art-J Posted December 15, 2017 Posted December 15, 2017 Rgr that. Thanks, will test later. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Northstar98 Posted December 15, 2017 Posted December 15, 2017 Hmmm, personally I think if this is going to be a thing (having limits of degrees of freedom based on harnesses or what have you) then maybe we should see this as an option similar to "hear like in helmet" Though the quick fix suffices for the time being. Modules I own: F-14A/B, F-4E, Mi-24P, AJS 37, AV-8B N/A, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk. Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas. System: GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, NVIDIA GeForce RTX 4070S FE, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV. Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.
Art-J Posted January 1, 2018 Posted January 1, 2018 The method doesn't quite work as intended for F-86. When I copied the Viewsettings section from views.lua to modded server.lua (adding correct name of the plane of course), even with all parameters left stock, the camera point and FoV get messed up for some mysterious reason (?!). How and why if nothing in the Viewsettings section has changed? That's puzzling. Doesn't mater, though - editing limit coordinates in views.lua in airplane folder works perfectly. So I made myself a OvGME mod, which changes that file. I don't fly online, so it's good enough for me. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Recommended Posts