I actually figured out that the messages are going to stderr and was able to suppress that output with freopen("NUL", "w", stderr); (on Windows).
In the future, it still would be nice to have control over the logging level though!
Search found 3 matches
- Wed Mar 02, 2016 2:56 pm
- Forum: Motive
- Topic: Disabling Motive API log messages
- Replies: 2
- Views: 2297
- Tue Mar 01, 2016 6:54 pm
- Forum: Motive
- Topic: Disabling Motive API log messages
- Replies: 2
- Views: 2297
Disabling Motive API log messages
I'm using the Motive API to receive rigid body data. When a rigid body is in view, a large number of log messages start to appear in the command console (stdout). They're all in the following format: ...npoint\thirdparty\ceres\v1.10.0\internal\ceres\wall_time.cc:74 DenseNormalCholeskySolver::Solve D...
- Fri Feb 26, 2016 3:24 pm
- Forum: Motive
- Topic: Problem loading a project file with Motive API
- Replies: 1
- Views: 1924
Problem loading a project file with Motive API
I'm trying to run Motive in headless mode using the Motive API. When I call TT_LoadProject(), it returns NPRESULT_FAILED. The code can continue on and does communicate with the Motive API -- it can enumerate the attached cameras, for instance. I would like to get the project file to load, though, si...