TrackIR 5.5.2 and OPUSFSX recent betas (3.2.5+)

[jabloomf1230]

I just spent a couple days trying to get OPUSFSX to directly control the TrackIR device. The OPUSFSX developers were convinced (as am I) that there is something odd about my setup that is causing the problem. But the problem did not appear until the last few releases of OPUSFSX over the past few weeks.

My setup is Windows 8 x64, the most recent nVidia video driver, A fairly new high end PC with FSX (SP2 with Acceleration) and P3D (1.4) installed. The problem occurs with either sim and any aircraft. I have the most recent version of FSUIPC4 installed, but disabling it makes no difference.

If I do not use OPUSFSX and just access TrackIR directly from the sim, the TrackIR device works flawlessly (and always has). If I rename the two manifest files in the TrackIR folder (as directed by OPUSFSX's instructions) and control TrackIR that way, OPUSFSX generates an error message:

"Cannot initialize TrackIR library."

Because I was trying any permutation to work around the issue, I renamed the manifest files back to their original names and then also ran both OPUSFSX and the TrackIR app. Doing this causes OPUSFSX to connect in some fashion (I don't get the error message at least) but the viewpoint is jerky, leading me to believe that somehow both the TrackIR app and OPUSFSX were simultaneously controlling the viewpoint in the sim.

The NPClient.dll library is in the

C:\Program Files (x86)\NaturalPoint\TrackIR5

folder (I've tried both the C: and D: drives to clean install the TrackIR software package), UAC is totally off via the Win 8 registry hack, everything is run in administrator mode and finally I've checked all the folder permissions and ownerships. Windows compatibility settings also do nothing. There is an OPUSFSX profile in the TrackIR app list. However the exe that actually communicates with the TrackIR hardware is a child app spawned by OPUSFSX called FSXTRACKIR.EXE.

Remaining thoughts:

I have seen this kind of problem before with Windows 8, where and app tries to load a dll and can't "find it". Usually uninstalling and reinstalling the apps fixes it. I must admit that I haven't seen this problem with any other app under Win 8 for a long time, though. The only other thing that I can think of is maybe FSXTRACKIR.EXE needs it's own profile in Windows 8 for some reason.

Thanks in advance for any insight into this matter.

[jabloomf1230]

NM and you can delete the duplicate thread as I have no idea how that happened. My solution was to start TrackIR, then OPUSFSX from the Windows desktop and not by using exe.dll or the FSUIPC RunIf command. That made everything work for some odd reason.

I also ran across an older thread here regarding the OPUSFSX's developers recommendation that the TrackIR SimConnect manifest files be renamed. I agree with you guys that doing so is a rather odd way of making something work, but I guess if you don't do that both the TrackIR app and OPUSFSX try to simultaneously control the sim's viewpoint, resulting in jiggling of the viewpoint.

[Seth Steiling]

Glad to hear your troubles are resolved. The OpusFSX integration is definitely outside the norm (out of necessity), so it's not super unusual for sticky things to pop up now and again. Always nice when they can be resolved relatively painlessly.

Happy flying.

- Seth