Problem when customizing the Mirage F1 Views on Server.Lua

[Rudel_chw]

Hi,

I'm having trouble customizing the default Mirage view by editing the Server.Lua file at /Saved games/DCS.openbeta/Config/View ... which is the method recommended by ED in order to not mess with the Module's files that are within DCS folder. I do this customization by inserting these lines on my Server.Lua:

 

Spoiler

ViewSettings["Mirage-F1EE"] = {
    Cockpit = {
        [1] = {-- player slot 1
                CockpitLocalPoint          = {3.225, 0.368, 0.0},
                CameraViewAngleLimits      = {20.000000,210.000000},
                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.150000,0.35000},y ={-0.350000,0.100000},z = {-0.22000,0.22000},roll = 90.000000},
                -- limits_6DOF               = {x = {-0.050000,0.20000},y ={-0.100000,0.100000},z = {-0.22000,0.22000},roll = 90.000000},
    },
}, -- Cockpit 
Chase = {
    --LocalPoint      = {0.200000,-0.652000,-0.650000},
    --AnglesDefault   = {0.000000,0.000000},
    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 
}

 

These lines were taken from the Modules default ViewsF1C.lua, and editing only the "limits_6DOF" and the "CameraViewAngleLimits" lines.

 

If I edit those lines directly on the default ViewsF1C.lua file of the Module, then I get the desired customization: a wider FOV and a bit more leeway for getting my virtual head nearer the instruments panel and consoles when I want to see some instrument up close (rather than zooming) ... but the same lines of Server.lua have no effect at all.

 

Could it be that ViewSettings["Mirage-F1EE"] needs a different Module ID? 

 

To better illustrate my point, this is the standard 6DOF of the Mirage EE, where I try to move my head forward, up, down and back up to the limits of movement that the aircraft allows:

 

 

and here is the same mission, but with the customized 6DOF values:

 

 

Thanks for any help with this 

 

Eduardo

Edited March 12, 2023 by Rudel_chw
Added sample videos

[YSIAD_RIP]

Hi @Rudel_chw, 

I stumbled on your post while checking in on the Mirage F1 updates and hopefully, the eventual fix of that Left Mirror freezing when using TrackIR/OpenTrack to look to the left. 

I realized that I had not added the Mirage-F1EE to my custom Server.lua in the SavedGames\Config\View Folder.   

Assumption 1: I have been using an updated version of the Reworked Cockpit Views files found in these DCS Forums as I believe you are as well.

Assumption 2: You have probably fixed your issue already but just in case here is my example in hopes that it helps others in the future. 

Assumption 3: Maybe there is an unseen typo or formatting issue that the newer Mirage F1CC did not like from your original edits?

-- -------------------------------------------------------------------------
-- Start of Additions and changes made by JJF Additions -------------------- 
-- Looks like chaning gEyePoint and settings below the first line 6 entry --
-- does successfully affect the modules listed below this entry! -----------
-- -------------------------------------------------------------------------
-- Global view configuration
-- Update for DCS 1.5.3
local gEyePoint                 = {-0.00, 0.10, 0.00}                     -- Front/back, up/down, lef/right {0.08, 0.10, 0.00} {0.16, 0.1} -- jjf So FAR:{-0.05, 0.10, 0.00}OK but HUD big.:{-0.10, 0.12, 0.00} OK for Warbirds! :Default{-0.08, 0.10, 0.00}  
local gCameraViewAngleLimits    = {55.000000,95.000000}                -- my value was {20.000000, 90.000000} and {55.000000, 95.000000} - Field of view, zoom min and max. consider setting it so that min + (max-min)/2 = default viewAngle (index 13) from snap views. This will result in the default zoom being located in the midle position of the zoom slider, for instance on the TM W . Note that Mi-8 is an exception from this rule as it uses a "Max FOV adjustment" from "Special" to override the max value. Setting max value to default FOV - viewAngle from SnapViews will remove the zoom-out effect at cokpit enter.
local gCameraAngleLimits        = {200.000000, -90.000000, 90.000000}   -- Maximum head movement angles: left/right, down, up. Not applicable for Mi-8
local gShoulderSize             = 0.25                                  -- 0.25 Shift head left/right when view angle is more than 90 degrees -- jjf so FAR: 0.20 is excellent and 0.15 is OK too!

function default_fighter_player(t)
	local res = { 
		CameraViewAngleLimits  = gCameraViewAngleLimits,
		CameraAngleRestriction = {false, 90.0, 0.5},
		EyePoint               = gEyePoint,
		Allow360rotation	   = false,
		CameraAngleLimits      = gCameraAngleLimits,
		ShoulderSize 		   = gShoulderSize,
	}
	if t then 
		for i,o in pairs(t) do
			res[i] = o
		end
	end
	return res
end

ViewSettings["Mirage-F1CE"] = {  -- by JJF Testing Settings
	Cockpit = {
	[1] = default_fighter_player({CockpitLocalPoint      = {3.225, 0.368, 0.0},
								  --CameraAngleLimits      = {200.0, -90.0, 90.0},
								  limits_6DOF            = {x 	 = {-0.150000,0.250000},
															y 	 = {-0.300000,0.100000},
															z 	 = {-0.220000,0.220000},
															roll =  90.000000}}),
	}, -- Cockpit 
	Chase = {
		LocalPoint      = {-5.0,1.0,3.0},
		AnglesDefault   = {180.000000,-8.000000},
	}, -- Chase 
	Arcade = {
		LocalPoint      = {-21.500000,5.618000,0.000000},
		AnglesDefault   = {0.000000,-12.000000},
	}, -- Arcade 
}
ViewSettings["Mirage-F1EE"] = {  -- by JJF Testing Settings
	Cockpit = {
	[1] = default_fighter_player({CockpitLocalPoint      = {3.225, 0.368, 0.0},
								  --CameraAngleLimits      = {200.0, -90.0, 90.0},
								  limits_6DOF            = {x 	 = {-0.150000,0.250000},
															y 	 = {-0.300000,0.100000},
															z 	 = {-0.220000,0.220000},
															roll =  90.000000}}),
	}, -- Cockpit 
	Chase = {
		LocalPoint      = {-5.0,1.0,3.0},
		AnglesDefault   = {180.000000,-8.000000},
	}, -- Chase 
	Arcade = {
		LocalPoint      = {-21.500000,5.618000,0.000000},
		AnglesDefault   = {0.000000,-12.000000},
	}, -- Arcade 
}

 

 

[Rudel_chw]

3 hours ago, YSIAD_RIP said:

Assumption 2: You have probably fixed your issue already but just in case here is my example in hopes that it helps others in the future. 

 

Hello, thanks for your input .. I have a workaround rather than a fix: instead of editing at /Saved Games/Config/View/Server.lua  I have been forced to edit the modules file, at /Program Files/Eagle Dynamics/DCS World Openbeta/Mods/aircraft/Mirage-F1/   ... there I edit two files: ViewsF1B.lua and ViewsF1C.lua

I will test your code to see if it works for me too, as I'd much prefer an edit at /Saved Games/ than on the DCS program folder. Will comment back once I have tested. Cheers,

 

Eduardo

[Rudel_chw]

16 hours ago, Rudel_chw said:

I will test your code to see if it works for me too, as I'd much prefer an edit at /Saved Games/ than on the DCS program folder. Will comment back once I have tested.

 

Hi,

Just tested and found that the server.lua lines that I showed on the original post, now work perfectly from /Saved Games/ and the Mirage F1 takes my new 6DOF limits with no issues.

Maybe Aerges fixed the problem and just didn't mention it here. @fausete can you please mark this issue as solved? 

Thanks @YSIAD_RIP for your help and best regards.

Cheers,

 

Eduardo

[markturner1960]

Hi Rudel, do these edited values affect the views in VR or only 2D with trackir? 

[Rudel_chw]

2 hours ago, markturner1960 said:

Hi Rudel, do these edited values affect the views in VR or only 2D with trackir? 

only 2D.