And here comes the slow descend into less and less interesting development posts...
Not much to say apart from I've been playing around with biomes, testing how to spread them across the world properly and stuff and then this happened:
That gave me a total FPS of -2. Somehow I need to figure out what is causing the FPS leak and if there isn't a specific thing causing it, whether or not the caching system is actually working properly.
I've also added another new type of seed, sandstone:
As you can see the amount of rectangular pieces of stone is fairly low now. This is because I'm overhauling the world generation to make each seed up of its own very small mini-biome. You can also see that in effect with the new tall grass generation:
Aside from all that I've been working on putting dungeons properly back into the world generator to compliment the Earthquake system. If dungeons didn't get their own IDs and weren't saved then the Earthquake system would essentially be a waste of time eventhough it adds a whole new wave of content. I'm also going to try to vary the dungeon themes (like realms) and finally I'm going to try to make a Village mini-biome with a whole host of new seed types.
I guess this is what I'm trying to get at: I.imgur.com
Yeah I know what you mean and thats probably what I'm going to try to do.
You try rendering 56000000x56000000px image in DX8, and get any higher than 1 FPS. Plus, the caching system in place already does something similar to that, but, because of the sheer amount of graphics, it wouldn't matter, anyway. xD
This is where some Computer Science play can come in. Maybe he can render chunks that match around a (128x128) grid size. When he reaches the limit, it re-renders the next chunk. That should reduce your 56,000,000px down to 4069px's (implying the texture size is 32x32px).
Which is why me and Sekaru are actually doing chunks, right now. xD. TeamViewer, ftw.
And by "me and Sekaru" he means him whilst I work on a game for charity ;].