Integration of new VRidge API?

Elliot Hawkins repo owner

As mentioned in issue #6, PSMoveFreepieBridge is meant to bring positional tracking data from PSMoveService to Freepie. Adding additional services would require substantial rework and is outside of the project scope. I don't mean to be rude in saying this, but PSMoveFreepieBridge just isn't set up in a way that allows for additional services to be added. Even if it were, I unfortunately don't have the time.

The good news is, from the link you posted it looks like Riftcat is interested in integrating PSMoveService support themselves. That would remove any need for PSMoveFreepieBridge!

Even if they don't, it should be much easier now to write a bridge than when I originally wrote this one. A large part of why PSMoveFreepieBridge is so clunky is because it has to move between many different languages (C++ to C, C to C#, C# to Python). These were all needed because in the past, the only way to interact with PSMoveService was through C++ and the only way to interact with VRidge was FreeTrack. Now PSMoveService is switching to a C-based API and VRidge is adding a sockets based API, so someone else can do a much better, cleaner, easier to read and easier to use bridge between them using one language.

2017-03-24T03:20:31+00:00

Comments (2)

Elliot Hawkins repo owner
As mentioned in issue #6, PSMoveFreepieBridge is meant to bring positional tracking data from PSMoveService to Freepie. Adding additional services would require substantial rework and is outside of the project scope. I don't mean to be rude in saying this, but PSMoveFreepieBridge just isn't set up in a way that allows for additional services to be added. Even if it were, I unfortunately don't have the time.

The good news is, from the link you posted it looks like Riftcat is interested in integrating PSMoveService support themselves. That would remove any need for PSMoveFreepieBridge!

Even if they don't, it should be much easier now to write a bridge than when I originally wrote this one. A large part of why PSMoveFreepieBridge is so clunky is because it has to move between many different languages (C++ to C, C to C#, C# to Python). These were all needed because in the past, the only way to interact with PSMoveService was through C++ and the only way to interact with VRidge was FreeTrack. Now PSMoveService is switching to a C-based API and VRidge is adding a sockets based API, so someone else can do a much better, cleaner, easier to read and easier to use bridge between them using one language.
- 2017-03-24T03:20:31+00:00
Elliot Hawkins repo owner
- changed status to invalid
Outside of project scope.
- 2017-03-29T16:48:04+00:00
Log in to comment