SimForums.com Homepage
Forum Home Forum Home > Flight One Partner Forums > Opus Software
  New Posts New Posts RSS Feed - TrackIR Settings
  FAQ FAQ  Forum Search   Register Register  Login Login

TrackIR Settings

 Post Reply Post Reply Page  <1234>
Author
Message
griphos View Drop Down
Intermediate Group
Intermediate Group


Joined: January-30-2009
Location: United States
Points: 49
Post Options Post Options   Thanks (0) Thanks(0)   Quote griphos Quote  Post ReplyReply Direct Link To This Post Posted: November-09-2012 at 8:02am
In item #3, setting the XYZ and the PBY settings to 0.50 and 0.75 just limit how far you can turn your head. They just scale the TIR input, according to what Stephen says above, and so shouldn't affect smoothness. A setting of 0.50 means you won't be able to look past about 90 degrees to the side.

Can't speak to the other suggestions, as I don't really have jerkiness anyway.
Back to Top
J van E View Drop Down
Senior Member
Senior Member


Joined: January-30-2006
Points: 337
Post Options Post Options   Thanks (1) Thanks(1)   Quote J van E Quote  Post ReplyReply Direct Link To This Post Posted: November-09-2012 at 8:22am
Originally posted by griphos griphos wrote:

In item #3, setting the XYZ and the PBY settings to 0.50 and 0.75 just limit how far you can turn your head. They just scale the TIR input, according to what Stephen says above, and so shouldn't affect smoothness. A setting of 0.50 means you won't be able to look past about 90 degrees to the side.

Can't speak to the other suggestions, as I don't really have jerkiness anyway.
Interesting. Not being able to move my head around made me move to another camera program (for the moment being). Maybe I should give Live Cam another try... Wink
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: November-09-2012 at 10:59am
In addition to setting our acan rate and scaling factors, you must also tweak the TIR device settings, including the advanced or Camera Light Sensitivity and IR settings. The Light Sensitivity Level is supposed to be the main cause of stutter (according to email from NP).

Stephen
Back to Top
J van E View Drop Down
Senior Member
Senior Member


Joined: January-30-2006
Points: 337
Post Options Post Options   Thanks (0) Thanks(0)   Quote J van E Quote  Post ReplyReply Direct Link To This Post Posted: November-09-2012 at 11:15am
Ok, I am back in business. I decided to give Live cam another try and to actually TEST various settings to see what they do.

Well, the problem I had with not being able to look behind me was indeed due to PBY Scaling being at 0.75. Don't know if that's the default number but I set it to 1.00 and all is perfectly fine in that regard. Just run the game in windowed mode, look behind you and change that PBY number: you will see your view being limited more and more the lower you make the number. My advice: leave it at 1.00!

Secondly: the huge jumps/movements of the screen were due to the Scan Speed. It's very odd but I had it at 12. I turned it up a lot and looking around got stuttery. So I turned it to 1 and with that setting I got huge jumps/movements! After setting it BACK to 12... the jumps were gone...! Odd... Maybe some setting got stuck somewhere and I had to change the setting in OpusFSX to reset it...?

The only thing that still doesn't work well are the smooth transitions: they aren't smooth. I do not get sudden jumps anymore as I did with a previous beta, but the transition is jerky... I can live with that though (for the moment) because in the Legacy I do not need to change views that often. Don't know if it is because of the latest beta OR simply restarting my PC in the meantime, but transitions are smooth too now!

So... I'm good again now! It pays to actually test various things so you know what you are doing. Wink

BTW I have TrackIR 4 hardware but still use TIR 5 software.

EDIT
After flying with the EZCA wobbles for a few days, OpusFSX DHM looks so much better...! Smile
Back to Top
Chunk View Drop Down
Senior Member
Senior Member


Joined: August-01-2009
Location: United States
Points: 117
Post Options Post Options   Thanks (0) Thanks(0)   Quote Chunk Quote  Post ReplyReply Direct Link To This Post Posted: November-09-2012 at 4:10pm
Thanks for the heads-up on the PBY settings Griphos.  I wasn't sure why I couldn't turn my head around further.

The question I have is my zoom level in cockpit.  When I started the sim without DHM, I was at a .80 zoom level, with DHM enabled, I get into the cockpit, and my zoom is set to .50.  Any ideas why this is happening?  I like the zoom at .80, and I want it to stay there.

Thanks BTW, this is a great overall product!
Back to Top
Villan View Drop Down
New Member
New Member


Joined: February-05-2012
Location: Australia
Points: 16
Post Options Post Options   Thanks (0) Thanks(0)   Quote Villan Quote  Post ReplyReply Direct Link To This Post Posted: November-10-2012 at 1:51am
G'day
 
Hi i just been trying out your program the demo one and i happen to be getting some problems myself. TIR 5 can't be used with OpusFSX open on the main panel as the VC is all over the place. If the sim is in paused state it will still jump and i can only stop it if i pause my TIR 5. Also i can get it to stop when i have the camera tab open but i cant see the shaking in side the VC and as soon as i close the camera tab its back.
 
Every time i try and change scan speed it will go back to 12. This happens only if im going down in numbers not up so at 20 that will be saved.
 
I would like to get the demo to run right before outlaying the $$$
 
Thanks Darryl
Back to Top
J van E View Drop Down
Senior Member
Senior Member


Joined: January-30-2006
Points: 337
Post Options Post Options   Thanks (0) Thanks(0)   Quote J van E Quote  Post ReplyReply Direct Link To This Post Posted: November-10-2012 at 4:28am
Originally posted by Villan Villan wrote:

G'day
 
Hi i just been trying out your program the demo one and i happen to be getting some problems myself. TIR 5 can't be used with OpusFSX open on the main panel as the VC is all over the place. If the sim is in paused state it will still jump and i can only stop it if i pause my TIR 5. Also i can get it to stop when i have the camera tab open but i cant see the shaking in side the VC and as soon as i close the camera tab its back.
 
Every time i try and change scan speed it will go back to 12. This happens only if im going down in numbers not up so at 20 that will be saved.
 
I would like to get the demo to run right before outlaying the $$$
 
Thanks Darryl


Sounds like you need a higher scan speed... BTW You can't see the shaking when the camera tab is opened because that automatically pauses the game and stops ALL effects. Closing the tab unpauses everything.
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: November-10-2012 at 4:28am
G'day Darryl
 
You need to set up TrackIR as per the Getting Started for Single PCs pdf. You must update your game list, rename the manifest files etc. Probably in your demo version the minimum scan speed is 12. I would recommend setting it at 25 to start with. Also set the TrackIR Speed to 1 and the Smoothness to 50 in the TrackIR program.
 

Ensure you have no other software packages running that are trying to control the camera or create camera shake effect.

Regards

Cheryl
Back to Top
Villan View Drop Down
New Member
New Member


Joined: February-05-2012
Location: Australia
Points: 16
Post Options Post Options   Thanks (0) Thanks(0)   Quote Villan Quote  Post ReplyReply Direct Link To This Post Posted: November-10-2012 at 7:28am
Originally posted by Chunk Chunk wrote:

I get into the cockpit, and my zoom is set to .50.  Any ideas why this is happening?  I like the zoom at .80, and I want it to stay there.
 
Give this a go run OpusFSX and go to cameras and look for Z-Axis just click up or down and stop to stop it. set your zoom you want from there and then Save all cameras. then shut down that tab. You may find that your camera will always say .50 but you have it at .80
 
PS. you can also use the other ones to move yourself around in the seat to be seated were you would like to be. left,right,up or down.
 
Hope that helps
 
BTW i had read about every post from avsim about your program and i think i did read if you had the older OpusFSX you got a discount for the newer one. I would like to know if i got 2.30 think thats the one out now what kind of updates would i get. As you was making lots of changes almost every day. Its still beta as well ?
 
Thanks Darryl
 
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: November-10-2012 at 7:37am
You could also just create your VC cameras with a zoom setting of 0.8, set the captains view as tye default view and assign buttons to all of them. Then you have achieved everything you want.

Stephen
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: November-10-2012 at 8:46am
Everyone gets free upgrades. You can try the betas, they are pretty stable, just download the zip and extract to your OpusFSX installation folder.

Regards
Cheryl
Back to Top
WilliamJSS View Drop Down
New Member
New Member


Joined: October-24-2012
Points: 12
Post Options Post Options   Thanks (0) Thanks(0)   Quote WilliamJSS Quote  Post ReplyReply Direct Link To This Post Posted: November-10-2012 at 4:17pm
Is there a cockpit walls like function for Opus? So as your head movement using TrackIR stays inside the cockpit?
Back to Top
griphos View Drop Down
Intermediate Group
Intermediate Group


Joined: January-30-2009
Location: United States
Points: 49
Post Options Post Options   Thanks (0) Thanks(0)   Quote griphos Quote  Post ReplyReply Direct Link To This Post Posted: November-10-2012 at 10:00pm
You'll find some discussion of this on p. 2 of this thread.

Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: November-11-2012 at 7:08am
We will be introducing cockpit limits in the future.
Back to Top
WilliamJSS View Drop Down
New Member
New Member


Joined: October-24-2012
Points: 12
Post Options Post Options   Thanks (0) Thanks(0)   Quote WilliamJSS Quote  Post ReplyReply Direct Link To This Post Posted: November-11-2012 at 11:48am
Thanks!
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: November-12-2012 at 5:25am
Possible cause of the jitters ...
 
You do not necessarilly have to be next to an open window to cause the jitters, any nearby IR source or IR reflector will produce them. Make sure your Light Filter Threshold isn't set too high, try setting the default 100, and adjusting from there, with a max setting of 15 for your IR Brightness. Also make sure you have Video Processing Mode set to Precision with a Precision Mode Smoothing of 100.
 
You can adjust TIR to suit from there. These recommendations come from Natural Point, light polution and an incorrect Light Filter Threshold setting are the number one main causes of flicker.
 
Everyone needs to get into the habit of checking their TIR manifest files after any TIR update, the TIR software can create new files after the upgrade.
 
Regards
Stephen Smile
Back to Top
Chunk View Drop Down
Senior Member
Senior Member


Joined: August-01-2009
Location: United States
Points: 117
Post Options Post Options   Thanks (0) Thanks(0)   Quote Chunk Quote  Post ReplyReply Direct Link To This Post Posted: November-25-2012 at 11:37pm
I got my issues all squared away with the DHM settings, and this program is proving to be a real winner.  Thanks Griphos, Villan, and Stephen!
Back to Top
Den View Drop Down
New Member
New Member


Joined: January-04-2013
Location: United States
Points: 3
Post Options Post Options   Thanks (0) Thanks(0)   Quote Den Quote  Post ReplyReply Direct Link To This Post Posted: January-04-2013 at 9:23am
I'm new to the forum and the following may have already been addressed.

In trying to adjust the smoothness of TrackIR5.2 in conjunction with the OpusFSX Camera speed indicator I've noticed that OpusFSX will not retain the readjusted slider setting after saving all camera views.

I must be missing something?

Lest I forget, OpusFSX is outstanding!  
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: January-04-2013 at 9:25am
What slider ... the vertical slider in the Camera dialog is nothing to do with TIR, it just alters the speed of movement for ajusting the eye position.
 
Stephen
Back to Top
Den View Drop Down
New Member
New Member


Joined: January-04-2013
Location: United States
Points: 3
Post Options Post Options   Thanks (0) Thanks(0)   Quote Den Quote  Post ReplyReply Direct Link To This Post Posted: January-04-2013 at 9:29am
Wow!  Thanks for the quick response...

Yes I understand that adjustment.  But in my case, I'm trying to find the happy medium between what my screen is doing versus the speed of TrackIR in a effort to remove the jitters.

Immediate adjustment to the slider seem to help me balance the rate of change in the view.  But, when I return to the Camera settings in OpusFSX the slider has returned to it's "original" setting.
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: January-04-2013 at 10:11am
The slider is not something you configure at all.

Try adjusting your TIR settings etc. including your light sensitivity etc. also check your TIR settings in our Configure dialog.

Please check the first post in this topic.

Stephen
Back to Top
RCFlyer51 View Drop Down
Senior Member
Senior Member


Joined: August-09-2009
Location: United States
Points: 145
Post Options Post Options   Thanks (0) Thanks(0)   Quote RCFlyer51 Quote  Post ReplyReply Direct Link To This Post Posted: January-05-2013 at 11:33am
Originally posted by Den Den wrote:

Wow!  Thanks for the quick response...

Yes I understand that adjustment.  But in my case, I'm trying to find the happy medium between what my screen is doing versus the speed of TrackIR in a effort to remove the jitters.

Immediate adjustment to the slider seem to help me balance the rate of change in the view.  But, when I return to the Camera settings in OpusFSX the slider has returned to it's "original" setting.
 
Den:  Danny here.  I found that reducing the Light Filter Threshold to around 70 has eliminated the flickering issue.  I still have complete response from TrackIr.  My TrackIr camera settings are:
 
Light Filter Threshold: 71
IR Brightness: 12
Video Processing: Stnadard
Precision Mode Smoothing: 100
 
See you on HC.
 
Regards,
Back to Top
Den View Drop Down
New Member
New Member


Joined: January-04-2013
Location: United States
Points: 3
Post Options Post Options   Thanks (0) Thanks(0)   Quote Den Quote  Post ReplyReply Direct Link To This Post Posted: January-07-2013 at 11:03am
Thanks Danny!
I can confirm that your solution worked for me!
Thanks again!
Den

Back to Top
B777ER View Drop Down
Senior Member
Senior Member


Joined: May-27-2004
Points: 129
Post Options Post Options   Thanks (0) Thanks(0)   Quote B777ER Quote  Post ReplyReply Direct Link To This Post Posted: March-21-2013 at 8:50am
Originally posted by Opus Software Opus Software wrote:

We will be introducing cockpit limits in the future.

Are these limits in there yet? If so I cannot find them.
Eric
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: March-21-2013 at 9:06am
Yes, you should check the Announcements they were included some time ago.

They were introduced in beta 2.94.0 ...

TrackIR head movement limits have been introduced. The limits for specific aircraft types can be set via the TrackIR Limits button in the Configure dialog. The Live Camera option must be enabled (ticked) to assign these limits. You do not need to enable the TIR device to assign the head movement limits.

Stephen
Back to Top
bdf369 View Drop Down
Intermediate Group
Intermediate Group


Joined: September-10-2012
Location: USA
Points: 78
Post Options Post Options   Thanks (0) Thanks(0)   Quote bdf369 Quote  Post ReplyReply Direct Link To This Post Posted: April-01-2013 at 8:31pm
Hi, just a comment about TrackIR settings in the docs. TrackIR can be used with the default TrackClip, or it can be used with TrackClipPro. The latter has its own LED emitters and its setup is very different from TrackClip. With TrackClipPro the Camera IR brightness should be zero and Light Filter Threshold should be set to a high value. The easiest way to get the correct settings is to click the TrackClipPro button in the TrackIR window and it will reset the Camera settings automatically.

If you use TrackClipPro and set up TrackIR as described in the docs, with Camera LED brightness set to 12 and filter threshold down to 75, you will get very bad jerky view behavior. It's especially bad for me because I wear eyeglasses which can reflect back the camera LEDs and fight with the TrackClipPro inputs. I'm suggesting you differentiate between the 2 devices in the docs.

I understand you have TrackIR limits in the latest betas, is this to prevent things like moving your head through the side of the airplane? Sounds like a great idea: I will upgrade to try that out.

Thanks for this great product.

Regards,
Barry
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: April-02-2013 at 10:22am
Thanks Barry, I will add that info to the docs.
 
Cheryl
Back to Top
BigJacko View Drop Down
New Member
New Member


Joined: February-03-2013
Points: 34
Post Options Post Options   Thanks (0) Thanks(0)   Quote BigJacko Quote  Post ReplyReply Direct Link To This Post Posted: April-04-2013 at 11:05am
It may also be worthwhile noting that if you have a TrackClipPro, AND you mess with the Infrared LED settings slider, you will NOT be able to return it to zero after you've altered it. However, if you're using the TrackClipPro, it's essential that the IR LEDs are off (for the reason Barry gave, and more).
To accomplish this, toggle the TIR mode back to TrackClip, and then back to TrackClipPro, using the buttons in the TIR software. This should reset the IR LEDs back to OFF. Then leave that item alone! ;)
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: April-04-2013 at 11:23am
Ok, many thanks for the additional info.

Cheryl
Back to Top
BigJacko View Drop Down
New Member
New Member


Joined: February-03-2013
Points: 34
Post Options Post Options   Thanks (1) Thanks(1)   Quote BigJacko Quote  Post ReplyReply Direct Link To This Post Posted: April-04-2013 at 1:24pm
Can I beg clarification on a couple of items gleaned from re-reading this thread a couple of times today, please?

Firstly - PBY scaling; I've found an answer to what it means here, but I don't believe I found it spelled out in any of the various manuals/guides included with the product. It might be worth ensuring that PBY - Pitch, Bank & Yaw - is made more obvious in the docs, perhaps? And with a note to the effect that if you can't turn your head fully round, it'll most likely by the PBY scaling factor that's the cause (which might stop folks returning to EZCA, etc).

Second - some of Stephen's posts mention reducing IR LED emission levels down to 15 or less - this is ONLY pertinent if you are using the reflective TrackClip (wire frame widget on the baseball cap), and conversely if you are using the TrackClipPro, it's an absolute no-no (you want IR levels to be OFF, as per my tip above), or you may suffer random IR reflections that confuse the camera.

Finally, I'm trying to determine what the scan-rate setting in Opus actually equates to. It's measured in milliseconds, from what I can tell, but if so, logically this means that a 30ms scan-rate is SLOWER than a 2ms scan rate, surely? By that I mean, if the INTERVAL between scans is 30ms, this is fifteen times less frequent in grabbing TIR data than a 2ms setting, presumably? Reason I bring this up is because various peeps (myself included) have talked about 'upping' the scan-rate, or 'increasing' it - when in fact, if we enlarge the number in that box, surely we're actually slowing it down, or increasing the interval, rather than the speed. It might be useful to have some confirmation on that point because it may prevent confusion in the future (if someone suggests 'speed it up' but actually means - without realising it - quite the opposite, well, you can see how that might end up complicating matters, rather than helping them!)

One last, last item - is it worth enabling some kind of 'input-output TIR data log', in Opus, so that we can keep track of what Opus is doing with TIR's data, and whether TIR itself, or Opus's handling of it, is the problem? I appreciate this might generate some pretty huge files (if scanning at 1ms, for example!) but perhaps might be worthwhile. From what I can tell, *usually* the cause of these 'one-frame resets' or occasional flickering, is the light threshold in TIR being momentarily confused, but I couldn't put my hand on my heart and say it's *always*, *exclusively* that reason alone. There are times when I'm scratching my head, and gritting my teeth, and maybe can't find anything obvious on TIR's panel to account for it - then next day, it'll be fine, without me having changed a thing, knowingly, at least.

Another, final, final, final ;) suggestion: perhaps is it worth introducing some 'TIR smoothing' in Opus itself? Simplistically, don't allow a reversion to zero XYZ/PBY coordinate on a single (or short number of frames), if the previous frame was greater than a certain deflection? I appreciate I'm saying this whilst blind of all the inner workings of what Opus is actually doing, but you probably get what I'm meaning. Not really 'smoothing' - more of a high-deflection-to-zero-deflection over a short time-frame 'filter'. Obviously, if the problem is SimConnect dropping the ball when it's busy, this won't help, but I mention it just in case it's worthy of investigation.

Thanks either way. :)
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: April-04-2013 at 1:37pm
With the scan rate, which is approximately in milliseconds, you must consider the response of your FSX system's SimConnect interface and the NP SDK interface. Going faster does not necessarily mean going smoother. You may end up going too fast for the interfaces and so miss many of the updates, possibly resulting in a more jerky display.

The best thing to do is balance everything so that it can run optimally and hence smoothly. All systems are different hence we allowed users to adjust the scan rate.

Stephen

P.S.

Data logging would generate huge amounts of data, literally gigabytes. Also data smoothing is best done at source since it has to take into account other factors and settings. The actual data can be reported via the NP SDK at a very fast rate so the smoothing has to be undertaken by the actual TIR software. That's really were it belongs, all the interface does is relay this data on to the FSX display after superimposing it with the Opus eye point data.
Back to Top
BigJacko View Drop Down
New Member
New Member


Joined: February-03-2013
Points: 34
Post Options Post Options   Thanks (0) Thanks(0)   Quote BigJacko Quote  Post ReplyReply Direct Link To This Post Posted: April-05-2013 at 5:52am

Thanks for the response, Stephen.

 
I take it from that, that I was correct in my thinking that INCREASING the number in the scan rate box actually SLOWS DOWN the rate at which data is fetched from the NP interface, yes? (Apologies to labour the point, but I need to get this straight in my head, and I'm sure others do too).
 
As regards logging - all totally understood and concurred with. I had expected as much. I wonder if perhaps an alternative strategy for debugging might be better? How about a facility in Opus which examines the 'feed' of data coming from the NP interface and flags up (in a log, most likely) any instances where the deflection exceeds a physically possible amount in a single frame or small number of frames. At least then we might be able to determine if the cause of the 'glitch' flicker really does stem from TIR's end (which is my hunch), and positively rule out Opus's 're-server' as the cause. In essence, fit Opus with a 'garbage-in' detector, and have it flag it when that occurs!
 
As I said, it's my belief that the flicker stems from extraneous light in TIR - but this is extremely difficult to pinpoint empirically, because by the time one has left the sim and pulled up the TIR panel, switched to camera view and hunted for red-traces, the sunbeam which caused the problem has gone behind a cloud and is no longer reflecting off the door behind/beside you, etc, etc. There is no 'sanity input' logging in TIR's program, so Opus is effectively the only 'tap' on that data.
 
Of course, if the problem is ALSO caused by an overload of the Simconnect interface (entirely possible, given what I know about Simconnect), then it'll be much harder to trace - because presumably Simconnect doesn't have the capability to politely inform Opus's outgoing 'pump' that Simconnect is unable to process it, and instead, Simconnect will presumably quietly drop data without warning. If that's the case, only some kind of Simconnect logging within FSX itself will shed any light, but I've not looked into that yet (but it might be worth it, if I have time).
 
At least if Opus was able to flag up 'dodgy data' coming from NP/TIR in the first instance, that *might* eliminate (or pinpoint) one of our lines of enquiry, perhaps? I am confident it's not Opus that's the problem (I'm sure I've seen these random one-frame flickers even before Opus, tbh, but perhaps less often - but then I didn't have anything pumping weather info in via Simconnect, so it could still be Simconnect's fault, rather than Opus's). But Opus could, in theory, prove its own innocence, and conclusively point the finger at NP/TIR, if the faulty data came from there.
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: April-05-2013 at 6:28am
We already have test outputs displayed, that's why I know smoothing is a waste of time. You must weigh up both the speed of scanning the TIR interface via the NP SDK with the update frequency to the SimConnect interface. Go too fast for FSX and it can throw away updates, to slow and you get slightly uneven panning.

NP themselves say most flickering comes from extraneous light hence they recommend everyone should adjust the TIR light sensitivity to suit their environment.

If your DHM and AHM can move smoothly without TIR then the SimConnect interface should be OK with a correct setting of the Opus TIR scan rate. I use 12ms or 18ms. Increasing the ms rate decreases the frequency at which the TIR interface is scanned.

The Opus TIR interface simply takes the raw data from the TIR device via the NP SDK interface, scales it, combines it with the current Opus eye point data, applies any limits and submits it to FSX via SimConnect. It is a very simple process and so far all jitteriness has really been as a result of needing to adjust the Opus scan rate and change the TIR settings, with the vast majority of jitters caused by extraneous light.

Stephen
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: April-05-2013 at 6:32am
To display our test outputs, just run the FSXTRACKIR.EXE program with a TEST argument. But the displayed test outputs depend on what I was checking the previous time, they are not meant to be for user information. The data may even be rounded for display purposes.

Stephen
Back to Top
BigJacko View Drop Down
New Member
New Member


Joined: February-03-2013
Points: 34
Post Options Post Options   Thanks (0) Thanks(0)   Quote BigJacko Quote  Post ReplyReply Direct Link To This Post Posted: April-05-2013 at 11:57am
Thanks for this Stephen - I'll try some test runs in Debug mode and see whether it sheds any light (no pun intended). For the most part, I'm not affected by this flickering too much, but I am aware that it is a big pain for some users, and I'd love to find a reliable way to nail it.
I think part of the problem is that the same symptom (a single or few-frame 'flicker' back to a default eye-point and deflection; a reset view, in other words) is the same outcome for both of these causes (Simconnect overload and TIR light-pollution). This makes it very difficult for, shall we say, the normal everyday user, to work out what's actually the cause. They'll try messing with the Opus scan-rate in the hope of a fix, but if their problem is light-pollution, they may well simply add to their problems by introducing Simconnect overloading into their already difficult mix! They won't know, because the results both look the same! Conversely, if they go hunting for light-pollution and the problem is Simconnect timing out, they're wasting their time - and even if they think to alter the Opus scan rate 'for balance', they may not know whether to increase the displayed number, or decrease it. End result = frustration, and probably wrongful putting of the blame on Opus - a situation I am keen to avoid, because like you, I don't think it is the problem!
 
This is why I'm wondering whether, if Opus can detect spurious light-polluted garbage coming from the TIR end, and if this could be flagged up to the user (in debug mode or otherwise), at least this would help the average non-technical user know where to start looking. Conversely, if Opus hadn't reported any 'garbage-input' and the user was still seeing glitches, it would point to Simconnect overflow as the most likely cause, and he could begin looking there, and slowing down the scan-rate, maybe.

As I said, I appreciate this isn't your problem - but I don't like reading that other folks have dropped Opus in preference to inferior products, simply because they've not been able to make headway in solving it - and when they end up on these products (which probably put less stress on the Simconnect layer because they don't do anything like as much magic, and/or mean that the light-pollution situation has changed by the time they've reconfigured), they'll believe (wrongly) that they were right to have dropped Opus. All they see is that the problem has 'gone away', not understanding quite why. Human nature says that will simply reinforce their belief that Opus was at fault in the first place, even though that's inductive, not deductive logic!
 
All I'm thinking is that if Opus was able to detect 'nonsense' from TIR/NP and flag it up, it's in your interest to point the user to that end of this double-ended nightmare to start twiddling with! Get me?
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: April-05-2013 at 12:08pm

They should just use the default settings and check there DHM and AHM movement, that will check their SimConnect, and users should have an idea how taxed their FSX systems are.

 
If you set the Opus scan rate too high you will eventually get a stuttery display, if you set it too low then the display will jump as updates are missed. All other jitters are usually down to TIR and the quality of the light signal.
 
We have tried filtering out data but that process must really be performed by the TIR driver and not after the fact in our interface which is really just relaying the data to the sim. Please do not read too much into the test data, the values may be rounded and are not intended as a user's analysis tool.
 
Stephen
Back to Top
rabid View Drop Down
Intermediate Group
Intermediate Group


Joined: September-07-2006
Location: United Kingdom
Points: 47
Post Options Post Options   Thanks (0) Thanks(0)   Quote rabid Quote  Post ReplyReply Direct Link To This Post Posted: April-08-2013 at 9:13am
Hi Stephen, 

I use Opus every flight and love the camera system, but I have had to untick DHM due to strange goings on with TrackIR. 

Without DHM TIR is smooth and tracks perfectly without stutters. Tick the DHM box and every now and then the screen/cockpit will judder violently, just for half a second. 

It ended up getting annoying hence why I turned it off. I've tried different scan rates but that did not eliminate the problem. In the meantime I've reactivated Accufeel turbulence but if you have any ideas regarding DHM please shout, it may be just one particular setting.

Many thanks,
David.
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13870
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: April-08-2013 at 9:52am
Try just turning off the turbulent bumps and leave the inflight turbulent motions on, and set all sliders to default mid way. I just couldn't fly without DHM, just not the same.

Stephen
Back to Top
rabid View Drop Down
Intermediate Group
Intermediate Group


Joined: September-07-2006
Location: United Kingdom
Points: 47
Post Options Post Options   Thanks (0) Thanks(0)   Quote rabid Quote  Post ReplyReply Direct Link To This Post Posted: April-15-2013 at 7:39am
Thanks, I have tried turning off turbulent bumps which seems to have helped a little but still get occasional "jumps" in the VC which can be very distracting. Will test further!
Back to Top
glider1001 View Drop Down
New Member
New Member


Joined: May-22-2013
Location: Australia
Points: 10
Post Options Post Options   Thanks (0) Thanks(0)   Quote glider1001 Quote  Post ReplyReply Direct Link To This Post Posted: May-23-2013 at 7:25pm
Had the same issue when I recently bought OpusFSX. TrackIR was working perfectly on it's own but when switching to DHM there were random jumps. I looked up the Opus manual and slowed the scan speed right down to 40ms. That fixed it but all the smoothness in head rotation was lost.

In the end the suggestion in the OP of this thread fixed it. The problem was not the scan speed but was the light filter threshold surprisingly. With track clip I set the light filter threshold down to 70 and IR brightness to 12 with precision of 100 on standard with the Opus TrackIR scan speed set back to it's default 12ms.

That nailed the problem and is now working sweet. I am actually really surprised that the light filter threshold was the problem all along.

Cheers
Back to Top
 Post Reply Post Reply Page  <1234>
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.01
Copyright ©2001-2018 Web Wiz Ltd.

This page was generated in 0.195 seconds.