Updated 2D vs 3D development with raylib (markdown)

Ray
2016-03-23 20:58:03 +01:00
parent 730485f060
commit 2a5eabe461

@ -25,7 +25,7 @@ In addition to the above problem, we have 2D vs 3D mixing. We use the same buffe
Sharing buffers for 2D and 3D is simple and works ok but presents a problem when mixing 2D and 3D: `DEPTH_TEST`. 2D screen elements are drawn in front of or behind the 3D elements; we don't want that.
An issue was introduced to try to find a solution for all this problems: https://github.com/raysan5/raylib/issues/89
An issue was introduced to try to find a solution for all this problems: [Issue 89](https://github.com/raysan5/raylib/issues/89)
A first idea was adding additional LINES and TRIANGLES buffers only for 3D but it was discarded due to the extra complexity and memory usage for raylib, considering that most of the time raylib users will probably use the library for 2D games and even in the case of using 3D, loaded 3D models are stored in separate static buffers. No need to overload the library with a new set of dinamic buffers.