You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feature is not downwards compatible since it uses another component of a vector that contains the depth-information. Projectionmatrices are now generated from OrthogonalDepthProjection (see #29).
The text was updated successfully, but these errors were encountered:
I think the only performant and viable solution is to implement a new renderer (TextDepthRenderer/TextZRenderer/similar), though this results in code duplication inside the existing TextRenderer, the drawing algorithms need tweaking everywhere for Z-capability, and if someone doesn't want it, it's not easy to turn it off/on without losing much performance while avoiding code-duplication.
Creating a new renderer is really high code duplication, one can use a bool template argument zbuffer to specify different render behaviour. This means everything regarding render needs to be moved inside a .hpp.
If somebody renders something, he/she will use in 99% of cases the z-buffer. Even for point rendering, a z-buffer that correctly controls what is rendered on top improves the render result. So it should be implemented by default. People have to look out to use the correct transformations.
This feature is not downwards compatible since it uses another component of a vector that contains the depth-information. Projectionmatrices are now generated from
OrthogonalDepthProjection
(see #29).The text was updated successfully, but these errors were encountered: