glen/dyna3
1
0
Fork 0
Code Issues 10 Pull Requests 1 Actions Projects Releases 2 Wiki Activity

Start writing up display prototype

Vectornaut 2024-08-26 08:06:42 +00:00
parent e97dee9a72
commit d01c9a7a4e
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Display.md Normal file

@ -0,0 +1,10 @@
A display prototype is under development on the [`app-proto`](../src/branch/app-proto) branch, in the `app-proto/inversive-display` folder. It only displays spheres so far.
## Concept
Right now, we're drawing all the spheres in a single fragment shader. For each pixel, we do ray-casting to get a fragment for each sphere, and then we depth-sort the fragments to handle translucency.
## Performance limits
* **Array size.** As of commit `a34fd0f`, the SPHERE_MAX array size seems to affect frame rate a lot, even though we should only be using the first few elements of each array. Not sure whether this is coming from a depth-sorting bug, a memory handling detail, or something else.
* **Shader variables.** Browsers seem to limit the number of variables that fragment shaders can store. For example, see this [vulnerability report](https://issues.chromium.org/issues/40067239) and [code review](https://chromium-review.googlesource.com/c/angle/angle/+/4503753) for Chromium. This limit doesn't seem to be part of the OpenGL standard, so it's hard to pin down.