Default zoom in cockpit

Hi all

Hopefully this is an easy one (I've searched and not found anything) ..

I play with a TrackIR.

Whenever I press F12 to re-centre the display (or more often when the TrackIR fails on me and I have to use the hat button!), I find the default zoom is too close for my liking. For example, on the A10, I can't see anything below the ADI (I like to be able to see my HSI too).

So - is there a config setting somewhere to make my default view in the cockpit slightly further away from the cockpit instruments.

Thanks in advance for any advice.

Regards

epoch

Well, the simple fix is to move your head closer to the TrackIR sensor before centering the display. Then once you sit in your normal comfortable position, you'll have a wider FOV.

I think there might be a way to change it, personally i never done it. But I assume it would be in your view.lua file in your Eagle Dynamics\Lock On\Config folder

Open it up with notepad and search for this

-- Camera view angle limits {view angle min, view angle max}.

CameraViewAngleLimits = {}

CameraViewAngleLimits[PlaneIndex.iSu_27] = {20.0, 120.0}

CameraViewAngleLimits[PlaneIndex.iSu_33] = {20.0, 120.0}

CameraViewAngleLimits[PlaneIndex.iSu_25] = {20.0, 120.0}

CameraViewAngleLimits[PlaneIndex.iSu_39] = {20.0, 120.0}

CameraViewAngleLimits[PlaneIndex.iMiG_29] = {20.0, 120.0}

CameraViewAngleLimits[PlaneIndex.iMiG_29K] = {20.0, 120.0}

CameraViewAngleLimits[PlaneIndex.iA_10] = {20.0, 120.0}

CameraViewAngleLimits[PlaneIndex.iF_15] = {20.0, 120.0}

Those are the default numbers in case you type in something and forgot the original value. Anyway, I would change the 20 to something a bit higher if you don't want trackir to zoom that far in. Maybe 50?

Anyway, this is why i don't use the trackir zoom function because it gets a bit of a hassle. If you just change your seating position, you might be in an awkward angle and have to reset it again. (which btw i changed the key from f12 to x. I got rid of a few useless keys such as z and x which is rudder (I got rudder on my joystick so no need to be on the keyboard) and m and n (view left and right mirror). You can get rid of these so you can put the center button closer to you.

Yeah - I remapped the keys from the defaults.

I'll have a go at tweaking the view.lua file - thanks for the tip.

I did try moving my head btw, but it didn't work! When I got my head (and view) the way I wanted, and pressed the centre view (default F12), it snaps back to the view I didn't want!

Thanks again for the tips - will try them!

Yeah - I remapped the keys from the defaults.

 

I'll have a go at tweaking the view.lua file - thanks for the tip.

 

I did try moving my head btw, but it didn't work! When I got my head (and view) the way I wanted, and pressed the centre view (default F12), it snaps back to the view I didn't want!

 

Thanks again for the tips - will try them!

Try this: Delete the TrackIR.ini in the Lock On/Input folder as well as the TrackIR file in Lock On/Config . Next time you launch TIR and Lock On (in this sequence), a new, fresh config file will be created.

Choosing a new center / FOV using F12 works fine for me every time I do it (TIR 4 Pro + Clip Pro) and the new center is stored for the time Lock On runs.

Major problem I still didn't find the solution.

TrackIR takes its default view zoom from the view.lua as SuperKungFu indicates. Make the 2nd number bigger. I use 145.0 myself. Play with it until you get the default zoom you want. Then you'll be set.

If you are use the keyboard views, OTOH, those are controlled elsewhere.

Rich

 

I did try moving my head btw, but it didn't work! When I got my head (and view) the way I wanted, and pressed the centre view (default F12), it snaps back to the view I didn't want!

That's the idea! You move your head close, which will zoom even further in. Now re-center. Now you have that default close view but your head is also closer than normal to the monitor too! Now, sit back and your view will pan out as you do. Basically you're setting what I call the "zero point".

Trust me, if you have the zoom axis enabled, this works. I do it on a daily basis. :)

Install LOCFG and you can set your cab zoom and (almost) everything else where ever you want.

Regarding this from view.lua

PlaneIndex = {

iSu_27 = 1,

iSu_33 = 2,

iSu_25 = 3,

iSu_39 = 4, -- Su-39 or Su-25T

iMiG_29 = 5,

iMiG_29K = 6,

iA_10 = 7,

iF_15 = 8,

}

-- Camera view angle limits {view angle min, view angle max}.

CameraViewAngleLimits = {}

CameraViewAngleLimits[PlaneIndex.iSu_27] = {15.0, 120.0}

--CameraViewAngleLimits[PlaneIndex.iSu_27] = {20.0, 120.0}

CameraViewAngleLimits[PlaneIndex.iSu_33] = {20.0, 120.0}

CameraViewAngleLimits[PlaneIndex.iSu_25] = {15.0, 150.0}

--CameraViewAngleLimits[PlaneIndex.iSu_25] = {20.0, 120.0}

CameraViewAngleLimits[PlaneIndex.iSu_39] = {15.0, 150.0}

-- CameraViewAngleLimits[PlaneIndex.iSu_39] = {20.0, 120.0}

CameraViewAngleLimits[PlaneIndex.iMiG_29] = {20.0, 120.0}

CameraViewAngleLimits[PlaneIndex.iMiG_29K] = {20.0, 120.0}

CameraViewAngleLimits[PlaneIndex.iA_10] = {20.0, 120.0}

CameraViewAngleLimits[PlaneIndex.iF_15] = {20.0, 120.0}

I'm pretty sure this changes what the minimum and maximum viewable angles are for a particular plane (as you can see I've commented out the originals & changed mine) not what the default angle is (smaller min angle = more zoom, larger max = wider field of view when zoomed out).

I'm fairly sure (because I just did this for mine & I use TIR - though not w/ 6DOF) that what you want to do is open snapviews.lua and change "viewAngle" in snap [n][13] where 'n' is the index number for the plane found in the view.lua

From snapviews.lua:

Snap[1][13] = {}

Snap[1][13]["viewAngle"] = 105.468338012695

Snap[1][13]["vAngle"] = -5.5

Snap[1][13]["hAngle"] = 0

& that this will change the default angle when you spawn or hit the 'put views back to normal' key

'vAngle' is how far down you can look, and 'hAngle' is how far around (sideways to the back) you can look.

If you're going to change that one, you probably want Teka-teka's seat mod that fixes where the headrest textures meet.

for moving the "F4" view

look in server.lua

function GetRearCameraPosition(iType)

...

edit these values

r[1] = p[1] + 0.1

r[2] = p[2] - 1.75

r[3] = p[3] + 0.1

They're in meters r[3] is left right pan, r[2] is vertical displacement & r[1] along the axis of the plane.

mine are at: ( you can leave the old values if you comment them out with --):

function GetRearCameraPosition(iType)

local p = CockpitLocalPoint[iType]

local r = {}

r[1] = p[1] + 0.5 -- was - 3.7

r[2] = p[2] + 0.75 -- was +2.4

r[3] = 0.0

return r[1], r[2], r[3]

which gets you:

or you can move it further forward into the cockpit or in front of the pilot looking at his face if you want ...

Weta43,

This is a case of one size does not fit all. Snap[1][13]["viewAngle"] in snapviews.lua controls controls how close/far you are as the default setting upon entering the cockpit for both the keyboard views and TrackIR when NOT using the Z-axis (lean in for closer/lean back for farther). With the Z-axis enabled, it's the 2nd number in views.lua that controls the default view.

I didn't realize this until this morning. I had changed snapviews.lua some time ago to make better use of my widescreen display and had to change views.lua separately to get the viewing distance I wanted with TrackIR (one that matched my default in snapviews). At the time, I had the Z-axis enabled. Since then I've turned it off because it's been driving me crazy. Anyway, I just checked and realized that how you have TrackIR set to zoom determines which file you have to change.

EDIT: BTW, in a post above this one I mentioned that I was using 145.0 as the 2nd number in view.lua. Actually it's 170.0. I was relying on memory and was wrong, as usual. Definitely a case of CRS.

Rich

This doen't fix the track ir re-center view to original set ( wide on this case or at list to a specific FOV ) with zoom enabled.

example

-- Camera view angle limits {view angle min, view angle max}.

CameraViewAngleLimits = {}

CameraViewAngleLimits[PlaneIndex.iSu_27] = {20.0, 115.0}

CameraViewAngleLimits[PlaneIndex.iSu_33] = {20.0, 115.0}

CameraViewAngleLimits[PlaneIndex.iSu_25] = {20.0, 109.0}

CameraViewAngleLimits[PlaneIndex.iSu_39] = {20.0, 121.0}

CameraViewAngleLimits[PlaneIndex.iMiG_29] = {20.0, 112.0}

CameraViewAngleLimits[PlaneIndex.iMiG_29K] = {20.0, 112.0}

CameraViewAngleLimits[PlaneIndex.iA_10] = {20.0, 97.0}

CameraViewAngleLimits[PlaneIndex.iF_15] = {20.0, 107.0}

Example for Mig29 in snapviews.lua

Snap[5][13]["viewAngle"] = 112.0

Snap[5][13]["vAngle"] = -9

Snap[5][13]["hAngle"] = 0

Sorry. I'm not sure I follow what you are trying to say. The number in Snap[5][13]["viewAngle"] should not be the same as it is in CameraViewAngleLimits[PlaneIndex.iMiG_29 =. Is that what you mean?

In your example, the comparable TrackIR view.lua setting would be: CameraViewAngleLimits[PlaneIndex.iMiG_29 = {20.0, 208.0}. This would give you the same default view with TrackIR's zoom axis both enabled (taken from view.lua) and disabled (taken from snapviews.lua "112.0"). Or at least it does on my widescreen monitor.

Rich

This doen't fix the track ir re-center view to original set ( wide on this case or at list to a specific FOV ) with zoom enabled.

 

example

-- Camera view angle limits {view angle min, view angle max}.

CameraViewAngleLimits = {}

CameraViewAngleLimits[PlaneIndex.iSu_27] = {20.0, 115.0}

CameraViewAngleLimits[PlaneIndex.iSu_33] = {20.0, 115.0}

CameraViewAngleLimits[PlaneIndex.iSu_25] = {20.0, 109.0}

CameraViewAngleLimits[PlaneIndex.iSu_39] = {20.0, 121.0}

CameraViewAngleLimits[PlaneIndex.iMiG_29] = {20.0, 112.0}

CameraViewAngleLimits[PlaneIndex.iMiG_29K] = {20.0, 112.0}

CameraViewAngleLimits[PlaneIndex.iA_10] = {20.0, 97.0}

CameraViewAngleLimits[PlaneIndex.iF_15] = {20.0, 107.0}

 

Example for Mig29 in snapviews.lua

 

Snap[5][13]["viewAngle"] = 112.0

Snap[5][13]["vAngle"] = -9

Snap[5][13]["hAngle"] = 0

No i mean they should be the same the view is my far or flying view "112" ( in the MiG ) and i cannot find the track IR center point view angle value, I understand that the track ir z axis have a center point and this center point is something like "60" that way the z axis allow the trackir user to go back and forward on that axis now what i'm trying to find is set the center point of the Z axis same as the far out FOV that would be 112 for me. Meaning i wouldn't have a back movement but only a forward movement from 112 to 20

Do i make sens ?

Thx

Mmmmmm. With the Z-axis enabled, you want the views.lua number to represent the maximum distance you can pull away with TrackIR. That way, when using TrackIR and the Z-axis, the most you can zoom out will be your default view. Yes?

If so, you don't control that in the sim. You control it through TrackIR. For the Mig-29, set view.lua CameraViewAngleLimits[PlaneIndex.iMiG_29] = {20.0, 208.0} and snapviews.lua Snap[5][13]["viewAngle"] = 112. Now you will enter the cockpit the same distance from the HUD both with and without the Z-axis enabled.

Next open TrackIR, select your profile and click EDIT. In the window that opens, highlight the Z axis and click "EDIT Z...". Make the right hand side flat and save:

Now, when you enter the cockpit with the Z-axis enabled, you'll be at your max zoom out distance. Is that what you're trying to do? Or have I once again completely misunderstood your intention?

Rich

Ironhand - Ahaa - I'll bear that in mind when I get the vector expansion (when BS is released & I upgrade, so I suspect a wee way off yet)

I was a bit surprised at your sounding so positive, when I knew that wasn't what I'd done a couple of days ago to change my default zooms...

Actually yes that is correct the result is good. I was hoping for a fix inside lockon but this can do the trick , I will look into it more in details from inside LC.

I think many guys will have to do this for now and should be on a sticky somewhere.

But here the problem that you will encounter by doing this ( 208 FOV view.lua) all sensitivity of your track ir will be "shifted" so you will have to built a profile specific to lockon only.

Like me i used one for all FSX F4 Condor lockon il2 stryke fighters etc.. They used to all share the same profile so you have just to remember to switch it back.

Thx Iron

If you dont turn off one side of the Z axis of track IR like in the above picture this will look like this

Ironhand - Ahaa - I'll bear that in mind when I get the vector expansion (when BS is released & I upgrade, so I suspect a wee way off yet)

I was a bit surprised at your sounding so positive, when I knew that wasn't what I'd done a couple of days ago to change my default zooms...

I've been confused myself over the wildly disparate advice being given over the months. I knew what had worked for me. Yet other people were reporting different results. I had realized early on that there was a difference between where TrackIR and the "keyboard" views got their default numbers. But it wasn't until yesterday that I realized that TrackIR itself gets its numbers from two different places depending on whether or not the Z-axis is enabled.

If you dont turn off one side of the Z axis of track IR like in the above picture this will look like this...

Unfortunately, yes. But in the past I've had different profiles, anyway, due to the sensitivity settings I wanted. So it doesn't seem like that big a deal to me to have a different LOMAC/FC profile.

Rich

Is this a stretch limo Mig-29 ?

LOL.. it remind me of Gliders pit that way :D