Closed CoryNessCTR closed 1 year ago
How was this not caught until now?
Was it because everything was inside the Robot
instance, which got constructed later?
It’s C++ exclusive, it’s a race condition in some cases, and if other objects are initialized before the motor controllers, it will bypass the issue. And also we generally tell teams to avoid initializing statically.
Describe the bug Statically initializing a motor controller in C++ throws an exception "NIFPGA: Resource not initialized: GetFPGATime"
To Reproduce
Expected behavior Robot program does not crash