Pacific Fighters VE support

[Slice]

Hi there, I have just received the VE addon, and so far it looks great. One problem I run Pacific Fighters ......edit..... OK I see there is no support for this.. please change the front page on the website - it is currently misleading as VE is surrounded by many games and only 2 of these work with it.

Cheers

[ December 22, 2004, 03:20 PM: Message edited by: Slice ]

[warrenEBB]

actually,
Vector Expansion works with all of the games that are "TrackIR Enhanced."

But if the Game doesn't have a 3-D cockpit, you're just going to find it easier to perform the current head rotation. (With Vector Expansion working, only your true head rotation will rotate the view. leaning won't change the view at all).

Instead of removing games from the front page, i've been ordered to better designate which games support full 3-D motion. Still trying to think up a great way to do this.
For now, i've noted the full 3-D (or "6 Degrees of Freedom") games on our all games page, here:
http://www.naturalpoint.com/trackir/games/allgames.html

Also, please keep in mind that while Pacific Fighters has no plans to support full 3-D motion, many of the other games on our list are excited about patching this in. and the makers of Pacific Fighters have promised full 3-D Vector Expansion support in their next game (due out in early 2005)

[ December 23, 2004, 02:59 AM: Message edited by: Warren Blyth -webdev- ]

[stephenju]

Is it possible to convert the new movement in VE to keystrokes? Say for example, translate forward/backward movements to keys that control the gun sight views or zoom levels?

Or to control TIR itself. Like moving forward enables precision mode and moving backward disables it?

[ December 23, 2004, 12:01 PM: Message edited by: Stephen Chu ]

[warrenEBB]

that's a very cool idea!

this would probably work best as a modification of the TrackMapper utility (a 3rd paty app).

i'll bring this to the attention of the programmers here.

Thanks Stephen!

[Mave]

Hello... Let's post this here as well... I with the "idea" from www.virtualflightproductions.com created "Z-Axis" to work as zoom.
VFP just had idea to use Joy2Key or ControlMk.232 as keymapper, and that sucks, you can only set 2 keys for full "axis"... Did some searching on google and found the solution

So here it is:

Download and install PPJOY
Download and "install" Tir2Joy

And after you have figured out how to make those to work ...

Download and install AutoHotkey

and paste following script to whatever.ahk :::

code:; 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[/code]That has all the 13 "views" configured for Shift+Keys@Numpad, check "AutoHotkey" help if you want to put there your own.

I won't give any support to this solution, but I just say: It works. You get all 13 FOVs to your z-axis in 6DOF, the closer you go to your TIR, the more you'll zoom in.

That script shall be my christmaspresent for the community

Ps. That script might need some modifying before it works.
JoystickNumber = 4 ; Increase this to test a joystick other than the first.
JoystickAxis = y ; Set this to the axis you want to use.
Above 2 lines might need modifying...

- Mave
Jagdgeschwader 55 - "Lufthunden"
www.lufthunden.com

[ December 24, 2004, 02:38 PM: Message edited by: Mave_FI ]

[Mave]

Hehe, talking about "Precision mode", Implemented that as well
Add the following codelines before line "sleep, 25"
code: 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}
}[/code]So, what does that do: If you go "closer" than 23 in axis, it will send "F10 down" and when you get back to 24+ in axis, it will send "F10 up"
So I have F10 bind as "Precision mode" in TrackIR.
You must remember to remove the checkbox from "Toggle" in Precision mode, without the toggle, Precision mode is on when you keep the key down, and that's what the script does...

[ December 25, 2004, 05:40 AM: Message edited by: Mave_FI ]

[Charlie251]

Nice job Mave! I havent tried this out yet, but thanks for your support on getting the best out to the community.

You Rock!

PS: I agree... joy2key sucks. I uninstalled it after I made sure it worked!

PPS: I am going to add the link to this thread on our site so readers can check this out as well.

[ December 25, 2004, 07:17 AM: Message edited by: Charlie ]

[Mave]

I think I'll post a note to guys behind that AutoHotkey and ask I they would like to implement support for TIR 6dof as native, after that we would not need to use any Tir2Joy things...

Btw. If you did not figure it out yourself yet, by using similar script, you can actually get full programming-features to _all_ your old gameport-joysticks

Ps. Charlie, thank's for linking, but there's a typo in your page, it's http://www.autohotkey.com/ not http://www.anyhotkey.com/

[ December 25, 2004, 07:25 AM: Message edited by: Mave_FI ]

[morgath]

I�m using your script and it runs perfectly, it�s the better possible with the limits of FB-PF. very good work, mave.
i�m making an "tutorial" or instructions for the spanish users and will put it in this spanish popular page (in spanish language)
http://www.il2mania.com/
for help the spanish users installing the necessary programs and your script, (and giving you the credit for your work with my words and a link to this post, and respecting the total integrity of your script, )
i expect yo like the idea.
some people will help me with a traduction to english (my english is too bad) and i expect put it in this forum in a future (with your permission, of course)

[Charvel]

Ok, I have the PPJoy set up with a virtual joystick. check.

Running TIR2Joy and its showing update info.

I start the Autohotkey with your script.

Then FB and it doesn't work for me.

When you say increase Joystick=4 does that only apply if you have other virtual joysticks or PPjoysticks because I only created the one virtual joystick?

I do run a throttly, pedals and USB joystick so I don't know if this is it or...

Maybe it's because some of my keys in FB/PF are remapped to other things (for my CH throttle setup)? Do I have to map these views to the shift+numpad values?

Thank you, I'd really like to give this a go!