TrackIR question

[BadAries]

Hi
I have some questions/problems about using TrackIR in GPL. I am using TrackIR 4 pro with Software 4.1 Build 28.

I got my TIR working in GPL. However, when I tried to set the deadzone to any number other than zero, the yaw won't work anymore. I set it back to zero, yaw works again.

Then I went to the TrackIR software, put the acceleration to deadzone, it seems having no effect at all. Does the ini file override the TrackIR software?

What do you guys drive on GPL with the max degree?

When I have the TrackIR software running, I heard the game will have some "dun dun dun dun..." sound continuosly. If I shutdown TrackIR Software

A non TrackIR related question. Can gplshift able to emulate the Shift-t?

[JSJ]

Hi BadAries

I will recommend that you only use one of the DZ support to avoid conflict:
e.g disable TrackIR's DZ, Enable GPLshift+ e.g:
LookLeftRightDeadZone = 2
Please notice that the numberpad keys will change the DZ level (not in replay mode)
e.g key 9 (PgUp) will set the DZ to max. 90% - key 0 (int) = no DZ, are you using
numberkeys to other purpose? I will make a On/Off option for using the numberkeypad
in next GPLshift version (0.72).

I am using max. about 45-55 degree, most natural for me with 19" monitor

No "dun dun dun dun..." here with P4 HT 3GHz - that Pc do you have, fast? using lates Carset,
Tracks?

GPLshift does not support Shift-T, but I will try to add it later if possible.

Please let me know if you still have problems.

Sorry for my English.

JSJ

[Bob_Simpson]

I see the line UserDefineFOV in the GPLShift.ini, but can you tell me how to generate that hex number for different angles? Or at least give the values here for 40°, 45°, 50° and 55°?

[JSJ]

bobsimpson said:

I see the line UserDefineFOV in the GPLShift.ini, but can you tell me how to generate that hex number for different angles? Or at least give the values here for 40°, 45°, 50° and 55°?

Hi Bob

GPL Angle2Hex by Costas Sourelis sayed:
"UserDefineFOV = "
40 42200000
45 42340000
50 42480000
55 425C0000
Or just use e.g wheel buttons to move to the position you want and then save it with the HOME key.

BTW "UserDefineFOV = " or "UserDefineSOV = "have nothing to do with TrackIR Look Left/Right max. setting
it's only for the old 2D Zoom In/Out - use "LookLRMaxAngle = " for TrackIR.

Edit:
oh, now I better understand why you are interest in
"UserDefineFOV = " with TrackIR setup:
forum.rscnet.org/showthread.php?t=243724#6

Sorry for my English

JSJ

[Bob_Simpson]

Let me try to understand GPLShift. I thought that if TrackIR wasn't running, I could set the FOV with the arrow keys and save the setting with Home and have that setting the same when I re-enterd GPL with TrackIR. If that's not saved, what FOV do I have when I go into GPL with TrackIR. It looked to me like I had roughly a 60° angle FOV.

I measured that 60° angle from the overhead view. At Monza, I drove forward until the ends of the start/finish lines were at the edges of the screen. The side views with TrackIR at the 122° setting in GPLShift.ini seem to be about an FOV of 90°. So I worry that starting out looking forward at 60°, when I start to move the view to the side, it might change to 90° suddenly.

What SOV angle is used? Are they set by default to some value?

Oh, when you say that the UserDefine values have nothing to do with TIR look left/right max, won't a wider angle SOV allow you to see further behind? I thought that the 122° angle referred to the centre of the viewing FOV.

>> OK, let me restate this. It sounds like I can set the angle of the FOV and SOV in the UserDefine lines. They don't affect the angle that you can turn your "head", but the SOV will change the edge of the view. So a LookLRMaxAngle of 122° plus half of the 90° SOV on each side that I think that I have gives 122 + 45 =167° range to each side, close to the 300° range that I roughly measured for the full viewing range.

[Bob_Simpson]

I've never trusted my running that GPL_angle2hex program.

The values that I see are:
40° C2B8323F
45° DB0F493F
50° F3665F3F
55° 0BBE753F

Why are we getting different values?

[BadAries]

Thanks JSJ

The dun dun dun sounds is not repro after a restart.

For the dead zone, I have to set it to Zero. Right now I am able to use the TrackIR software for that purpose. However, per your email, I should disable TrackIR deadzone but enable the one in GPLShift. How can I do disable it in TrackIR?

For those fov hex number, if I am using TIR, I don't have to worry about it, right?

Can some one please provide me more documents about the num key change the dz? I am so confuse about this feature.

Yep, if Shift-T could be added to some later version of GPLShift, that will be great.

Thanks again JSJ.

[Bob_Simpson]

JSJ,

The values that you've shown are outside of the range that you show in the GPLShift.ini I've tried that gpl_angle2hex program, but the numbers that come up don't change the FOV.

Also, putting your numbers in don't change the view.

"Front Of View (also for 45 degree Side Of View) (a 8 digits hex # between 3F4A0000 and 3FC03DA8) "

[JSJ]

bobsimpson said:

JSJ,

The values that you've shown are outside of the range that you show in the GPLShift.ini I've tried that gpl_angle2hex program, but the numbers that come up don't change the FOV.

Also, putting your numbers in don't change the view.

"Front Of View (also for 45 degree Side Of View) (a 8 digits hex # between 3F4A0000 and 3FC03DA8) "

Yes my numbers was wrong, Sorry

BTW: I have released v0.7.2.0 (0.72) where the numbers has been change to degrees e.g the default: 78.0

JSJ

[Bob_Simpson]

admin said:

BTW: I have released v0.7.2.0 (0.72) where the numbers has been change to degrees e.g the default: 78.0

JSJ

Hey! This is great news indeed. Have you announced it at RaceSimCentral? Should I mention something there?

Cheers, Bob

[JSJ]

bobsimpson said:

admin said:

BTW: I have released v0.7.2.0 (0.72) where the numbers has been change to degrees e.g the default: 78.0

JSJ

Hey! This is great news indeed. Have you announced it at RaceSimCentral? Should I mention something there?

Cheers, Bob

Thanks for the offer Bob, but I have announce "now"