updates readme to reflect changes

Author: diroru

README.md

@@ -4,17 +4,28 @@ It is based on the FullDomeTemplate code from Christopher Warnow, available at h
 
 ### Work in progress
 
-Switching to a raycasting approach in the cube map rendering stage. Will also fix the `createShape()`-bug (as of Processing 3.3.6).
+**DONE:**
+
+- More accurate rendering.
+- Variable aperture.
+- Debug grid (shader-based).
+- Toggle rendering of cubemap sides.
+- 2D overlay image rendering in post. (has unfortunately a noticeable performance penalty).
 
 **TODO:**
-- ~~variable aperture~~
-- reimplement debug grid
-- custom sweet spot
-- toggle rendering of the sixth (or any) side
+- Improve cubemap resolution (or at least visual quality).
+- Implement rendering into background (2D) layer. (Possible implementation would be to send PGraphics as sampler into the shader, but it collides with the samplerCube, haven’t found a solution yet).
+- Custom sweet spot.
+- 4 sides should suffice for fulldome, need to rotate cubemap by 45° for that.
+- Implement picking?
+
+**CHANGES:** (technical)
+- Switching to a raycasting approach in the cube map rendering stage. Uses quad with ray-casting instead of hemisphere.
+- Cubemap sampling set to linear.
 
 ### Overview (original)
 
-A brief descrition of how it works: a 360° view of the scene is generated by rendering the scene 6 times from each direction: positive x, negative x, and so on. The output of each rendering is stored inside a cube map texture, which is then applied on a sphere representing the dome. Hence, the library calls the draw() method 6 times per frame in order to update the corresponding side of the cube map texture (in reality, only 5 times since the bottom side of the cube map is not invisible on the dome). 
+A brief descrition of how it works: a 360° view of the scene is generated by rendering the scene 6 times from each direction: positive x, negative x, and so on. The output of each rendering is stored inside a cube map texture, which is then applied on a sphere representing the dome. Hence, the library calls the draw() method 6 times per frame in order to update the corresponding side of the cube map texture (in reality, only 5 times since the bottom side of the cube map is not invisible on the dome).
 
 So, it is important to keep in mind that if you need to perform some calculation only one time per frame, then the code for that calculation should be put inside the pre() method. Similarly, calculations that should performed only once after the rendering is concluded should be put in the post() method.