TrackIR/Freetrack FOV control

[lelek]

Hello everybody,

Just wanted to post a request to the dev's to implement an option to control Field of View (Zoom) with z-axis movements of TrackIR/Freetrack instead of moving back and forth in the cockpit.

I'think this setup would greatly improve my dogfighting skills since abrupt changes of FOV settings with a button usualy make me lose sight of the enemy.

For me it would be a much better sollution to use head tracking for FOV change and a button for toggling different, useful "center" spots around the cockpit.

Maybe someone in the community already has a workaround for this? GlovePIE or PPJoy maybe?

Thanks, I'm enjoing the game and hope the rest of the problems clear up easily.

[1.JaVA_Platypus]

To tell you the truth, I think this is highly preferential. I have the wide/medium/close views programmed on a POV hat on my joystick and the SHIFT F1 as well. I've been using this set-up with Il-2 (1946) for years. So, I hope they don't change it

[Extreme_One]

Originally Posted by 1.JaVA_Platypus

To tell you the truth, I think this is highly preferential. I have the wide/medium/close views programmed on a POV hat on my joystick and the SHIFT F1 as well. I've been using this set-up with Il-2 (1946) for years. So, I hope they don't change it

That's exactly what I do too. Perfect.

I'm not trying to stifle other's choices but just saying what works for me.

[Dazzed DJ]

I also have track IR 5 and use the FOV change on joystick, I find it more helpful the way it is, sorry. Also if you zoom in with the FOV do you notice that dots at exteam distance disapear or become to small to see so the wide setting is best for looking for others while the close good for targeting work. .
I am not saying that your option does not mater mate but am adding my 2c to the debate. Maybe if there is an option box to have it one way or the other, that is when the development team has fixed the major bugs.

[brando]

I gave up using the FoV three positions and instead used the incremental 'zoom' toggle and the Shift+F1 option. I also use TIR_5 and the pro-clip, but the head forward and back isn't working well. Maybe I need to use the Loosen straps command to make it work properly - just a thought?

[MadBlaster]

This might work for you OP. Glovepie script just wrote for myself today. Allows you to zoom FOV style with your hat at 90 degrees, and snap back to FOV 90 with hat at 270 degrees. You need to measure your monitor height in mickeys and substitute your numbers for what I have in there. You do this with the debug command in Glovepie (i.e., debug=mouse.DirectInputY). Using your up/ down arrow keys, starting at the top and scrollling down to the bottom...note the difference in mickeys and put that number in the script in place of what I have. See my notes for rest. It's a bit clunky but it does the job.

*GLOBAL
var.mcx=640/2 //game resolutions
var.mcy=480/2//game resolutions

if var.mcy=480/2 then //changes zoom variable when game resolution changes
var.mckmstr=480
elseif var.mcy=600/2 then
var.mckmstr=600
elseif var.mcy=768/2 then
var.mckmstr=768
elseif var.mcy=864/2 then
var.mckmstr=864
endif

*ZOOM [HotKey viewset]
if (joystick1.pov1=90.00 and var.a=0) then
key.PageDown=true //FOV to 90
key.PageDown=false
mouse.cursorposx=var.mcx //initilze cursor, var.mcx and var.mcy equal to game resolution divided by 2 so that mouse cursor is centered.
mouse.cursorposy=var.mcy
mouse.cursorposy=0 //intialize mickey count
var.mick=mouse.DirectInputY //initialize mickey count
var.a=1 //start action
endif
if (joystick1.pov1=90.00 and var.a=1) or (joystick1.pov1=90.00 and var.a=2) then //action
key.Alt=true //"hold to adjust field of view" mapped to Alt-Z
key.Z=true
mouse.DirectInputY=mouse.DirectInputY+20 //cursor moves -y direction, sensitivity set here
endif
if (abs(mouse.DirectInputY)-abs(var.mick) > var.mckmstr) and var.a=1 then //first stage ends
key.Delete=true //opens the door to further zoom
key.Delete=false
mouse.cursorposx=var.mcx //initilze cursor, var.mcx and var.mcy equal to game resolution divided by 2 so that mouse cursor is centered.
mouse.cursorposy=var.mcy
mouse.cursorposy=0 //initialize mickey count
var.mick=mouse.DirectInputY //initialize mickey count
var.a=2 //kick back to action
endif
if (abs(mouse.DirectInputY)-abs(var.mick) > var.mckmstr) and var.a=2 then //second stage ends
var.a=3
key.Alt=false //job done, turn off now
key.Z=false
endif
if released(joystick1.pov1=90.00) then
var.a=0 //reinitialize variables to do it again
var.mick=0
mouse.DirectInputY=0
key.Alt=false
key.Z=false
mouse.cursorposx=var.mcx //initilze cursor, var.mcx and var.mcy equal to game resolution divided by 2 so that mouse cursor is centered.
mouse.cursorposy=var.mcy
endif
if (joystick1.pov1=270.00) then //snap back to FOV 90
key.PageDown=true
key.PageDown=false
endif

[335th_GRAthos]

Originally Posted by Extreme_One

That's exactly what I do too. Perfect.

I'm not trying to stifle other's choices but just saying what works for me.

+1

[jimbop]

Discussed (with solutions) in thus thread: http://forum.1cpublishing.eu/showthread.php?t=20697

[lelek]

Ok. I've managed to work out something that works for me.
I'm using this little GlovePIE script:

PIE.FrameRate = 108 Hz
if Pressed(q) then
if var.a=1 then
var.a=0
Release(Mouse.MiddleButton)
Else
var.a=1
Key.End = True
Key.End = False
endif
endif

if var.a=1 then
Mouse.MiddleButton = True
Mouse.DirectInputY = RealTrackIR.z * 6
endif

For this to work you have to map middle mouse button to "Hold to adjust FOV" setting within CoD, and put z-axis sensitivity in FreeTrack to minimum (this basicaly swiches off back and forth movement in cockpit). (For some reason FakeTrackIR.z = 0 didn't work. This is a workaround).

How it works is when you press the "q" button z-axis will controll FOV but you won't be able to use the mouse until you press "q" again to regain control of the mouse and that's about it.
You can play with the number - (* 6) to adjust sensitivity or change the buttons if you want.

[MadBlaster]

Right on guy I guess you have 3 point cap? I'm only single point, so no Z axis data. Anyway, it's good to see another guy figure it out. We will conquer CLOD in short order.