Zig raycaster fun https://git.l-3.space/zirc/atom/walls.png?h=polygon_walls 2021-10-19T01:31:24Z 2021-10-19T01:31:24Z tslil clingman 2021-10-19T01:31:24Z urn:sha1:d69b55246c129ee676377117ecc621e3f7fe23da 2021-10-07T15:33:36Z tslil clingman 2021-10-07T15:25:09Z urn:sha1:d4f2376bb0ea219b79dac3f4f37b77342ca6ef4a Plus bonus graphical artefacts around the edges of such! In the end the majority of this code was rather easy: take the upwards floor drawing code and reflect it. However, there were many edge-cases and plenty of off-by-one pixels and rounding issues that didn't quite work the same way going down as they do going up. Also the object drawing code used to take advantage of the fact that the z-buffer was painted bottom-up only, so that required change too. 2021-09-10T21:05:47Z tslil clingman 2021-09-10T21:05:47Z urn:sha1:a0c7e2508df1cb0a094b9311ce90d4c25c6c31fd 2021-09-06T00:45:43Z tslil clingman 2021-09-06T00:45:43Z urn:sha1:e95d2bd264df2682f05db4a5873594af52a7583a 2021-09-05T15:43:38Z tslil clingman 2021-09-05T15:43:38Z urn:sha1:b1086c978996e522f133b4c6bdc59c95016eec0a Except that i'm not satisfied. It would appear that we're computing various distances more-or-less exactly in the sprite rendering process, but this is at odds with the walls and floors which -- by virtue of the linear interpolation garbage -- don't agree about where things are. The net result is that there are at least two fudge factors: - to account to for the incorrect height of the floors i shift the sprites up by 0.2 - to account for the incorrect wall distances i add 1 to the z_buffer comparison These fudges are ugly and empirical. Still to do: for more than one object we have to sort by distance first! 2021-09-01T19:54:03Z tslil clingman 2021-09-01T19:48:09Z urn:sha1:de255063b234871021da004d32964e25d549d3e4 Also bumped up the textures to 32x32 2021-09-01T16:59:50Z tslil clingman 2021-09-01T16:59:50Z urn:sha1:6a2d132873ce7b40405a3dc000a12539fffd969b