Page 2 of 6

Re: Pacific Fighters VE support

Posted: Wed Feb 23, 2005 11:34 pm
by morgath
Hello Charvel , i�m not the author but maybe i can help.
check this (all):
1 - in the TIR profile you are using for PF all axis are operative. (in default profile for FB/PF, zoom axis isn�t operative)
2 - open the virtual joystick (you only need one) in the windows control panel, open TIR and tir2joy too, and test if your head move the joystick axis, if it makes it, your "Joystick = *" value is correct, if not, check it changing the value "4" for different values like 2, 3, 4 etc... not coincident with your real peripheals. (sometimes this can use unexplicable values, don�t worry for that, it�s not a problem)
-Set in controls panel in FB/PF the next values:

Wide view = Numpad +; Fov 85 = Numpad -; FOV 80 = Numpad *;

FOV 75 = Numpad 1; Normal View = Numpad 2; FOV 65 = Numpad 3;

FOV 60 = Numpad 4, FOV 55 = Numpad 5; FOV 50 =Numpad 6;

FOV 45 = Numpad 7;, FOV 40 = Numpad 8; Fov 35 = Numpad 9; Gunsight View = Numpad Insert

and reserve this keys, no use or combine with
Shift, control or alt, in another function.

if the movement is incorrect, (erratic, for example) maybe the autohotkey is using an incorrect axis, check tis line in the mave F1 text:
JoystickAxis = y
and change the "Y" for: "X" or "Y"
"Z" "R" "U" "V" (more common is "V")

if it now runs, remenber that you can adjust the distance and movement progression with the windows settings of the virtual joystick
if not run,(or not understand something) don�t worry, continue asking here.
sure it will be easy of repair.
good luck

Re: Pacific Fighters VE support

Posted: Thu Feb 24, 2005 9:44 am
by Charvel
quote:Originally posted by morgath:
Hello Charvel , i�m not the author but maybe i can help.
check this (all):
1 - in the TIR profile you are using for PF all axis are operative. (in default profile for FB/PF, zoom axis isn�t operative)
2 - open the virtual joystick (you only need one) in the windows control panel, open TIR and tir2joy too, and test if your head move the joystick axis, if it makes it, your "Joystick = *" value is correct, if not, check it changing the value "4" for different values like 2, 3, 4 etc... not coincident with your real peripheals. (sometimes this can use unexplicable values, don�t worry for that, it�s not a problem)
-Set in controls panel in FB/PF the next values:

Wide view = Numpad +; Fov 85 = Numpad -; FOV 80 = Numpad *;

FOV 75 = Numpad 1; Normal View = Numpad 2; FOV 65 = Numpad 3;

FOV 60 = Numpad 4, FOV 55 = Numpad 5; FOV 50 =Numpad 6;

FOV 45 = Numpad 7;, FOV 40 = Numpad 8; Fov 35 = Numpad 9; Gunsight View = Numpad Insert

and reserve this keys, no use or combine with
Shift, control or alt, in another function.

if the movement is incorrect, (erratic, for example) maybe the autohotkey is using an incorrect axis, check tis line in the mave F1 text:
JoystickAxis = y
and change the "Y" for: "X" or "Y"
"Z" "R" "U" "V" (more common is "V")

if it now runs, remenber that you can adjust the distance and movement progression with the windows settings of the virtual joystick
if not run,(or not understand something) don�t worry, continue asking here.
sure it will be easy of repair.
good luckFirst of all thanks very much for your help, morgath!

Okay, still not working but here's what I've done:

1) checked TIR profile (custom) and all axes, including "Y" are enabled.

2) Opened virtual joystick in control panel, just shows that there's a virtual joystick there. Not sure if this window needs to be open so I left it open. Should I be using one of the other shortcuts to open (eg. PPjoyCOM, PPjoyKEY, PPjoyMOUSE...etc.)? I tried having the PPjoyMouse open anyway on another attempt.

3) Make sure TIR software is on and open TIR2JOY. It shows a window with X, Y values constantly changing (very fast). It seems to react to my headmovements. I leave this window open.

4) Start Hotkey program with the script pasted into the AutoHotkey.ini. Double-clicking the tray icon shows this:

quote:Script lines most recently executed (oldest first). Press [F5] to refresh.
The seconds elapsed between a line and the one after it is in parens to the right (if not 0).
The bottommost line's elapsed time is the number of seconds since it executed.

091: if joystate between 072 and 100
097: Sleep,25 (0.03)
098: }
017: {
018: GetKeyState,joystate,%JoystickNumber%Joy%JoystickAxis%
019: if joystate between 000 and 013
025: if joystate between 014 and 018
031: if joystate between 019 and 023
037: if joystate between 024 and 028
043: if joystate between 029 and 033
049: if joystate between 034 and 038
055: if joystate between 039 and 043
061: if joystate between 044 and 048
067: if joystate between 049 and 056
068: if sent_button <> 9
073: if joystate between 057 and 061
079: if joystate between 062 and 066
085: if joystate between 067 and 071
091: if joystate between 072 and 100
097: Sleep,25 (0.03)
098: }
017: {
018: GetKeyState,joystate,%JoystickNumber%Joy%JoystickAxis%
019: if joystate between 000 and 013
025: if joystate between 014 and 018
031: if joystate between 019 and 023
037: if joystate between 024 and 028
043: if joystate between 029 and 033
049: if joystate between 034 and 038
055: if joystate between 039 and 043
061: if joystate between 044 and 048
067: if joystate between 049 and 056
068: if sent_button <> 9
073: if joystate between 057 and 061
079: if joystate between 062 and 066
085: if joystate between 067 and 071
091: if joystate between 072 and 100
097: Sleep,25 (0.03)
098: }
017: {
018: GetKeyState,joystate,%JoystickNumber%Joy%JoystickAxis%
019: if joystate between 000 and 013
025: if joystate between 014 and 018
031: if joystate between 019 and 023
037: if joystate between 024 and 028
043: if joystate between 029 and 033
049: if joystate between 034 and 038
055: if joystate between 039 and 043
061: if joystate between 044 and 048
067: if joystate between 049 and 056
068: if sent_button <> 9
073: if joystate between 057 and 061
079: if joystate between 062 and 066
085: if joystate between 067 and 071
091: if joystate between 072 and 100
097: Sleep,25 (0.03)
098: }
017: {
018: GetKeyState,joystate,%JoystickNumber%Joy%JoystickAxis%
019: if joystate between 000 and 013
025: if joystate between 014 and 018
031: if joystate between 019 and 023
037: if joystate between 024 and 028
043: if joystate between 029 and 033
049: if joystate between 034 and 038
055: if joystate between 039 and 043
061: if joystate between 044 and 048
067: if joystate between 049 and 056
068: if sent_button <> 9
073: if joystate between 057 and 061
079: if joystate between 062 and 066
085: if joystate between 067 and 071
091: if joystate between 072 and 100
097: Sleep,25 (0.03)
098: }
017: {
018: GetKeyState,joystate,%JoystickNumber%Joy%JoystickAxis%
019: if joystate between 000 and 013
025: if joystate between 014 and 018
031: if joystate between 019 and 023
037: if joystate between 024 and 028
043: if joystate between 029 and 033
049: if joystate between 034 and 038
055: if joystate between 039 and 043
061: if joystate between 044 and 048
067: if joystate between 049 and 056
068: if sent_button <> 9
073: if joystate between 057 and 061
079: if joystate between 062 and 066
085: if joystate between 067 and 071
091: if joystate between 072 and 100
097: Sleep,25 (0.03)
098: }
017: {
018: GetKeyState,joystate,%JoystickNumber%Joy%JoystickAxis%
019: if joystate between 000 and 013
025: if joystate between 014 and 018
031: if joystate between 019 and 023
037: if joystate between 024 and 028
043: if joystate between 029 and 033
049: if joystate between 034 and 038
055: if joystate between 039 and 043
061: if joystate between 044 and 048
067: if joystate between 049 and 056
068: if sent_button <> 9
073: if joystate between 057 and 061
079: if joystate between 062 and 066
085: if joystate between 067 and 071
091: if joystate between 072 and 100
097: Sleep,25 (0.03)
098: }
017: {
018: GetKeyState,joystate,%JoystickNumber%Joy%JoystickAxis%
019: if joystate between 000 and 013
025: if joystate between 014 and 018
031: if joystate between 019 and 023
037: if joystate between 024 and 028
043: if joystate between 029 and 033
049: if joystate between 034 and 038
055: if joystate between 039 and 043
061: if joystate between 044 and 048
067: if joystate between 049 and 056
068: if sent_button <> 9
073: if joystate between 057 and 061
079: if joystate between 062 and 066
085: if joystate between 067 and 071
091: if joystate between 072 and 100
097: Sleep,25 (0.03)
098: }
017: {
018: GetKeyState,joystate,%JoystickNumber%Joy%JoystickAxis%
019: if joystate between 000 and 013
025: if joystate between 014 and 018
031: if joystate between 019 and 023
037: if joystate between 024 and 028
043: if joystate between 029 and 033
049: if joystate between 034 and 038
055: if joystate between 039 and 043
061: if joystate between 044 and 048
067: if joystate between 049 and 056
068: if sent_button <> 9
073: if joystate between 057 and 061
079: if joystate between 062 and 066
085: if joystate between 067 and 071
091: if joystate between 072 and 100
097: Sleep,25 (0.03)
098: }
017: {
018: GetKeyState,joystate,%JoystickNumber%Joy%JoystickAxis%
019: if joystate between 000 and 013
025: if joystate between 014 and 018
031: if joystate between 019 and 023
037: if joystate between 024 and 028
043: if joystate between 029 and 033
049: if joystate between 034 and 038
055: if joystate between 039 and 043
061: if joystate between 044 and 048
067: if joystate between 049 and 056
068: if sent_button <> 9
073: if joystate between 057 and 061
079: if joystate between 062 and 066
085: if joystate between 067 and 071
091: if joystate between 072 and 100
097: Sleep,25 (0.03)
098: }
017: {
018: GetKeyState,joystate,%JoystickNumber%Joy%JoystickAxis%
019: if joystate between 000 and 013
025: if joystate between 014 and 018
031: if joystate between 019 and 023
037: if joystate between 024 and 028
043: if joystate between 029 and 033
049: if joystate between 034 and 038
055: if joystate between 039 and 043
061: if joystate between 044 and 048
067: if joystate between 049 and 056
068: if sent_button <> 9
073: if joystate between 057 and 061
079: if joystate between 062 and 066
085: if joystate between 067 and 071
091: if joystate between 072 and 100
097: Sleep,25 (0.03)
098: }
017: {
018: GetKeyState,joystate,%JoystickNumber%Joy%JoystickAxis%
019: if joystate between 000 and 013
025: if joystate between 014 and 018
031: if joystate between 019 and 023
037: if joystate between 024 and 028
043: if joystate between 029 and 033
049: if joystate between 034 and 038
055: if joystate between 039 and 043
061: if joystate between 044 and 048
067: if joystate between 049 and 056
068: if sent_button <> 9
073: if joystate between 057 and 061
079: if joystate between 062 and 066
085: if joystate between 067 and 071
091: if joystate between 072 and 100
097: Sleep,25 (0.02)

Press [F5] to refresh.Tried creating my own .AHK file and starting AuotHotkey with that but no luck. When opening it up in Notepad it shows this:

quote:; TrackIR Zoom Script for IL2FB/AEP/PF
; http://www.lufthunden.com
; This script is used to send single keypresses to manage FOV in IL2.
; =LH=Mave's Xmas present for the IL2 community

#SingleInstance
SetFormat, float, 03 ; Omit decimal point from axis position percentages.
JoystickNumber = 4 ; Increase this to test a joystick other than the first.
JoystickAxis = y ; Set this to the axis you want to use.
GetKeyState, axis_count, %JoystickNumber%JoyAxes
if axis_count < 1
{
MsgBox Joystick #%JoystickNumber% does not appear to be attached to the system.
ExitApp
}
Loop
{
GetKeyState, joystate, %JoystickNumber%Joy%JoystickAxis%
if joystate between 000 and 013
ifNotEqual, sent_button, 1
{
sent_button = 1
Send, +{Numpad0 1}
}
if joystate between 014 and 018
ifNotEqual, sent_button, 2
{
sent_button = 2
Send, +{Numpad9 1}
}
if joystate between 019 and 023
ifNotEqual, sent_button, 3
{
sent_button = 3
Send, +{Numpad8 1}
}
if joystate between 024 and 028
ifNotEqual, sent_button, 4
{
sent_button = 4
Send, +{Numpad7 1}
}
if joystate between 029 and 033
ifNotEqual, sent_button, 5
{
sent_button = 5
Send, +{Numpad6 1}
}
if joystate between 034 and 038
ifNotEqual, sent_button, 6
{
sent_button = 6
Send, +{Numpad5 1}
}
if joystate between 039 and 043
ifNotEqual, sent_button, 7
{
sent_button = 7
Send, +{Numpad4 1}
}
if joystate between 044 and 048
ifNotEqual, sent_button, 8
{
sent_button = 8
Send, +{Numpad3 1}
}
if joystate between 049 and 056
ifNotEqual, sent_button, 9
{
sent_button = 9
Send, +{Numpad2 1}
}
if joystate between 057 and 061
ifNotEqual, sent_button, 10
{
sent_button = 10
Send, +{Numpad1 1}
}
if joystate between 062 and 066
ifNotEqual, sent_button, 11
{
sent_button = 11
Send, +{NumpadMult 1}
}
if joystate between 067 and 071
ifNotEqual, sent_button, 12
{
sent_button = 12
Send, +{NumpadSub 1}
}
if joystate between 072 and 100
ifNotEqual, sent_button, 13
{
sent_button = 13
Send, +{NumpadAdd 1}
}
Sleep, 25
}
return*copy/pasted here

5) Start PF and change all values for FOV to what you specified. I thought these were supposed to be "shift"+ numpad x but I just did them exactly as you said and removed any other assignments to these keys.

6) Try a QMB and get nothing. TIR works as always but not a hint of any key changes or anomolous stuff happening.

I'm probably just doing something dumb but after spending all this time on it I'm kind of determined to figure it out.

Thanks again for your help.

Re: Pacific Fighters VE support

Posted: Thu Feb 24, 2005 9:46 am
by Charvel
Oh, not sure if this means anything but I think the TIR2JOY shows "nodata" when I come out of PF after trying it out.

Re: Pacific Fighters VE support

Posted: Fri Feb 25, 2005 4:31 am
by morgath
o.k I understand, tir and tir2joy seem run well but you need to test this:
with TIR and TIR2JOY on,
1) Open the control panel/ games controllers
and select the virtual joystick, open it with the properties and check if your head move the joystick axis, if it makes it your virtual joystick is running well too and you can continue, if not, here is the problem, you need reinstall it.

when it runs well, observe what is the zoom axis (probably x-rotation) that you are using for your zoom movement and you can configure it with the config set in the same window. (ignore the other axis in the calibration, you not need them for the zoom)

2) Now open an new .txt and copy/paste the script in this link: (use THIS script, not your old script)

il2mania/instruccioneszoomPF

, saving it with this name FBzoom.ahk
the script is in the text of this spanish instructions (maybe in a few days will appear an english version); (don�t worry i.ll not make the traduction )
but i can�t cut it and copy here, i don�t know why when i send this reply the natural point forum rejected it if the script is copied in. i�ll investigate it later.



with tir and tir2joy on, perform a double click on the archive FBzomm.ahk
(ignore the program autohotkey or the autohotkey.ini, you`ll not need make nothing with this, if you make changes in autohotkey.ini remove the changes or reinstall the program)

the program appears in your taskbar?, well. continue to the next point
if not: edit the FBzoom.ahk and change in this text line:

----

"JoystickNumber = 2 ; Increase this to test a joystick other than the first."

----

this value: 2
for another (3, 4...)

restart FBzoom.ahk and check if it appears in the taskbar., make this whith diferent values until it works.

probably the zoom works now, you can test it making this:
remenber, tir and tir2joy and pfzoom.ahk on
open a new text document (it�s provisional)
and write something in.
set the bloqNum on in the keyboard (remenber put it off when you finish the test))
move your head in zoom axis but use all axis too
if the numbers 1,2....9 and simbols *-+ appears in the text The zoom is operative at this point
but its possible that they are using a diferent axis, you can set this�editing the fbzoom.ahk and changing in this line the value: V

---

"JoystickAxis = V ; Set this to the axis you want to use."

---

(if you used the x-rotation axis in the Virtual Joystick probably this value is correct and not need more changes)

this part is explained in mi last post, it�s copied here:
"if the movement is incorrect, (erratic, for example) maybe the autohotkey is using an incorrect axis, check tis line in the mave F1 text:
JoystickAxis = V
and change the "V" for: "X" or "Y"
"Z" "R" "U" (more common is "V")

if it now runs, remenber that you can adjust the distance and movement progression with the windows settings of the virtual joystick"

but at this point the zoom is working,SURE, maybe need some final detais but it will be easy, if need help explain me what,s not working in the process, or if your zoom theorically works but it,s imposible to use it, i have no more time now but i will continue..

Remenber that you not need use more programs or archives than this:
the setting of virtual joystick, TIR VE, tir2joy, and fbzoom.ahk.
not touch or change nothing and not execute the ppjoy, or anyhotkey, anyhotkey.ini, or nothing more. it only will serve for become you more confused.

good luck

Re: Pacific Fighters VE support

Posted: Fri Feb 25, 2005 12:03 pm
by Charvel
It's ALIVE!!

You sir, are a scholar and a gentleman!

Thank you very much for your help and patience.

cheers!

Re: Pacific Fighters VE support

Posted: Fri Feb 25, 2005 6:20 pm
by 3ra_Luke
Hi all.
Just a lines to thank Mave_FI for his great idea and incredible Autohotkey script, and to Morgath (Hola colega!) to help me to sucessfully make it work.

I�ve been using the zoom on dogfights and works great.
The only problems I�ve noticed are:
1. The need of opening 2 programs (AHK and tir2joy)
2. After exiting from a game, tir2joy deactivates.

For the first one, does anybody knows a way to make some kind of batch file or if there is a program out there (maybe AHK can do it) to open AHK script, open tir2joy AND (this could be great) send t2j to tray (or minimize, but in tray could be the best option), all-in-a-row?

Mave_Fi, as you seem to know well how AHK works, can it be done with this program? Could you make an script for that purpose?

For the second problem, maybe theres not a solution, cause as the TIR software deactivates the "Enhanced" mode after exiting from game, maybe it turns crazy to tir2joy...

Can anybody help? Thank you very much!

Re: Pacific Fighters VE support

Posted: Fri Feb 25, 2005 6:28 pm
by 3ra_Luke
I�ve found a AHK that minimizes any window using Win+H
http://www.autohotkey.com/docs/scripts/ ... ayMenu.htm

If we could find a way to combine this script with the TIR script and with tir2joy, could be incredible!

Any idea? I think I�ll post this question on AHK forums.

Re: Pacific Fighters VE support

Posted: Fri Feb 25, 2005 8:40 pm
by morgath
quote:Originally posted by Charvel:
It's ALIVE!! great news, Charvel, i,m happy to see it working for you, and you know, if need something more, here i am, but now, be fun with the zoom.
probably you will notice now better performance in deflection shooting.
�bad day for your virtual enemies!

P.D visit this thread from time to time, maybe the development continue looking for better performance.

see you long, friend

[ February 26, 2005, 03:43 AM: Message edited by: morgath ]

Re: Pacific Fighters VE support

Posted: Sat Feb 26, 2005 2:47 am
by Charvel
quote:Originally posted by morgath:
quote:Originally posted by Charvel:
It's ALIVE!! great news, Charvel, i,m happy to see it working for you, and you know, if need something more, here i am, but now, be fun with the zoom.
probably you will notice now better performance in deflection shooting.
�bad day for your virtual enemies!

P.D visit this thread from time to time, maybe the development continue looking for better performance.

see you long, friendYou're the man morgath.

Not sure if I'm any better at deflection shooting but the immersion factor has gone up with some tweaks (for comfort) to the Z axis in my custom profile.

I love the fact that we can really fine-tune the axes by deselecting mirror and was the first thing I did when testing the beta. Due to the way we sit in a chair it tends to make more sense to have more sensitivity leaning back as you don't really have as much room to move than leaning forward.

Next I'm going to add the other script for precision mode but that might have to wait till I'm back from vacation next week.

Anyway, thanks again. I'll be directing some squadmates who are buying vector to try this out.

Re: Pacific Fighters VE support

Posted: Sat Feb 26, 2005 4:50 am
by 3ra_Luke
Charvel,and for increase your happyness, here�s the Mave�s full script with some bonus:

1. When you load this script, tir2joy is automatically loaded, with its window hidden.
2. Added a key (Alt+F11) for closing at the same time the Mave_Fi script and tir2joy.
3.Added two keys (Alt+F9 and Alt+F10) for showing or hide again the tir2joy window.

For example, I use one button on my Logitech multimedia keyborad to load the full script, and other button for close it.

Notice that I�ve used my own directory, where I have tir2joy (C:\Juegos\IL2.....\tir2joy) You must use your own route.

code:
; AutoHotkey Version: 1.x
; Language: English
; Platform: Win9x/NT
; Author: A.N.Other
;
; Script Function:
; Template AutoHotkey script.
;

; TrackIR Zoom Script for IL2FB/AEP/PF
; http://www.lufthunden.com
; This script is used to send single keypresses to manage FOV in IL2.
; =LH=Mave's Xmas present for the IL2 community
#SingleInstance
#Persistent ; will keep your script active
Run, tir2joy.exe, C:\Juegos\IL-2 Sturmovik Forgotten Battles\tir2joy, Hide, tir2joy

SetFormat, float, 03 ; Omit decimal point from axis position percentages.
JoystickNumber = 2 ; Increase this to test a joystick other than the first.
JoystickAxis = V ; Set this to the axis you want to use.
GetKeyState, axis_count, %JoystickNumber%JoyAxes
if axis_count < 1
{
MsgBox Joystick #%JoystickNumber% does not appear to be attached to the system.
ExitApp
}
Loop
{
GetKeyState, joystate, %JoystickNumber%Joy%JoystickAxis%
if joystate between 000 and 013
ifNotEqual, sent_button, 1
{
sent_button = 1
Send, +{Numpad0 1}
}
if joystate between 014 and 018
ifNotEqual, sent_button, 2
{
sent_button = 2
Send, +{Numpad9 1}
}
if joystate between 019 and 023
ifNotEqual, sent_button, 3
{
sent_button = 3
Send, +{Numpad8 1}
}
if joystate between 024 and 028
ifNotEqual, sent_button, 4
{
sent_button = 4
Send, +{Numpad7 1}
}
if joystate between 029 and 033
ifNotEqual, sent_button, 5
{
sent_button = 5
Send, +{Numpad6 1}
}
if joystate between 034 and 038
ifNotEqual, sent_button, 6
{
sent_button = 6
Send, +{Numpad5 1}
}
if joystate between 039 and 043
ifNotEqual, sent_button, 7
{
sent_button = 7
Send, +{Numpad4 1}
}
if joystate between 044 and 048
ifNotEqual, sent_button, 8
{
sent_button = 8
Send, +{Numpad3 1}
}
if joystate between 049 and 056
ifNotEqual, sent_button, 9
{
sent_button = 9
Send, +{Numpad2 1}
}
if joystate between 057 and 061
ifNotEqual, sent_button, 10
{
sent_button = 10
Send, +{Numpad1 1}
}
if joystate between 062 and 066
ifNotEqual, sent_button, 11
{
sent_button = 11
Send, +{NumpadMult 1}
}
if joystate between 067 and 071
ifNotEqual, sent_button, 12
{
sent_button = 12
Send, +{NumpadSub 1}
}
if joystate between 072 and 100
ifNotEqual, sent_button, 13
{
sent_button = 13
Send, +{NumpadAdd 1}
}
if joystate between 000 and 023 ;If state "023" or below, enable precision mode
ifNotEqual, precision_mode, 1
{
precision_mode = 1
Send, {F10 down}
}
if joystate between 024 and 100 ;If state "024" or more, disable precision mode
ifNotEqual, precision_mode, 0
{
precision_mode = 0
Send, {F10 up}
}

Sleep, 25
}
return



!F11:: ; ALT+F11 to close both programs
Process, Close, tir2joy.exe ; kill your proggy
ExitApp ; quit AHK
return

!F9:: ; ALT+F9 to show the window
WinShow, TrackIR2Joystick v1.2
Return

!F10:: ; ALT+F10 to hide the window
WinHide, TrackIR2Joystick v1.2
Return


#NoTrayIcon[/code]Enjoy!!

(BTW, can you explain that about deactivate "mirror"? I�ve been using a very flat curve for Z axis, to avoid oversensitive zoom with this script. How have you modified your curve?

Tnx)