Unexpected VCS C++ pro behavior

[jpearman]

@technik3k

There got to be some rational explanation of why this is happening.

yes, there nearly always is.
for example, we know that the sdk in VCS still has a bug when using largestObject (fixed in the SDK included with VEXcode)

Vision Sensor config - objectCount inconsistent

takeSnapshot can be used in a number of ways. takeSnapshot is filtering all the objects** that have been received from the vision sensor into an array of objects that you are interested in, you access the array of filtered objects using the “objects” array. The objects we receive from the vision sensor in the brain have already been sorted by size, the largest object is always received first. When takeSnapshot is used like this Vision.takeSnapshot(0); We are asking for all objects (ie. th…

@technik3k

And, finally, least likely but still possible is the bug in the compiler itself.

Not impossible, both VCS and VEXcode are using clang, not gcc, and we know of one really frustrating bug that I’ve never found a workaround for.