quote:
Originally posted by Anti-Paragon:
<STRONG>I'll see if the new version of the visualizer will run my big ol' map properly, since the last one couldn't.</STRONG>
Will have a new version out in the next few days that has improved memory management, as well as greatly improved loading times.
As far as the triangle estimate goes, the engine very easily hits 150k. It doesn't seem like it, but since each tile is capable of 10 polys, and each layer of a 4x4 map has ~36k tiles in it.... adds up VERY quickly. I feel that the current engine is almost pushed to it's limits, especially since I'm about to add flow rendering and the poly count will increase further.
For those who are curious, I'm using display lists to speed things up, and ultimately the entire scene gets shoved into one large display list and sent to the card. Ideally, the entire list is stored on the video card's memory (if there is enough), so there really isn't much optimization to do other than LOD, and the engine isn't built for that.
I'll put out another release or two to address issues everyone has brought up, and possibly add door/object rendering in the future when the memory hackers reverse engineer all that information. Other than that, I'm content with this program as more of an overview visualizer that doesn't get into fine detail.
I think my next project will be a visualizer that DOES get into more detail (1st person dwarf mode, prettier landscape, better looking water and trees, LOD). The focus will be more along the lines of Anti-Paragon's idea... nice screenshots
I'm new to the realm of 3D programming, so if any wizards out there feel like helping I'll gladly accept it.