sthalik

I'm necroing this also. In windows 10, installing the regfix with the newest driver causes USB devices to stop working. To fix e.g. mouse, go to device manager and delete all USB hubs from usb controller section. Edit: Here's the proper solution: install the driver for older Windows. URL: ftp://ftp.saitek.com/pub/software/beta/Saitek_X65F_Flight_Controller_SD7_0_10_6_BETA_64_bit_Driver.exe Then you can apply the regfix. Don't use the dedicated Windows 10 driver as applying the regfix causes (at least on my Intel controller) USB controllers/hubs failing to start, or silently not working.

Don't exceed 90 degrees pitch and 180 for other rotations then it won't jump around for 1 frame. Other issues are causes by mathematics of the task that PT performs. That is, PT can't do what's impossible.

That Accela wiki page that Wim wrote? There's no info there, just a screenshot and what a filter is for. No sarcasm, just old-timer mannerism. Thanks for the info on the driver. It's now installed, and money can be spent on cigs, beer and vodka as usual. Cheers!

Is there audio input for payware driver? The instructions were something to refer basic questions to, but that you've actually READ them and were able to act on them. My hat off to you, Sir! cheers, -sh

It's true, CAYMAN/evergreen hardware has hardware bugs, that are known to anyone who looks. Ben from Laminar got an ATI issue fixed within WEEKS since he actually bothered to have contact with the vendor. Not to mention his small sales in comparison to ED. All it takes is effort, not posturing about whether there's a hardware bug or not.

Denco, are you same person as here https://github.com/opentrack/opentrack/issues/49#issuecomment-55126452 ? If there are any further issues drop a note on the bug tracker. FWIW, the issue was fixed some months ago. I'll remove old versions with the bug from the website sometime. Note that we now have a FAQ, guys, please link to it, since it only has a few answers and 80% of questions are answered there. Are these PointTracker glitched view issues -or- are they short flashes every few seconds that occur only in DCS? The problem was reported more than half year ago and wasn't fixed. Just about every approach didn't help or made it worse. These aren't even flashes to (0,0,0 0,0,0), these are random! Unless DCS team helps, I see no idea to make it work for the time being. I understand that playing with DLLs, editing Lua scripts sucks, but the solution isn't known, and issue only exists in DCS so far.

Hey, Need a favor from DK2 user. There's opentrack build on dropbox with "test-" prefix. See if the damn thing works. It's using the 0.4.1 SDK but when new build environment works, 0.4.2'll be integrated. -sh

Guys, Common issues are answered here: https://github.com/opentrack/opentrack/wiki/Common-issues Software's explained here: https://github.com/opentrack/opentrack/wiki/Concepts-used Rather than advising new users to make a LED rig, point them to Aruco tracker: https://github.com/opentrack/opentrack/wiki/Aruco-tracker

Hey guys! Filter code in 2.2 is broken, yes. It's better to report it on the bug tracker. The bug was there for few months and no one noticed.

Do you even know if what you're attempting is defined behavior? Developers usually attempt using different code paths, for instance x-plane 10 developer blog and ATI woes about cars and weather. Software is complex, drivers are buggy, given that it only manifests in DCS engine seems fishy. Not fixing major visual artifacts for the matter of principle is for me plain foolish. Dozens of sims got it right, you can't. Whose at fault? Apparently ATI users for buying your product.

Disabling HDR helps no matter how fresh the driver. Shame on ED for not fixing this long-standing issue.

Hey guys! As Wim stated, this is no official build. However! It has been rebased on the current 1.7 repo, taking advantage of features Wim added while merging back my changes, as well as ones he made himself. I fixed some pretty critical bugs (see SF forum for the details) but functionality-adding changes are pretty nonexistent. Repo: https://github.com/sthalik/facetracknoir Also, I plan to add a new tracker sometime, but only after it gets good, because it's still in heavy development. See my other github repo. @doveman: Try tweaking Accela and increasing your curve output for yaw. It's also recommended to calibrate your camera. I can supply a lens file if needed. Please email me if you're interested. Since you're using the Eye, just tell me which FOV you use (70-ish or 50-ish, I need the precise value). I can then compute a lens file. Oh, I also need the EXACT name of the camera that shows on the FTNOIR screen.

True, true. We, the people developing FTNOIR in some kind of way, are working on getting issues present in 1.6 resolved. So far, fixing jitter present in tracker output, as well as upgrading support for output curves are in the process of being integrated into mainline and for the 1.7 release. While I barely play DCS A-10C due to the complexity of it, it fully works, giving 6DOF and stable output using the SeeingMachines FaceAPI tracker 3.2.6.

Logitech profiler? Apply a persistent profile. Also make sure that you don't designate a launcher as the application, use simulator.exe or similar.