Jump to content

Recommended Posts

Posted

Hi,

every time I try to center view straight ahead I find me watching 70° up.

So I need to point my head down to my feet and click the center trackir button to hane a good align with the plane nose.

 

Happens only with F86 module since 1.5.3 :helpsmilie:

I'm flying since 1988 (Flight Simulator 3.0) :pilotfly:

  • 2 weeks later...
Posted (edited)

Do you still have this problem? It's fine here, with 1.5.4.56500.155.

Could it be the definition of the views, in this user file, that somehow got corrupted?

 

c:\%USERPROFILE%\Saved Games\DCS.openbeta\Config\View\SnapViews.lua

 

(DCS.openbeta, or DCS, or DCS.openalpha, depending on your version)

 

I don't have any entry for the Sabre in this file, so I'm still on the default values, you could check if you have a SnapViews["F-86"] in this file, and if so, whether the angles look weird.

 

There's also a file in the module itself,

 

{DCS install dir}\Mods\aircraft\F-86\Views.lua

 

Mine is looking like this:

 

ViewSettings = {
Cockpit = {
[1] = {-- player slot 1
	CameraViewAngleLimits  = {20.000000,140.000000},
	CockpitLocalPoint      = {1.677    ,1.151,0.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.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 
}

local function head_pos_default(tab)
   if not tab then
   tab = {}
end

tab.viewAngle = tab.viewAngle  or 85
tab.hAngle    = tab.hAngle     or  0
tab.vAngle    = tab.vAngle     or -7.5915411489154785
tab.x_trans   = tab.x_trans    or -0.0033610288728929474 - 0.05
tab.y_trans   = tab.y_trans    or -0.066924695772275097
tab.z_trans   = tab.z_trans    or  0
tab.rollAngle = tab.rollAngle  or  0

return tab
end

SnapViews = {
[1] = {-- player slot 1
	[1]  = head_pos_default({}),--Num 0
	[2]  = head_pos_default({}),--Num 1
	[3]  = head_pos_default({}),--Num 2
	[4]  = head_pos_default({}),--Num 3
	[5]  = head_pos_default({}),--Num 4
	[6]  = head_pos_default({}),--Num 5 Default view
	[7]  = head_pos_default({}),--Num 6
	[8]  = head_pos_default({}),--Num 7
	[9]  = head_pos_default({}),--Num 8
	[10] = head_pos_default({}),--Num 9
	[11] = head_pos_default({viewAngle = 60, vAngle = 10}),--look at left  mirror
	[12] = head_pos_default({viewAngle = 60, vAngle = 10}),--look at right mirror
	[13] = head_pos_default({}),--default view
},
}

Edited by Redglyph

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

Posted

I found this post particularly helpful for setting up the views, I haven't tried but maybe accidentally typing RAlt + Num0 could cause that problem, but setting the default view off?

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

Posted

Ok, copied lua file on 2.0 on 1.5 and now works fine.

 

But now I discovered that I cannot bind Y axe on thrust on 2.0

The line is RED. :(

I'm flying since 1988 (Flight Simulator 3.0) :pilotfly:

Posted
Ok, copied lua file on 2.0 on 1.5 and now works fine.

 

But now I discovered that I cannot bind Y axe on thrust on 2.0

The line is RED. :(

 

Yes, that's a known problem when some products are still in development.

 

Option 1: You have to delete the offending configuration file, and re-configure this device... though read further for option 2.

 

For example if the red line is your throttle, you can delete this file:

 

%USERPROFILE%\Saved Games\DCS.openalpha\Config\Input\F-86F\joystick\Throttle - HOTAS Warthog*.diff.lua

 

(your filename may vary, but you get the idea).

 

Option 1' would be to remove the entire joystick directory, but then you'll have to reconfigure all your devices for the F-86.

 

 

 

Option 2: If you're up to it, you can edit this file instead, and remove the offending entry/entries, and rebind the Y axis on thrust again.

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

Posted

I think I had this for a couple of aircraft recently, I hadn't even changed anything, but some of the bindings just became red, incompatible with the new version of the aircraft, I suppose.

 

If you edit the file, just make sure to remove the "offending" part properly. If for example the conflict is on joystick button 1, and the file has those lines:

 

local diff = {
["keyDiffs"] = {
	["d555pnilu555cdnilvd0.5vpnilvu0"] = {
		["added"] = {
			[1] = {
				["key"] = "JOY_BTN1",
			},
		},
		["name"] = "Trigger - FIRST DETENT",
	},
	["d84pnilu85cdnilvdnilvpnilvunil"] = {
		["added"] = {
			[1] = {
				["key"] = "JOY_BTN6",
[...]

 

then it should become

 

local diff = {
["keyDiffs"] = {
	["d84pnilu85cdnilvdnilvpnilvunil"] = {
		["added"] = {
			[1] = {
				["key"] = "JOY_BTN6",
[...]

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

  • Recently Browsing   0 members

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