Access violation error:tutorial-apriltag-detector-live

[Hawthorne0]

Hello everyone. When I follow the tutorial of AprilTag marker detection(https://visp-doc.inria.fr/doxygen/visp-daily/tutorial-detection-apriltag.html), the program has encountered access violation error. How can I fix it.

[fspindle]

Which OS ?
Which Compiler ?
Which ViSP version ?
Which grabber used in tutorial-apriltag-detector-live.cpp ?
Does tutorial-apriltag-detector.cpp work ?

[Hawthorne0]

Which OS ? Which Compiler ? Which ViSP version ? Which grabber used in tutorial-apriltag-detector-live.cpp ? Does tutorial-apriltag-detector.cpp work ?

windows 11 22H2,visual studio 2022,visp 3.5.0 and OpenCV grabber. Both programs dont work with the same error(access violation). Any help would be greatly appreciated.

[fspindle]

The first thing to do is to try with visp github version.
Check also that the location of ViSP dll files are in the Path env var.

[Hawthorne0]

The first thing to do is to try with visp github version. Check also that the location of ViSP dll files are in the Path env var.
That's right. When I encountered this error, I upgraded visp using github version firstly. But it still doesnot work with the same error. The location of ViSP dll files were also checked.
I guess maybe this line: detector.detect(I, tagSize, cam, cMo_vec) of tutorial-apriltag-detector-live.cpp arises unexpected problems cause the program could work without error by deleteing this line. I dont know how to fix it.

[fspindle]

There is something wrong in your setup. What is the content of your ViSP-third-party.txt file ?

Try to do a fresh visp build without 3rd parties and run tutorial-apriltag-detector.cpp again.
If it doesnt' work use the debugger to figure out the issue.

[Hawthorne0]

Okay, thanks a lot.

[yangqingnian]

good @Hawthorne0

[Hawthorne0]

I solve this issue by doing a fresh visp and the most important step I think is to switch the vs mode from debug (default) to release. If I use the upgraded visp and switch the vs to debug, the same error shows up. So if you guys have the same error like this, change the vs code mode maybe a good solution after following the tutorial step by step. Finally, thanks a lost for fspindle's help and all contributors of this project.