Closed izatar closed 7 years ago
@jevertt looks like the check should be updated to == 1 instead of > 1?
It looks like solver.Init() can be called multiple times without any bad side-effects, so this wasn't noticed. But, yes - that's not intentional - it's a bug.
Fixed with #371
Here is the InitializeSolver() function I see in my sync'd holotoolkit-unity:
I see Solver_Init() resolving to:
which resolves to something in the C++ code in Holotoolkit:
It appears the Solver_Init() always returns 1. But, the function in LevelSolver.cs is checking for ">1" so it appears that " IsSolverInitialized = true;" never happens. I put in a debug there and it does in fact look like it never gets set right, and so appears to be calling InitializeSolver() on every update.