TrackIR Behavior with 1.5.4 Release

[BitMaster]

Tbh, I like it alot !!!

 

Much more natural from where I look and what I get to see.

 

Maybe you need to rearrange your setup a bit but it aint unusable.

[Livers]

You guys can make quick simple adjustments to get it perfect.

 

Please share your TIR5 profile for the A10, if you would. I have yet to find a solution that will let me get at the left and right consoles easily with the change.

[AJaromir]

To understand the problem. The new view is not a bug. It is the update to make view more natural and realistic. But the problem is you still look in the monitor. In reality your field of view is much bigger than you see in the monitor. That's the main problem of TiR and monitor. In real life you look straight ahead but you also see the avionics. But the monitor is just too small window which will not allow you to see that and that is the problem. You have to constantly hold head tilted down which will cause the neck ache and eye ache. I think that is the main difference between VR and TiR with monitor.

 

Edit: I have the biggest problem in the SU-25A where is no artificial horizont and speed and altitude indicator in HUD.

Edited July 14, 2016 by AJaromir

[Snoopy]

To understand the problem. The new view is not a bug. It is the update to make view more natural and realistic.

 

Again, only speaking for the A-10C the new view is in no way realistic.

[jay43]

Definitely changed for VR users, tried the new update when it rolled out end of last week, received Rift beginning of this week and the view is spot on with head steady an looking at hud i can easily glance down with eyes to scan instruments.

TIR users need a way to check this on or off i thinks some like some don't allow the customer to decide.

[dburne]

Track IR behavior is much better with today's update.

Thanks ED!

[SyntaxError]

Agreed it's not slanted down anymore but the decreased sensitivity is still there. Lowering the Saturation X setting on the absolute camera views to 75 seems to bring it back to the normal values. Sadly it's the price to pay to keep the external tracking views, but otherwise I'd still recommend using the old default lua file should you not want to bother altering all the settings for each aircraft.

Edited July 15, 2016 by SyntaxError

[Gliptal]

At this point, the easiest solution would be to keep the old controller in. New users will find the new implementation (now with a correct angle), whilst old users just need a JSGME mod to keep their years old settings and muscle memory.

[SkateZilla]

depends on how long the old controller is retained.

[Gliptal]

depends on how long the old controller is retained.

Exactly. What I'm asking is for ED to keep it around "forever". No need to add an option either.

[SkateZilla]

its likely being replaced for a reason.

[Snoopy]

its likely being replaced for a reason.

 

Not a good one that I can see. Why change what isn't broken?

[firmek]

Nooooo, ED please restore the old new TIR behavior - after the update A10-C is unplayable, the pilot is looking down watching his shoes all the time :D Maybe a bug in helmet code made it too heavy...:D

.

..

...

Being serious though, thx for update! Everyone should be happy right now. For those that want more of an old new TIR and look a bit higher change vAngle value for default view (index13) snapviews.lua in "saved games/config/view" folder. "0" will make the pilot looking straight ahead. Or just configure and save the default position using custom snap views.

 

One observation though, each aircraft has a different angle for looking down, as an example:

A-10c: -23°

F-15: -9,7°

Ka-15: -15,6°

M2000C: -17°

Mig-21: -8.0°

etc...

...but I guess it's fine in old TIR... or maybe just everyone got used to it?

 

I'm coming to the conclusion that there should be one global option for the pilot view in DCS allowing to share FOV, head angle, min/max "zoom" (probably some other). Than if needed this could be customized for every single pit. At the moment it's not consistent at all.

[SkateZilla]

Not a good one that I can see. Why change what isn't broken?

 

 

why,

 

-Because of the vAngle?, That's Been Restored.

-Because it requires about 5 minutes of adjusting curves, which is already a user preference setting?

 

 

If Software doesn't evolve it becomes obsolete,

The TrackIR Controller is what... 9-10 Years Old? Maybe it's Time for it to be updated to allow for Future Expansion etc etc.

 

 

Maybe we should all go back to DirectX 9 because users with 1GB and 512 MB GPUs and Windows XP Cant Run DCS.

 

And Truth Be told, DCS is the ONLY game I have that doesn't use TrackIR 0,0,0/0,0,0 to Set 0,0,0/0,0,0 in Virtual Cockpits.

[Snoopy]

why,

 

 

 

-Because of the vAngle?, That's Been Restored.

 

-Because it requires about 5 minutes of adjusting curves, which is already a user preference setting?

 

 

 

 

 

If Software doesn't evolve it becomes obsolete,

 

The TrackIR Controller is what... 9-10 Years Old? Maybe it's Time for it to be updated to allow for Future Expansion etc etc.

 

 

 

 

 

Maybe we should all go back to DirectX 9 because users with 1GB and 512 MB GPUs and Windows XP Cant Run DCS.

 

 

 

I'm not going to say anything else. We'll just agree to disagree. trackIR worked fine how it was, I see no reason to change anything causing users to have to adjust something that's worked for years.

 

Maybe we should all go back to DirectX 9 because users with 1GB and 512 MB GPUs and Windows XP Cant Run DCS.

 

That's a grown up response, and doesn't even apply. Unless you know something most of users don't TrackIR isn't going anywhere and VR is still in it's infancy.

 

 

 

Sent from my iPhone using Tapatalk

Edited July 15, 2016 by SkateZilla

[Texac]

Never change a running system.

 

But I can deal with it even though I would like to have the old system back.

[SkateZilla]

I'm not going to say anything else . We'll just agree to disagree. trackIR worked fine how it was, I see no reason to change anything causing users to have to adjust something that's worked for years.

 

 

 

That's a grown up response, and doesn't even apply. Unless you know something most of users don't TrackIR isn't going anywhere and VR is still in it's infancy.

 

 

 

Sent from my iPhone using Tapatalk

 

 

But.. It's a valid counter argument, Grown Up, Childish, Snarky or not...

 

The Old Controller is About a Decade old, who knows what code its based off, it has nothing to do with "VR",

Other wise they would have just changed it back to the old iCommandView instead of continuing to expand and develop the iHeadTracker controller.

 

It has nothing to do with TrackIR Going anywhere, and likely more to do with how and when commands are read and sent through the UI to DCS, There's significant changes under the hood w/ Inputs.... and likely more on the way.

 

I can see how its a headache for some, but its still being tweaked and adjusted.

Edited July 15, 2016 by SkateZilla

[escaner]

Nice, it has been fixed in tonight's update. :)

[SharpeXB]

Looks like TrackIR is restored to it's good pre-1.5.4 setting for the A-10

THANK YOU! :thumbup:

[SkateZilla]

TrackIR behavior and orientation has been restored in the new controller,

The only issue now is unsupported head tracking devices and some tweakin'

[Gliptal]

And Truth Be told, DCS is the ONLY game I have that doesn't use TrackIR 0,0,0/0,0,0 to Set 0,0,0/0,0,0 in Virtual Cockpits.

The reason behind this has been presented numerous times, with hard facts and by people that have worked on the real deal for years.

[SkateZilla]

The reason behind this has been presented numerous times, with hard facts and by people that have worked on the real deal for years.

 

Ive sat in many cockpits myself...

 

looking forward did not equal looking down at the Front panel.

(looking at 0,0,0/0,0,0 IRL does not equal looking at 0,0,0/-27,0,0 IRL.)

 

The tracking was correct, as it was true to head position at 0,0,0/0,0,0.

 

The issue is translation of the user to a small FoV screen space, made it a bit tedious,

 

Especially when users were used to using TIR as a head mounted mouse device and not a head tracking device.

 

And used to looking forward to to have the -27 vAngle.

 

If that makes sense.

Edited July 15, 2016 by SkateZilla

[decipher]

i used the rollback fix until todays latest update and gave the "new" trackIR handling a quick testrun now.

i just had to re-assign the trackir YAW and PITCH axis (for every module i have it was blank after update, except mig21/m2000), but i felt "right at home" without changing ANY other axis or sensitivities either in trackIR nor DCSworld options.

 

just sharing this, because i was very skeptical at first, but with the latest fixes and adjustments this issue is settled for me

[wilbur81]

TIR pitch-up/look-up

 

Do any of you guys have suggestions for how to fix my TIR5 in the pitch department with the new setup? I've played with yaw, roll, etc...and everything is fine. But no matter what I do with the pitch curves in the TIR software, when I'm in the F-15C cockpit and I lean my head back to look straight up at the top of the seat...the camera in-game does weird things (ie - flipping the image around so it's no longer clear which way is up, going "head tracking disabled" on me, etc.). Before the headtracking update with 1.5.4, if an aircraft flew at me head on and straight over head, all I had to do was slightly move my head up and the virtual pilot would keep a steady view within the max-limit that the seat would allow, without image flipping, loss of tracking, etc. Again, I've played with the curves to the point where barely looking up the view in the TIR software has the virtual head looking back and upside down at something like 200 deg. Any suggestions?

 

Thanks in advance!

 

PS - my pitch down settings for looking down at the instruments works just fine.

[SkateZilla]

Do any of you guys have suggestions for how to fix my TIR5 in the pitch department with the new setup? I've played with yaw, roll, etc...and everything is fine. But no matter what I do with the pitch curves in the TIR software, when I'm in the F-15C cockpit and I lean my head back to look straight up at the top of the seat...the camera in-game does weird things (ie - flipping the image around so it's no longer clear which way is up, going "head tracking disabled" on me, etc.). Before the headtracking update with 1.5.4, if an aircraft flew at me head on and straight over head, all I had to do was slightly move my head up and the virtual pilot would keep a steady view within the max-limit that the seat would allow, without image flipping, loss of tracking, etc. Again, I've played with the curves to the point where barely looking up the view in the TIR software has the virtual head looking back and upside down at something like 200 deg. Any suggestions?

 

Thanks in advance!

 

PS - my pitch down settings for looking down at the instruments works just fine.

 

I think this is a TrackIR issue, check the TrackIR display, Mine does this, Which is why when IM in the A-10s I put camera below screen to get better downward tracking, and in fighters I put camera above monitor for better look up tracking.