BLUF: A wild guess @jjhembd : Do you know from the tip of your head if voxel picking involves some picking buffer/texture that may be limited to 65k elements?
(If not, don’t spend too much time here - it’s really just a sanity check for my guesses…)
It may not be immediately helpful for resolving the issue, but I played around with that a bit, and with
this.dimensions = new Cesium.Cartesian3(360, 200, 1);
this.availableLevels = 1;
I noticed something strange: The highlighted/picked voxel is just at the wrong place - and not “always”:
First, it highlights the voxels under the cursor. A bit further to the north, it suddenly highlights voxels that are further to the right. But the hovered voxels still seem to be “mapped” to consecutive(!) voxels somewhere else.
It shows the voxel index in the output at the top. And this is suspiciously close to 65k. Maybe there is some “picking texture render pass” that uses uint16 textures or so… (Again, just a wild guess, but the point is that it does not not pick - it is just returning “wrong” voxel indices…)