I'm not drawing an entire map. My camera class only allows for the drawing of what's visible and then a little extra.Quote:
You don't want to store 400kk structures in memory. If you really want, you should do the same thing that the swap memory. Write a "memory" block to the disk. In Photoshop, you can easily edit a picture with a working space of several Mo. A little image will take at least 20 Mo. Photoshop is rendering the part you're viewing.
Just create a temp file that will be purged when closing the app (GetTempPath?) and write the unsaved part there. With memory for actual view, temp memory for unsaved change and the source file for the saved but unviewed parts, you'll have a low memory utilization. And, a map shouldn't be 1 Go based on what I saw in CO2. So, the disk speed will not be a big problem for reactivity of the program.
Visual Tiles are just "ushorts"
Data Tiles are the real memory whores... Data Tile is a class