3D rendering: Difference between revisions
Marius851000 (talk | contribs) First version of Memory use table |
Marius851000 (talk | contribs) m →Memory: minor spelling |
||
| Line 11: | Line 11: | ||
The 3D engine is | |||
The 3D engine is capable of rendering in 2D, simply by rendering rectangle in front of the virtual camera, which is what EoS always does. The way this game work is by first buffering the elements to render to a buffer and then a function will submit those to render (probably during VBlank), which will then take effect on the next frame. | |||
The 3D engine can only render on the main screen, which in EoS is the bottom screen. Some game (but not EoS) render on both screen by switching the main screen every frame, dividing by two the framerate from 60 to 30 FPS. | The 3D engine can only render on the main screen, which in EoS is the bottom screen. Some game (but not EoS) render on both screen by switching the main screen every frame, dividing by two the framerate from 60 to 30 FPS. | ||
| Line 20: | Line 21: | ||
The game store | The game store its 3D data in WTE files. It contain the texture and the palette, but not where the file will be stored in the RAM, which is specified in the game’s code. Here is table of the (known) allocation the game make. It is probably exhaustive. | ||
ProcessWTE is the function used to load them. | ProcessWTE is the function used to load them. | ||