a colleague showed me the processing sketch and i had to port it to jitter.
i used jit.fprint to read the cvs file that holds the data- it seems it was
made just for this kind of things.
another find was switching jit.gl.mesh [cache_mode] from the default VAR
(vertex arrays) to VBO (vertex buffer object) which made this thing
(1,367,028 point mesh) eat close to nill (cpu) resources.
get Zach's 3d_navigator for