Hello!

Thank you for flagging this to us
It could be that the new software version has some changes that are not supported yet.

For us to get a better view of things, please send in the logs: https://www.animaze.us/faq/tech/gatherlogs via email

Please include details on your Tobii hardware and software versions too.

So far we have seen no logs coming in.
If the needed context logs are not being sent in, it limits our investigation horizont.

Originally posted by OttersGonnaOtt:

I'm trying to set up my Tobii Eye Tracker 4C for eye tracking, but Animaze just won't initialize it.

There's a new early version ( Animaze 1.26.12598 ) on the Next-Version beta branch where the old Tobii 4C not initializing should be sorted out.

Unlike the more modern Tobii 5, the 4C had no wink support and that was throwing a wrench in the gears.

Oh, wow. I didn't realize I was getting responses on this because for whatever reason I wasn't auto-subscribed to my own discussion. Ha.

If you still need logs I can definitely get them to you. I'll try out that release candidate build tonight and see how it works out, with some feedback here as well.

Thanks for being patient with the silence there!

Success! The beta branch is very unstable for me, but the Tobii 4C does track and it tracks quite well at that. Reverting to the default branch solved the instability (crashing on panel/tab change, mostly) but as expected broke the 4C support you fixed up.

I think that does the trick. Thumbs-up from me at least for putting that in the next master build. I'll make due with camera based eye tracking in the master branch for now to have a stable build and look forward to the 4C fix merging at some point in the future! :3

Originally posted by OttersGonnaOtt:

Success! The beta branch is very unstable for me, but the Tobii 4C does track and it tracks quite well at that. Reverting to the default branch solved the instability (crashing on panel/tab change, mostly) but as expected broke the 4C support you fixed up.

I think that does the trick. Thumbs-up from me at least for putting that in the next master build. I'll make due with camera based eye tracking in the master branch for now to have a stable build and look forward to the 4C fix merging at some point in the future! :3

Thank you for following up.

For crash-fixing, it is important to send in logs and detailed repro-steps to support[@]animaze[.]us , if you could capture the logs from the next version branch, immediately after a session where you got it to crash and if possible also a link to a video recording of the steps you take to get it to crash, it would be super helpful, as it would enable us to get the crash to trigger on a dev machine, catch that case and address that before the launch to main.

We didn't get any other crash reports from it from early testers so it may be specific to Tobii4c users, we do hope you can send in the logs and detailed context :).

Alright, I tried to recreate the crash issue and couldn't, not outright. Windows had updated and rebooted between the issue and the repeat testing attempt, and after digging through LOADS of event logs I found the culprit: Some AI training I was doing on my 4090 had an unnoticed memory leak and was locking up the driver when swapping render modes. After about 20 epochs of training later, I reproduced the situation... and sadly Animaze was crashing in a manner where the logger thread was severed before it could record anything to file. Windows event logs show the nvidia driver crashing from an async loop that engaged a 3D mode. This happened when swapping a character to any other character, upon the loading bar filling and (I'm assuming) trying to render the 3D model afterward. The only errors in the log file (in beta branch) regarding async requests (and the only errors at all, actually) were some unhandled promise errors, all stating the same thing:


Upon forcing the memory to clear out (manual driver restart) the GPU driver no longer would crash using Animaze, and while testing I tried the beta branch as well as the master branch, both crashing the same abnormal way. Of note however, Animaze was NOT the only application that would crash when tested. Some DX12 games using ray tracing for example would crash upon loading the game world (swapping to a 3D mode). Also an AI voice changer would crash upon engaging the tensor cores to assist. Definitely seems like some combination of bad memory garbage collection in the nvidia drivers and a bad leak in my AI training scripts. I don't think this is a problem with Animaze, rather a local issue with my setup and hardware usage.

Long story short: You guys are probably in the clear, though you may want to check your promise chains for proper try/catch handlers. :3