Jump to content

Guide - Enhancing head movement on TrackIR


Recommended Posts

The technique shown on the first post applies to every aircraft, it should work with the A-10C too.

 

 

 

good morning

Could you tell me the ideal parameters for limits_6DOF in the case of a 10 c, I say this because I have been testing with different values ​​to those that come in the server file. lua and I have not noticed any difference between the modified and what comes by default. I use the TR5. Thank you in advance

Link to comment
Share on other sites

  • 3 weeks later...
good morning

Could you tell me the ideal parameters for limits_6DOF in the case of a 10 c, I say this because I have been testing with different values ​​to those that come in the server file. lua and I have not noticed any difference between the modified and what comes by default. I use the TR5. Thank you in advance

 

I haven’t flown the A-10 in years, so I haven’t yet tinkered with its 6dof values, I would be surprised of its 6dof values cant be tuned a bit.

 

Question: When we change the snap view and save it with Right-Alt/Num0, does it save it in the main game folder or the saved games folder?

 

Its saved on saved games/dcs/config/view/snapviews.lua

 

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

I haven’t flown the A-10 in years, so I haven’t yet tinkered with its 6dof values, I would be surprised of its 6dof values cant be tuned a bit.

 

 

 

Its saved on saved games/dcs/config/view/snapviews.lua

 

 

Ok, thanks. I was experiencing some weird stuff and in the end I think it was just a bad battery in my TrackIR. Mine runs on 2 AA rechargeable batteries and one was down to 0.85V while the other was at 1.24 like it is supposed to be. I am new to TrackIR as far as using it and was curious if in the adjustment screen under TrackIR if all the fields are supposed to be blank? The TrackIR works fine. Also, can you assign the Num5 key to the same key that centers the TrackIR using OpenTrack? I tried it but was unsure if it was really working.

 

Thanks,

Dave

Link to comment
Share on other sites

I've been trying to change the zoom out(x) value for the A-10c as well, so my triple screens won't zoom out so far. But no luck!..

 

The only value that I changed in the Server.lua was the x/back(aft) value. The default was -0,050000. I tried -0.02000 and 0.200000, but neither had any effect at all. And after googliing for limits_6dof for the A-10c I found nothing to help. And I don't see a view.lua in the mods/aircraft/A-10c folder. So, I don't know where else it is getting it's limits for 6dof?

 

I also searched the dcs.log for the server.lua and it was loaded ok, with no errors. So it's not a typo.

 

The A-10c is an older module, so maybe it works differently? :cry:

 

These changes to the Server.lua have no effect:

			limits_6DOF = {x = {[b][color="Red"]0.200000[/color][/b],0.600000},
						y = {-0.300000,0.100000},
						z = {-0.250000,0.250000},
						roll = 90.000000}}),

--	ORIGINAL		 limits_6DOF = {x = {-0.050000,0.600000}, 
--							y = {-0.300000,0.100000}, 
--							z = {-0.250000,0.250000}, 
--							roll = 90.000000}}),
--
-- WHERE: x = back to front (aft-forward axis), y = top to bottom (vertical axis), z = side to side
-- INSTRUCTIONS HERE: [url]https://wiki.hoggitworld.com/view/Cockpit_Views[/url]

Intel I9-10850K (OC @ 5.0ghz) │ Asus Maximus XII Hero │ G.Skill Ripjaws 64GB (4x16GB) DDR4 3200 │ Thermaltake Water 360mm
Gigabyte RTX 4090 Gaming OC 24gb │ 2TB M.2 EVO Pro; 1T M.2 EVO; Sandisk SSD Drives │ 49" Samsung Curved Widescreen │ 28" Touchscreen

- ҉ - Blackshark Cockpit Trainer - ҉ -    Thread   | Download

Link to comment
Share on other sites

  • 1 month later...

Does anyone else have their 6DOF edits screwing up VR head position in aircraft? The only values I ever change are the x/y/z limits, yet that somehow FUBARs my Hornet and Tomcat VR head positions. I'm constantly having to rebuild my Server.lua file and redo every. single. module.

Link to comment
Share on other sites

  • 2 months later...

Hi all,

Has anybody tried this with the Heatblur F-14B? I'm getting some really mixed results messing with the Server.lua file in saved games:

 

if I open up the limits in Limits_6DOF until say ±1.0 in all directions they work until ±0.5 in all directions with the TrackIR (though I use OpenTrack, but it uses the TrackIR protocol and DCS reads it as such), at which point it appears to run into some other limit, but doesn't run into the limit until the ±1.0 when using the RCtrl+RShift+Num2/4/6/8 keys. I also can't get it to roll 1:1 with OpenTrack, it only rolls to 45° and it requires a 90° roll of the (checked OpenTrack and the scaling is 1:1 and the little model does rotate to 90° with a 90° head roll)

 

I also tried to open up the pitch up limit as the default doesn't let me even look up all the way to vertical (already verified that OpenTrack isn't the limiting factor, its exporting angles well past 90 with no problem):

CameraAngleLimits      = { 180, -80.0, 120.0 },

but replacing the "-80" with -120 or anything else doesn't seem to have any effect, even smaller numbers like 10 don't seem to have an effect.

 

So DCS is definitely reading the file and the F-14B section because changing limits_6DOF works (albeit oddly) so the aircraft ID isn't the problem, but DCS seems to be ignoring the CameraAngleLimits parts of it. In fact, even if I change the pitch up limits in default_fighter_player there is no effect in the F-14 or the default DCS SU-25T (should there be?).

 

Is there something I'm missing?

 

here's my complete Server.lua file for reference (F-14B at the bottom):

-- View scripts 
-- Copyright (C) 2004, Eagle Dynamics.
DisableCombatViews				= false -- F5 & Ctrl-F5
ExternalObjectsLockDistance 	= 10000.0
ShowTargetInfo 					= false
CameraTerrainRestriction 		= true
hAngleRearDefault 				=  180
vAngleRearDefault 				= -8.0
vAngleRearMin    				= -90 -- -8.0
vAngleRearMax    				= 90.0

dbg_shell    = "weapons.shells.PKT_7_62_T" -- 23mm shell
--dbg_shell    = "weapons.shells.2A42_30_AP"
--dbg_shell    = "weapons.nurs.WGr21"
--dbg_shell    = "weapons.shells.2A64_152" -- 152mm shell
dbg_shell_v0 = -1 -- Muzzle speed m/s (-1 - speed from shall database)
dbg_shell_fire_rate = 120
--reformatted per-unit data to be mod system friendly 
--this file is no longer should be edited for adding new flyable aircraft , DCS automatically check core database (i.e. where you define your aircraft in aircraft table just define ViewSettings and SnapViews tables)

function default_fighter_player(t)
local res = { 
	CameraViewAngleLimits  = {20.000000,140.000000},
	CameraAngleRestriction = {false	   ,90.000000,0.500000},
	EyePoint               = {0.05     ,0.000000 ,0.000000},
	limits_6DOF            = {x = {-0.050000,0.4500000},y ={-0.300000,0.100000},z = {-0.220000,0.220000},roll = 90.000000},
	Allow360rotation	   = false,
	CameraAngleLimits      = {200,-80.000000,110.000000},
	ShoulderSize 		   = 0.2,  -- move body when azimuth value more then 90 degrees
}
if t then 
	for i,o in pairs(t) do
		res[i] = o
	end
end
return res
end

function fulcrum()
return {
	Cockpit = {
				default_fighter_player({CockpitLocalPoint = {4.71,1.28,0.000000}})
	},
	Chase   = {
		LocalPoint      = {1.220000,3.750000,0.000000},
		AnglesDefault   = {180.000000,-8.000000},
	}, -- Chase 
	Arcade = {
		LocalPoint      = {-15.080000,6.350000,0.000000},
		AnglesDefault   = {0.000000,-8.000000},
	}, -- Arcade 
}
end

ViewSettings = {}
ViewSettings["A-10A"] = {
Cockpit = {
[1] = default_fighter_player({CockpitLocalPoint      =  {4.300000,1.282000,0.000000},
							  EyePoint  			 = {0.000000,0.000000,0.000000},
							  limits_6DOF            = {x 	 = {-0.050000,0.600000},
														y 	 = {-0.300000,0.100000},
														z 	 = {-0.250000,0.250000},
														roll =  90.000000}}),
}, -- Cockpit 
Chase = {
	LocalPoint      = {0.600000,3.682000,0.000000},
	AnglesDefault   = {180.000000,-8.000000},
}, -- Chase 
Arcade = {
	LocalPoint      = {-27.000000,12.000000,0.000000},
	AnglesDefault   = {0.000000,-12.000000},
}, -- Arcade 
}
ViewSettings["F-15C"] = {
Cockpit = {  
[1] = default_fighter_player({CockpitLocalPoint      = {6.210000,1.204000,0.000000}})-- player slot 1
}, -- Cockpit 
Chase = {
	LocalPoint      = {2.510000,3.604000,0.000000},
	AnglesDefault   = {180.000000,-8.000000},
}, -- Chase 
Arcade = {
	LocalPoint      = {-13.790000,6.204000,0.000000},
	AnglesDefault   = {0.000000,-8.000000},
}, -- Arcade 
}
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},
},
}, -- Cockpit 
Chase = {
	LocalPoint      = {-0.512000,2.790000,0.000000},
	AnglesDefault   = {180.000000,-8.000000},
}, -- Chase 
Arcade = {
	LocalPoint      = {-16.812000,5.390000,0.000000},
	AnglesDefault   = {0.000000,-8.000000},
}, -- Arcade 
}
ViewSettings["MiG-29A"] = fulcrum()
ViewSettings["MiG-29G"] = fulcrum()
ViewSettings["MiG-29S"] = fulcrum()

ViewSettings["Su-25"] = {
Cockpit = {
[1] = default_fighter_player({CockpitLocalPoint      = {3.352000,0.506000,0.000000}}),-- player slot 1
}, -- Cockpit 
Chase = {
	LocalPoint      = {-0.348000,2.906000,0.000000},
	AnglesDefault   = {180.000000,-8.000000},
}, -- Chase 
Arcade = {
	LocalPoint      = {-16.648001,5.506000,0.000000},
	AnglesDefault   = {0.000000,-8.000000},
}, -- Arcade 
}
ViewSettings["Su-25T"] = {
Cockpit = {
[1] = default_fighter_player({CockpitLocalPoint      = {3.406000,0.466000,0.000000}}),-- player slot 1
}, -- Cockpit 
Chase = {
	LocalPoint      = {-0.294000,2.866000,0.000000},
	AnglesDefault   = {180.000000,-8.000000},
}, -- Chase 
Arcade = {
	LocalPoint      = {-16.594000,5.466000,0.000000},
	AnglesDefault   = {0.000000,-8.000000},
}, -- Arcade 
}
ViewSettings["Su-25TM"] = {
Cockpit = {
[1] = {-- player slot 1
	CockpitLocalPoint      = {4.000000,1.000000,0.000000},
	CameraViewAngleLimits  = {20.000000,140.000000},
	CameraAngleRestriction = {true,90.000000,0.400000},
	CameraAngleLimits      = {160.000000,-70.000000,90.000000},
	EyePoint               = {0.000000,0.000000,0.000000},
	limits_6DOF            = {x = {-0.200000,0.200000},y ={-0.200000,0.200000},z = {-0.200000,0.200000},roll = 60.000000},
},
}, -- Cockpit 
Chase = {
	LocalPoint      = {4.000000,2.000000,0.000000},
	AnglesDefault   = {180.000000,-8.000000},
}, -- Chase 
Arcade = {
	LocalPoint      = {4.000000,2.000000,0.000000},
	AnglesDefault   = {180.000000,-8.000000},
}, -- Arcade 
}
ViewSettings["Su-27"] = {
Cockpit = {
[1] = default_fighter_player({CockpitLocalPoint      = {7.959000,1.419000,0.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"]

ViewSettings["F-14B"] = {
   Cockpit = {
       [1] = {

          
           --CockpitLocalPoint      = { 7.114937, 1.39846, 0.0 },
		CockpitLocalPoint      = { 7.014937, 1.39846, 0.0 },
           CameraViewAngleLimits  = { 30.0, 140.0 },
           --Original Limits
		--CameraAngleLimits      = { 180, -80.0, 120.0 },
		CameraAngleLimits      = { 180, -10.0, 110.0 },
           CameraAngleRestriction = {false, 90.0, 0.5},


           EyePoint         = { 0.00000,0.100000,0.000000},
           ShoulderSize     = 0.1,
           Allow360rotation = false,
		--Original Limits
           --limits_6DOF      = { x = {-0.3, 0.57}, y = {-0.55, 0.10}, z = {-0.25, 0.25}, roll = 45.0 },
		--Desired limits
		--limits_6DOF      = { x = {-0.6, 0.57}, y = {-0.75, 0.30}, z = {-0.55, 0.55}, roll = 90.0 },
		--Experimental limits
		limits_6DOF      = { x = {-1.0, 1.0}, y = {-1.0, 1.0}, z = {-1.0, 1.0}, roll = 90.0 },
           
       },
       [2] = {

           
           CockpitLocalPoint      = { 5.596174, 1.605, 0.0 },
           CameraViewAngleLimits  = { 30.0, 140.0 },
           CameraAngleLimits      = { 180, -80.0, 120.0 },
           CameraAngleRestriction = {false, 90.0, 0.50},


           EyePoint         = { 0.05000,0.100000,0.000000 },
           ShoulderSize     = 0.15,
           Allow360rotation = false,
           limits_6DOF      = { x = {-0.3, 0.45}, y = {-0.55, 0.10}, z = {-0.25, 0.25}, roll = 45.0 },
           
       },
   },
   Chase = {
       --LocalPoint    = {0.6, 3.7, 0.0},
       --AnglesDefault = {180.0, -8.0},
       LocalPoint    = {-10.0,1.0,3.0},
       AnglesDefault = {0.000000, 0.000000},
   },
   Arcade = {
       LocalPoint    = {-25.0, 6.0, 0.0},
       AnglesDefault = {0.0, -8.0},
   },
}

Link to comment
Share on other sites

  • 10 months later...

This is odd! Everytime I open this thread, on any of my PC's, I get this BitDefender notification? Something to do with the photos attached in the 1st post that are no longer available?

 

"chrome.exe attempted to establish a connection relying on an expired certificate to www.schoenstatt-antofagasta.cl. We blocked the connection to keep your data safe since websites must renew their certificates with a certification authority to stay current, and outdated security certificates represent a risk."

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

18 minutes ago, Fakum said:

This is odd! Everytime I open this thread, on any of my PC's, I get this BitDefender notification? Something to do with the photos attached in the 1st post that are no longer available?

 

"chrome.exe attempted to establish a connection relying on an expired certificate to www.schoenstatt-antofagasta.cl. We blocked the connection to keep your data safe since websites must renew their certificates with a certification authority to stay current, and outdated security certificates represent a risk."

 

Yeah, sure I will spend $$$ to purchase a certificate so that my website looks nice to your antivirus 🙂

 

I edited the 1st post, hopefully it will be better now.

 

 

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

LOL,,,, I dont know anything about the mentioned certificates, and I had no idea it had anything to do with your site??? LOL.. as far as I could tell,, I was on DCS forums only???? I guess it had something to do with embedded links then to your site? Anyway,, thank you sir!

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

  • 6 months later...

I hate to drag up an old thread, but it's not working for me in the F-5.  I copied your settings exactly as shown in your image but I'm still limited to the default range of motion.

 

Quote

ViewSettings = ["F-5E-3"] = {
    Cockpit = {
    [1] = {-- player slot 1
        CameraViewAngleLimits  = {20.000000,140.000000},
        CockpitLocalPoint      = {3.022,0.860,0.0},
        CameraAngleRestriction = {false,90.000000,0.500000},
        CameraAngleLimits      = {200,-90.000000,90.000000},
        EyePoint               = {0.05000,0.100000,0.000000},
        ShoulderSize           = 0.25,
        Allow360rotation       = false,
        limits_6DOF            = {x = {-0.50,0.50},y ={-0.50,0.10},z = {-0.40,0.40},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
}

 

Link to comment
Share on other sites

  • 4 months later...
  • 6 months later...

Thank you to the OP for putting this together, does this still work currently?

 

as per the mission editor, this is what I have for aircraft names (2 pics below) in the server.lua for the 3 that I fly currently, now I'm guessing that the names in yellow are the ones we want given the F5 variant as an example:

F-5E-3

F-16CM bl.50

F/A-18C Lot 20

 

 

DCS World aircraft models-1.png

DCS World aircraft models-2.png


Edited by GK61
Link to comment
Share on other sites

1 hour ago, GK61 said:

Thank you to the OP for putting this together, does this still work currently?

Yes, it still works 🙂

 

1 hour ago, GK61 said:

as per the mission editor, this is what I have for aircraft names (2 pics below) in the server.lua for the 3 that I fly currently, now I'm guessing that the names in yellow are the ones we want given the F5 variant as an example:

F-5E-3

F-16CM bl.50

F/A-18C Lot 20

 

The names are the same ones used on the file Snapviews.lua, located at /Saved Games/DCS/Config/View/

 

YG5qGmp.jpg

 

 

  • Like 1

 

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

10 minutes ago, Rudel_chw said:

Yes, it still works 🙂

 

 

The names are the same ones used on the file Snapviews.lua, located at /Saved Games/DCS/Config/View/

 

YG5qGmp.jpg

 

 

hmm ok, I thought the names were what the mission editor or startup mission screen had shown, anyhow this is what I have:

ViewSettings["FA-18C_hornet"] = {
ViewSettings = {
    Cockpit = {
    [1] = {-- player slot 1
        CameraViewAngleLimits  = {20.000000,140.000000},
        CockpitLocalPoint      = {3.533,1.156,0.0},
        CameraAngleRestriction = {false,90.000000,0.500000},
        CameraAngleLimits      = {200,-90.000000,90.000000},
        EyePoint               = {0.05000,0.100000,0.000000},
        ShoulderSize           = 0.25,
        Allow360rotation       = false,
        limits_6DOF            = {x = {-0.13,0.45},y ={-0.4,0.065},z = {-0.2,0.2},roll = 90.000000},
        --limits_6DOF          = {x = {-0.13,0.30},y ={-0.3,0.065},z = {-0.18,0.18},roll = 90.000000}, (default)
    },
    }, -- 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
}

 

and the numbers in "CameraViewAngleLimits" don't seem to change no matter what I place in there, what may I be overlooking?

Link to comment
Share on other sites

5 minutes ago, GK61 said:

the numbers in "CameraViewAngleLimits" don't seem to change no matter what I place in there, what may I be overlooking?

 

I have no idea, the only parameter I change is the " limits_6DOF", to allow me a greater area of movement of my virtual head .. I don't touch the camera limits.

 

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

2 minutes ago, Rudel_chw said:

 

I have no idea, the only parameter I change is the " limits_6DOF", to allow me a greater area of movement of my virtual head .. I don't touch the camera limits.

no worries, I too have TrackIR and really appreciate work here nonetheless


Edited by GK61
Link to comment
Share on other sites

3 hours ago, Rudel_chw said:

 

I have no idea, the only parameter I change is the " limits_6DOF", to allow me a greater area of movement of my virtual head .. I don't touch the camera limits.

I pulled your custom server.lua from this link: https://wiki.hoggitworld.com/view/Cockpit_Views#Default_keybindings and redid all my settings, all good now except for the fact I still can't seem to get the "CameraViewAngleLimits" any closer than 20 FOV as seen in the pic of the C130, in my opinion I think it's capped @ 20.

CameraViewAngleLimits.jpg

CameraViewAngleLimits-crop.jpg

CameraViewAngleLimits-crop.jpg


Edited by GK61
Link to comment
Share on other sites

  • 5 months later...

So today I've revisited this thread along with my TIR settings to tweak a bit and noticed now that some of the particulars within the server.lua have changed somewhat since DCS 2.7 etc., e.g. shoulder size to 20 from 25, EyePoint global to {0.05, 0.000000, 0.000000} from {0.05 , 0.080000, 0.000000}, mostly inconsequential however With 2.8 now a few of the 6DOF numbers have changed somewhat, JF-17 as well as the F-16 anyone else notice this?


Edited by GK61
Link to comment
Share on other sites

1 hour ago, GK61 said:

anyone else notice this?

 

Hello,

On my case, I adjust the values by trial-error and once I'm happy with my 6DOF limits I then forget about them and don't check them again ... so, I have not noticed any changes on the default values, since I still use my own custom ones. I only repeat this process whenever I get a new aircraft, my latest was the VSN F-4B/C and these are the values that I use with it:

 

hzrn4qc.jpg

 

  • Thanks 1

 

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

59 minutes ago, GK61 said:

things seem almost perfect but I'm too zoomed in now with my TIR

 

The 6DOF parameter has no relationship with the zoom .. it just establishes the limits for the movement of your virtual head within the cockpit.

For the zoom, I adjust this other parameter:

CameraViewAngleLimits  = {20.000000,210.000000}

20 degrees is the maximum zoom, and then 210 degrees is the minimum.  When I do this change, the normal zoom is set by DCS to the mid point between these two values: (20+210)/2 = 115 degrees (for me, as I have a widescreen monitor)

and then on Snapviews.lua I modify the FOV of the default view to ensure that the normal FOV (zoom) matches with the prior value, like this:

 

BnZ9OCX.jpg

 

 

  • Like 1
  • Thanks 1

 

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

1 hour ago, Rudel_chw said:

 

The 6DOF parameter has no relationship with the zoom .. it just establishes the limits for the movement of your virtual head within the cockpit.

For the zoom, I adjust this other parameter:

CameraViewAngleLimits  = {20.000000,210.000000}

20 degrees is the maximum zoom, and then 210 degrees is the minimum.  When I do this change, the normal zoom is set by DCS to the mid point between these two values: (20+210)/2 = 115 degrees (for me, as I have a widescreen monitor)

and then on Snapviews.lua I modify the FOV of the default view to ensure that the normal FOV (zoom) matches with the prior value, like this:

 

BnZ9OCX.jpg

 

 

thanks, I'll try this. if I may do you fly the Viper or Hornet? I may have fubar'd some of my 6DOF #s


Edited by GK61
Link to comment
Share on other sites

2 hours ago, GK61 said:

if I may do you fly the Viper or Hornet? I may have fubar'd some of my 6DOF #s

 

I have these sections on my Server.lua for the Viper & Hornet:

 

u9QpPAF.jpg

 

Just tried them and it works like this:

 

 

  • Thanks 1

 

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

  • Recently Browsing   0 members

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