documentation:planning:todo
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
documentation:planning:todo [2011/06/06 08:55] mhgamework [Things to do] |
documentation:planning:todo [2012/05/25 16:54] (current) chuptys |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== TODO ====== | ====== TODO ====== | ||
| - | ===== ‘Small’ and needed technologies ===== | ||
| - | + | See the [[https://docs.google.com/spreadsheet/ccc?key=0AmDq_8xEeFI8dEFoR0lpR1F3RjRfaUFDdnRkaEczOEE# | |
| - | * Implement SSAO (Screen Space Ambient Occlusion) | + | |
| - | * Fix unrealistic water | + | |
| - | * Implement Parallax mapping | + | |
| - | * Create spot lights + shadow mapping | + | |
| - | * Create Depth of field | + | |
| - | * Create HDR lighting | + | |
| - | * Light beams / light shafts | + | |
| - | + | ||
| - | ====== Things to do ====== | + | |
| - | + | ||
| - | * Occlusion culling | + | |
| - | * Pre-Z pass | + | |
| - | * Maybe use NShader: visual studio shader syntax highlighting. Update Cascaded shadow mapping using this : http:// | + | |
| - | * Also think about using a geometry buffer implementation (see DirectX10 module) http://www.wolfgang-engel.info/ | + | |
| - | * Make a XML helper library, which uses the exact same functions for loading as for saving. This way save and load code will be equal. (Make sure this is possible first, I don’t think so actually) | + | |
| - | * Take a Serious look at Light Pre-Pass rendering: http:// | + | |
| - | * Implement PSD reading: http:// | + | |
| - | * Bake a large scale texture for the terrain to counter the tiling problem + major performance boost. | + | |
| - | * Terrain: Use the GPU instead of the CPU for weightmap and heightmap painting. | + | |
| - | * Better multitexturing: | + | |
| - | * Add, besides Geomipmapping, | + | |
| - | * Create impostor system. Also think about the depth twiddling algorithm. The basic idea here is to pick a near and far plane of 0.1-400, render all objects in that range, and then pic a near and far plan of 400-20000 or more and render all objects after that, behind the already existing pixels. This should be possible by, in the second pass, setting all the depth values of pixels rendered in the first pass to the near plane of the second pass (which is a value of 0) and leaving the other pixels at a value of 1 (far plane). This should allow for dramatically GINORMOUS sight ranges. **this technique has been found and suggested at blogs too. Implement it !** | + | |
| - | * For the editor, correctly implement the Black & White hand-style camera movement correctly. The terrain editor is supposed to use this, but the rotation currently centers at the hand when rotating, this should not be like that. Note: In black & White, the hand moves like a cursor in screen space, so world movementspeed is not lineair with mouse speed. | + | |
| - | * While we’re at it, implement Black & White style object pickup and dropping on the terrain. | + | |
| - | * Add functionality to run in a fixed frame mode, rendering the frames to files for video creation. Later on, also add functionality to disable rendering and record the audio, so it can be multiplexed with the recorded video later. | + | |
| - | * Implement Linear-Speed Vertex Cache Optimisation as in http:// | + | |
documentation/planning/todo.1307350520.txt.gz · Last modified: 2011/06/06 08:55 by mhgamework
Page Tools
