That's an idea I guess, the only other option to to stick the usual method, and create the arrays on the fly from stored data.
MD2 does store 'per frame' information on the mesh, in the case of that one in the pics, 198 frames @ 1948 bytes per frame = approx 385k. That's for the stored MD2 though (data is shorts & bytes), I've been converting it to float arrays, I'm gonna try it on the fly instead, save on memory.
MD2 does store 'per frame' information on the mesh, in the case of that one in the pics, 198 frames @ 1948 bytes per frame = approx 385k. That's for the stored MD2 though (data is shorts & bytes), I've been converting it to float arrays, I'm gonna try it on the fly instead, save on memory.