Thanks for the reply Greg. That's the wierd part for us, we aren't passing big numbers to the initializer. The size is calculated at run time. When we use the exact same number inputs from a vi that hasn't been incuded in our robot project, everything compiles and runs fine.
We were trying to debug our elevator code offline, because one case that we tested on the robot generated different numbers than we got when we built and tested the logic offline on the PC.
Here is a link to our git repository. The Development branch has the code.
Elevator.vi - our problem child
Motion Profile Filter.vi - The sub-vi
Filter Tester.vi - VI that runs fine with no compile issues, containing the sub-vi.