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... | |
| | | | |
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 m... | |
| | | | |
www.jendrikillner.com
|
|
| | | | | ||
| | | | |
mynameismjp.wordpress.com
|
|
| | | First things first: what am I talking about? I'm talking about something that finds great use for deferred rendering: reconstructing the 3D position of a previously-rendered pixel (either in view-space or world-space) from a single depth value | ||
