Java Library written IN Java

[theagentd]

@Longor1996

Actually, there is a good use for software rendering: Occlusion Culling by Software Depth Testing.

Draw a bunch of occlusion bounding boxes with a software renderer into a depthbuffer, then check with another pass if the bounding boxes of any object are hidden by the pixels in the software depthbuffer. Its one of the fastest ways to do occlusion culling; the company Umbra is selling a library that uses this technique.

Someone should write a software renderer for occlusion culling in java…

The primary reasons for doing this was either having a very weak GPU where culling a single triangle no matter the CPU cost was a win (Playstation 3) or attempting to avoid a number of expensive single-threaded draw calls with threadable occlusion testing while avoiding expensive synchronization by reading back the depth buffer. Hopefully with Vulkan-based engines this won’t actually be needed any more, as draw calls can be threaded and there’s no high driver overhead of doing GPU occlusion culling.

[trollwarrior1]

@Longor1996

@trollwarrior1

Writing custom renderers just for fun is cool, you just need to realize that you only do it for fun and it will not be usable in any real world scenarios.

Actually, there is a good use for software rendering: Occlusion Culling by Software Depth Testing.

Draw a bunch of occlusion bounding boxes with a software renderer into a depthbuffer, then check with another pass if the bounding boxes of any object are hidden by the pixels in the software depthbuffer. Its one of the fastest ways to do occlusion culling; the company Umbra is selling a library that uses this technique.

Someone should write a software renderer for occlusion culling in java…

This is a very specific case. I meant that writing an entire API like OpenGL purely in Java has no real world applications.