Opentrack with a new feature called Snap View

[z1j]

Hi everyone,

I’ve prepared an experimental opentrack build with a new feature called Snap View.

The basic idea is simple: you can place named points on the Mapping curves, such as Yaw1, Pitch1, X1, and so on. These points then appear in a separate [b]Snap View[/b] table, where one or two buttons can be assigned to each point.

While a button is held, the corresponding output axis is set to the Output value of that point. When the button is released, opentrack returns to the normal Mapping curve behavior.

This can be used for quick fixed view directions or camera positions, for example:

* look left;
* look right;
* look back;
* look at the dashboard;
* move the camera toward a mirror;
* create any partial or full 6D view preset using Yaw / Pitch / Roll / X / Y / Z.

Snap View does not replace normal tracking. Axes without an active assigned button continue to work normally through the Mapping curves.

The implementation also adds Snap View profiles. Each profile has its own:

* Mapping curves;
* points on those curves;
* button assignments for those points.

When switching profiles, the curve shapes, their points, and the Snap View table contents switch together.

The current implementation is available as a pull request to opentrack. It is still experimental, so feedback would be very useful, especially on:

* whether assigning buttons to curve points feels convenient;
* whether the profile behavior is clear;
* whether old opentrack profiles migrate correctly;
* which Snap View use cases are actually useful in games and simulators;
* what parts of the UI should be simplified.

If anyone wants to try it, I can provide a Windows installer. The build I’m testing also includes the additional trackers I built with opentrack: PointTracker/OpenCV, NeuralNet Tracker, ArUco Tracker, and others.

Download (GitHub)

[3ra_Luke]

I use opentrack with Tobii 5.0 for IL-2 and WarThunder. I installed your version, because I find it very interesting, and now the camera is not working, using Tobii plugin or UDP. Nothing works. Installing the official version, solves the problem.  Please, add all the additional trackers so I can test your version with Tobii camera. Its a lot better than use a web cam. 🙂 

(I also noticed in your version a new option called something like "constant autocenter"?. I want to try it too. I need to center opentrack too often, so maybe that option is the solution.)    Thanks!

[z1j]

11 часов назад, 3ra_Luke сказал:

not working, using Tobii plugin or UDP

My version of OpenTrack is perfectly capable of receiving data via UDP.

[3ra_Luke]

15 minutes ago, z1j said:

My version of OpenTrack is perfectly capable of receiving data via UDP.

Well, I dont know what parts are missing from the official version. What is a fact is I can't use Tobii with your version, using the Tobii plugin (your version missed that one) or using UDP method. Installing the official version, overwriting yours, I got both working instantly, although I prefer UDP method (and Tobii tech support too, caused they recommend it on their web). I suppose you are not Tobii user, so you can't verify my tests. 

[z1j]

55 минут назад, 3ra_Luke сказал:

using UDP method

Are you sure you are using the correct UDP port number?

I couldn't find a currently available public NuGet package for Tobii Stream Engine.
opentrack's tracker-tobii still requires a local SDK_TOBII path with the Tobii headers, import library, and runtime DLL.
Tobii's current Streams SDK page says the SDK is shared by Tobii together with a license key after contacting them, so I can't build the native Tobii plugin without access to that SDK.
 

I don’t think this is specific to the modified build.

Could you please test the UDP path separately on your system?

For example, I tested it with two local opentrack instances:

1. First opentrack instance:

   • Input: test tracker

   • Output: UDP

2. Second opentrack instance:

   • Input: UDP

   • Output: TrackIR

With this setup, I can see the pose data being transmitted through UDP correctly and the second opentrack instance receives and forwards it as expected.

So before assuming the issue is caused by the modified build, please try the same local UDP loop test:

• start one opentrack copy with a test input and UDP output;

• start another opentrack copy with UDP input and TrackIR output;

• check whether the second instance receives motion data.

If this works, then the UDP input/output path in opentrack is functioning, and the problem is probably in the Tobii Game Hub UDP configuration, port, address, protocol format, firewall rules, or another local setup detail.

If it does not work, please share the exact UDP settings from both opentrack instances, including IP address, port, and selected protocol/options.

Edited Saturday at 07:37 PM by z1j

[3ra_Luke]

I simply use this guide and it works: War Thunder – Tobii Help Center  I dont change ports. Works instantly.

In the guide mentions do not use Tobii Eye Tracker cause it disables Game Hub features such as Camera Boost, profiles, and key bindings, but also works for me using the Tobii plugin included in the official version. I prefer UDP, but this option works the same.  Other options do not work.

[z1j]

7 часов назад, 3ra_Luke сказал:

using the Tobii plugin included in the official version

In addition to the test with two OpenTrack instances that I described above, if I were you, I would do the following:
1) Install two versions of OpenTrack: the official one and my build.
2) Launch the official OpenTrack with Tobii input and UDP output.
3) Launch my build of OpenTrack with UDP input and FreeTrack output.
I look forward to the results of these two tests (the previous message and this one). Don't forget to verify that the port numbers match in both tests.

[3ra_Luke]

Man, that´s what I did from starters. But I did it again to confirm, and I had the same results with UDP input/output. With Tobii input, I can't do any test because, on your version, is not there unfolding input sources. In the official version, is there.

When I move my head, the octopus is dead on your version and alive on the official version. That's all.

If you don't have a Tobii tracker, you can't check it by yourself, so trust me.

[z1j]

3 часа назад, 3ra_Luke сказал:

With Tobii input, I can't do any test because, on your version, is not there unfolding input sources

Judging by what you’ve said, you aren’t doing what I suggested.
If you want to run a test, do the following:

1) Launch the official OpenTrack and my OpenTrack simultaneously.
2) In the official OpenTrack, set the input to Tobii and the output to UDP.
3) In my OpenTrack, set the input to UDP and the output to Freetrack.

Make sure the port numbers match.

[3ra_Luke]

My last test. Tobii plugin is not there. UDP works in your version only if I have both running, official with Tobii plugin and yours with UDP.

If I have both versions UDP running, only one works even if I change the ports i.e. to 4242 and 4243. But if I leave yours active, inside IL-2, is not working.

Anyway, after some tweaks I noticed Tobii plugin seems to work better than UDP and I´m keeping it.  Maybe you should cheeck in your version if these files are missing "C:\Program Files (x86)\opentrack\modules\tobii_stream_engine.dll" or "C:\Program Files (x86)\opentrack\modules\opentrack-tracker-tobii.dll" because I think they are the key to solve this problem with Tobii.

 

Edited yesterday at 04:41 AM by 3ra_Luke
Update