TrackIR Settings

Steve do the TR5 simconnect files still need to be renamed? I have checked the folders you instructed and I cant find them with Win search. I did find the Simconnect.manifestopus and Simconnectsp2.manifestopus1 files. Does Opusfsi change the files on its on now? Thanks.

Am setting up my new system.

You should NEVER run an AV program with FSX, P3D, TrackIR, or OpusFSX.

If you want to flight sim then shutdown your AV software completely.

You only need Windows Firewall. AVs are nothing but trouble and ruin performance and correct functioning of the software.

Stephen

I have tried both TrackIR versions 5.1.3.Final and 5.2.2.Final with no problems. Although I did have to rename the three manifest files again in the NP TrackIR5 install folder.

Please double check you have done the above then check again for OpusFSX listed in the 'Tiles' title. Once connected (with FSX, TIR and FSXSERVER running) it is down to the NP TIR5 software to show OpusFSX as the Title within its window.

You could try reinstalling TIR version 5.2.2.Final version, don't forget to rename those manifest files again.

Stephen

Try starting TrackIR after starting the FSXSERVER program just to see if that makes a difference.

I am back now so I will check to see what I get. But looks like yours is not connecting or attempting to connect to OpusFSX interface through its own NP SDK.

Stephen

Double check that there are no manifest files hiding somewhere that will need renaming. Open the FSXTRACKIR program window and make sure TrankIR is connecting to it. It should be reported in the window. Nothing much else to do other than what's in the manual and the TrackIR topic here. Are your TIR lights coming on? Have you checked OpusFSX exists in the TrackIR games list, have you checked to make sure OpusFSX is shown in the TrackIR display.

Stephen

Stephen,

      Thank you for clarifying this. Sure would be awesome if that feature could be added. I have a 9 monitor setup with virtual cockpit views and it is very immersive seeing the cockpit interior as part of the simulation. If only I could move my head with TIR to look over the glare shield or look down out of a side window it would really complete the experience. Any thoughts about including this down the road or is the FSX / P3D code prohibitive? It would seem to me to be a natural extension of DHM effects on the clients which show motion of the airframe relative to the observer (ie: eyepoint).

Peter.

Stephen,

   I use Virtual Cockpit views on all my clients for a panoramic setup. I have Track IR working through OPUS on my P3D server machine (renamed the manifest files etc.). Unfortunately, I cannot get my head movements to show up in the Virtual Cockpit Views on my clients even though TIR works fine on the server.

    I'm not sure if it has anything to do with it but I do have DHM enabled on the Camera Control page for the P3DServer Camera which is assigned to all aircraft types. I enabled Live Camera on the Server which of course greys out the General DHM Options on the OPUS FSI Server-Configuration page. Is this the correct approach?

     I've read the forum and the manual but can't seem to figure out what I'm doing wrong that prevents my TIR movements from passing through to my clients? Any advice would be appreciated.

     Thanks,

Peter.

You can use Live Camera to create your VC views. Normally you create them for each aircraft you fly. You can easily select a view then click on Add New Camera to clone the view, then just edit the view to suit your new aircraft. There are also CDF (Camera Definition Files) on our website, provided by users, these camera definitions can be Imported into Live Camera. Whichever method you use its a fairly simple process to create your views.

Stephen

Thanks for explaining, it makes sense now.

I like the idea of having to simulate adjusting your seat. Another step closer to the close as it gets for flight sim. 

Thanks,

Gabe 

Opus Software wrote: Hi Gabe You can use Live Camera Control to make temporary adjustments to the viewpoint, it is compatible with TrackIR and our DHM. As you mentioned, Live Camera will save the changes permanently. Cheryl

Hi Cheryl, I set my viewpoint with Live Camera and viewpoint was ok. After shutting down FSX and later when I got back in the sim, I had to reset my viewpoint. Live Camera didn't save changes permanently.

Thanks Cheryl, I give it a try.

Hi Gabe

You can use Live Camera Control to make temporary adjustments to the viewpoint, it is compatible with TrackIR and our DHM.

Cheryl

I will soon be adding 'Run as High Priority' options for the Opus FSXTRACKIR.EXE and the NP TrackIR programs. Users have reported that setting, normally the NP TrackIR program, to run in High Priority has cured there otherwise jerky TIR response.

I put two polarized lenses from sun glasses on mine

I can keep the curtains open most of the day now as my lounge faces south and its only an issue in the evening when the sun is lower in the sky :)

My TrackIR camera does face the window as well and i have the pro clip and it all works sweet :)

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.

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

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.

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

Thanks for the response, Stephen.

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. :)