Yes... it looks like there could be an issue here. The LargeVolume is supposed to have pager and compressor objects but the constructor you have used does not set these up. I've forgotten what my logic was here... did I mean to check them for null before using them? I don't remember, but the important point is that you are going to want to set them up to get the benefits of the LargeVolume.
To do this, use the other constructor. You can find some code in 'TestVolume' as an example:
Code:
TestVolume::TestVolume()
{
Region region(-57, -31, 12, 64, 96, 131); // Deliberatly awkward size
//m_pCompressor = new RLECompressor<int32_t, uint16_t>;
m_pBlockCompressor = new MinizBlockCompressor<int32_t>;
m_pFilePager = new FilePager<int32_t>("./");
//Create the volumes
m_pRawVolume = new RawVolume<int32_t>(region);
m_pSimpleVolume = new SimpleVolume<int32_t>(region);
m_pLargeVolume = new LargeVolume<int32_t>(region, m_pBlockCompressor, m_pFilePager, 32);
The LargeVolume does work and we are using it in Cubiquity. That said, SimpleVolume is easier and you can probably have hundreds or millions of voxels before worrying too much about memory. Actually, we do have plans to merge these into a single volume type but I'll talk more about that in the future.
