[CLOSED] Slanted side view when using TiR in latest 1.5.4. OB.

[SkateZilla]

That's because when TIR is Paused, it returns you to NUMPAD/KB/MOUSE Input.

 

As Soon as You unpause view will jump to current tracked position from TIR Input.

 

Whether or not this is going to be adjusted, I cannot say.

 

I would Use Snap Views for the Panels in those area's, So Much easier.

[Lange_666]

But Snap Views don't "stick". I don't use them because i always feel i lack an extra hand to operate them or i might overlook something... (and i don't have room on my HOTAS to implement them there).

[SkateZilla]

I have asked about track pausing returning to default forward view instead of pausing in current position.

[cichlidfan]

I have asked about track pausing returning to default forward view instead of pausing in current position.

 

Good. Because the whole point of pausing TIR is to lock the view right where it is at that moment.

[firmek]

I have asked about track pausing returning to default forward view instead of pausing in current position.

Thanks!. Since I've got the TIR I didn't see no more need to use the snap views. The pause is really sufficient and convenient. Please check also why TIR in M2000C and Mig-21 works differently.

[SkateZilla]

Good. Because the whole point of pausing TIR is to lock the view right where it is at that moment.

 

 

 

The Hole Point of using TiR is to use your head to control your head so u dont have to use your hands and KB Buttons.

[Gliptal]

^The Hole Point of using TiR is to use your head to control your head so u dont have to use your hands and KB Buttons.

He probably meant "TIR pause function".

[Rhinozherous]

TIR seems completly messed up... please dont release that into the stable version

[cichlidfan]

Good. Because the whole point of pausing TIR is to lock the view right where it is at that moment.

 

The Hole Point of using TiR is to use your head to control your head so u dont have to use your hands and KB Buttons.

 

He probably meant "TIR pause function".

 

I did. That would be the reason that I used the phrase 'pausing TIR'.

 

:doh:

 

Btw, Skates, in this context, the word 'whole' has a 'w' in it. Rather changes the meaning quite a bit.

[SkateZilla]

I did. That would be the reason that I used the phrase 'pausing TIR'.

 

:doh:

 

Btw, Skates, in this context, the word 'whole' has a 'w' in it. Rather changes the meaning quite a bit.

 

I blame Teamviewer, I type so fast some keystrokes dont register, lol

[archer86]

Changing openbeta trackir default.lua with stable version fixed my issue again:)

[grunf]

TIR worked fine for years and I really see no reason to change the way it used to work. Snapviews are no substitute for pause TIR, so please bring it back.

 

Also, I can't seem to look more than 90 deg to the side, unless I turn my head all the way back. But then I'm looking at the wall, not my monitor, so no point of doing it. Not to mention a sore neck.

 

ED, I realy appreciate your work, but the TIR changes are going in a wrong direction. :(

[jjohnson241]

TIR worked fine for years and I really see no reason to change the way it used to work. Snapviews are no substitute for pause TIR, so please bring it back.

 

Also, I can't seem to look more than 90 deg to the side, unless I turn my head all the way back. But then I'm looking at the wall, not my monitor, so no point of doing it. Not to mention a sore neck.

 

ED, I realy appreciate your work, but the TIR changes are going in a wrong direction. :(

 

+1

From the Changelog:

"In-cockpit TrackIR functionality corrected. Influence of mouse and default camera position was switched off."

 

Corrected? I hope the party that made these changes has the benefit of feedback from this forum.

[theropod]

Changing openbeta trackir default.lua with stable version fixed my issue again:)

 

:thumbup:

 

Yes, it works!

[SkateZilla]

+1

From the Changelog:

"In-cockpit TrackIR functionality corrected. Influence of mouse and default camera position was switched off."

 

Corrected? I hope the party that made these changes has the benefit of feedback from this forum.

 

Corrected as In it Fixed the issue that was the Purpose of this thread, with the Mouse and KB Conflicting/Fighting w/ headTracking causing the slanted view.

 

Which was a Bug introduced w/ the Initial 1.5.4 Open Beta Launch,

 

 

Not "Corrected" as in Corrected vs 1.5.3

[jjohnson241]

Corrected as In it Fixed the issue that was the Purpose of this thread, with the Mouse and KB Conflicting/Fighting w/ headTracking causing the slanted view.

 

Thanks for the clarification.

I thought it meant corrected the TIR problem that was created by last weeks OB update and repeated today. I missed your 1.5.3 reference.

[[DBS]TH0R]

Just tested 1.5.4 last night. In P-51 I can't check my six, and A-10C view is odd at best sharing the same problem of not being able to look back over your shoulder.

 

Please fix this.

[Enduro14]

Use the mirrors that's what their for

[Gliptal]

Use the mirrors that's what their for

The mirrors are huge resource hogs.

 

And in most fighters and planes, the pilot has more than enough freedom to look behind him.

[Fakum]

I don't know what else to say, TrackIR needs to be fixed soon and work the way it always has,, this fiddling around with files is annoying,,,, yes its Beta, I get it! But eluding to this may be the norm in the end does not sit well. We just need it back to where it worked right,,, my 2 cents, and no offence intended to anyone.

[HiJack]

Just tested 1.5.4 last night. In P-51 I can't check my six, and A-10C view is odd at best sharing the same problem of not being able to look back over your shoulder.

 

Please fix this.

Replace this file with the same file from 1.5.3 or 2.0 and you are all good.

..\Config\Input\Aircrafts\Default\trackir\default.lua

[SyntaxError]

I'm not sure why they trying to fix something that was never broken and worked perfectly between TrackIR, FTNOIR and Opentrack. I can understand if this is testing if these settings are shared with VR, but I have to agree with the previous poster in that if I want VR movements, I'll buy a VR Headset.

[nomdeplume]

I suspect they don't want to have maintain two completely separate view control methods for the rest of time. That will add constant overhead to the development process, both for ED and third party developers who have to test and support both methods.

 

Plus: not all devs may have a VR headset, and in future some may only have VR headsets but no TrackIR. There's also likely to be more types of headsets and developers won't have all of them. So, creating a single unified view control system that works properly with all devices makes sense in the long term.

 

Some teething issues are to be expected, and if they can't iterate on these types of changes in an open beta then where on earth are they supposed to?

[Hadwell]

 

Some teething issues are to be expected, and if they can't iterate on these types of changes in an open beta then where on earth are they supposed to?

 

well you'd think they'd test trackIR on their own systems and at the very least make sure it works in all modules, not just fc3, before releasing the update, there's no way they don't have trackIR on hand...

 

it'd be one thing if the like... 10 people who play dcs with VR on a regular basis didn't have working head tracking with their VR sets, it's totally another when the majority of people who use head tracking non-VR can't... even if it is a beta update...

Edited July 3, 2016 by Hadwell

[SnowTiger]

I suspect they don't want to have maintain two completely separate view control methods for the rest of time. That will add constant overhead to the development process, both for ED and third party developers who have to test and support both methods.

I completely disagree with this idea.

The fact that developers would have to test and support both methods forever would only apply if they continue to make changes to both methods.

Whereas if they have TIR working .. leave it alone and create a completely independent method of control for VR headsets. These things are not alike.

Each method should have it's own Radio Button ... select the TIR system radio button to use that method if you have TIR OR select the VR radio button to utilize the VR method.

 

Then if/when they make changes to one it doesn't adversely affect everyone like we are currently seeing.

 

I'm not a programmer so I don't know if this is possible, but I'd like to think it would be that simple for someone who is ?? !