Explore >> Select a destination
|
You are here 
|
brutalism.rs | ||
| | | | |
0fps.net
|
|
| | | | | Large voxel terrains may contain millions of polygons. Rendering such terrains at a uniform scale is both inefficient and can lead to aliasing of distant objects. As a result, many game engines choose to implement some form of level of detail based rendering, so that distant terrain is rendered with less geometry. http://www.youtube.com/watch?v=4S1sYUHV20s In this... | |
| | | | |
wassimulator.com
|
|
| | | | | Blogpost explaining how the game was made. | |
| | | | |
etodd.io
|
|
| | | | | This week was a lot of under the hood improvements. The voxel engine got a TON of performance optimizations, which allow my Nvidia GTX 260 to render my test scene at 100-200 FPS. Screenshots: New features: Rough-draft tutorial level with instructions and whatnot. Fullscreen toggling on-the-fly by hitting F11 Rudimentary fog effect Performance optimizations: Voxels are now rendered as surfaces, rather than complete cubes. This lets me cull a lot of unnecessary geometry. Voxels are now split into chunks. This lets me easily implement frustum culling and view distance, which helps tremendously with shadow map rendering as well. I fixed some bugs in the voxel modification code, making voxel modifications of up to 100-150 cells practically instantaneous. Shadow maps and reflections are now rendered every other frame. It's a hack, but the important thing is that the gameplay is responsive. My biggest development challenge was my battle with fullscreen toggling and graphics resource management. Switching from fullscreen to windowed mode, the entire XNA GraphicsDevice is invalidated, along with every vertex buffer, texture, shader, everything. So that was interesting. | |
| | | | |
jeskin.net
|
|
| | | |||
