Atracsys fusiontrack 500 & AtracsysMarkerCreator.exe not registering fiducial markers

[LiamIsSuperCool]

Hello,
I am working on a project that involves using PlustoolKit to communicate with the Atracsys fusionTrack 500 to get data in Slicer using SlicerIGT. I am having a few issues with Plus and the Atracsys communicating. I am able to launch the Plus Server without it crashing and the Atracsys is recording properly which I can confirm using the demo that comes in the AtracsysSDK. The problem I am currently facing is that the Plus Server does not recognize the tools with the fiducial marks I have. I manually created the .ini file for the tool I'm using because I am also having troubles with the AtracsysMarkerCreator.exe application that comes with the PlusApp package. The AtracsysMarkerCreator fails almost immediately with the message "too few fiducials in frame. Ensure marker is fully visible and try again". I have confirmed through the Atracsys demo that the markers are in frame before running the AtracsysMarkerCreator. I am unsure of what to do at this point as I cannot determine the exact problem as to why the AtracsysMarkerCreator cannot see the fiducials.

[Khaleel-HTIC]

If the created geometry file is being detected in demo software of Atracsys then for sure it will be detected in plusapp. Can you show a visual illustration of your problem

[Lukas-Novosad-UKBB]

Hi!

We are working with an Atracsys spryTrack 180 and we would like to generate the geometry INI file for a custom marker. However, I do encounter the same issue as @LiamIsSuperCool, namely that the AtracsysMarkerGenerator.exe almost immediately returns with the error message
"Too few fiducials in frame. Ensure marker is fully visible and try again.| in E:\D\PTNPSTb\PlusLib\src\PlusDataCollection\Atracsys\AtracsysMarkerCreator.cxx(192)".
Does anybody have an idea why this is the case? The command line string calling the tool is as follows:
AtracsysMarkerCreator.exe --marker-name=NAME_STRING --description="DESCRIPTION STRING WITH SPACES" --geometryId=1000 --verbose=5
(adding the parameter --num-frames=2000, for example, does not help)
I have to point out that we use fiducials from Vicon on our custom marker, but this should not be relevant to my understanding.
Also, I tried using the official snap fiducials from Atracsys, albeit to no avail.
Finally, I tried to scan the Atracsys Tindax 302 with the official snap fiducials and I received the very same error message.

Meanwhile, I will create the INI file for the geometry manually, but it would be nice to use the AtracsysMarkerGenerator.exe.

Unfortunately, I do not have the time to delve into the source code of Plus. If this should be the case in the future, I will post any findings or potential solutions to the issue here.

[Sunderlandkyl]

What version of Plus do you have installed? There were updates last week that may have fixed the issue.

[Lukas-Novosad-UKBB]

Dear Kyle,

thank you very much for getting back to me, I had a version installed from the end of July 2025
PlusApp-2.9.0.20250730-spryTrack-Telemed-Win64
and after installing the latest nightly build
PlusApp-2.9.0.20250912-spryTrack-Telemed-Win64
I can confirm that the AtracsysTrackerGenerator.exe works as expected! 😄 🚀

The Atracsys "Demo spryTrack Software" is able to detect the custom marker (Note: the INI file must follow the naming convention "geometryID*.ini" in order for the software to pick it up).

fCal is also able to detect the custom marker (serves as Stylus), together with the Tindax 302 (serves as probe).

Thanks again for the help, this is really appreciated!

Cheers,
Lukas