Raycasting demo

[artrag]

What about adding SW sprites now?

[JohnPCAE]

I've started thinking about how to do it, but in the meantime here's the slidey-slidey update. Now if you run into a wall you'll slide along it instead of just stopping. This would have been a necessary feature regardless.

raycast_20200406.zip

[JohnPCAE]

raycast_20200407.zip

 

Fixed a crash that arises if you lower the maximum view distance. Added support for different ceiling and floor colors, and added support for dithering the walls.

[JohnPCAE]

raycast_20200413.zip

 

I found that simply changing some constants allows me to dither the wall or ceiling, so that allows some more variation. I've also increased the unit height of walls from 8 to 36 (the height when the wall is exactly one unit away from the viewer). This makes walls appear square, which makes them look a lot better when dithered. It would also be necessary if/when I add texture mapping. Also managed to eke out a little more speed from the engine to try to make up for the overhead from dithering. Getting more speed is important since texture mapping would add even more overhead.

[artrag]

With dithering everything looks more interesting, speed and smoothness are excellent too

Greetings!

[JohnPCAE]

raycast_20200418.zip

Reworked a lot of code and made many speed improvements to the colored-squares version.

[JohnPCAE]

I was thinking about artag's DDA algorithm posts and something finally clicked. I decided to take another whack at it, and the result is fantastic. No more missing areas at corners, the code is tiny, simple, and maybe twice as fast!

 

raycast_20200419.zip

[artrag]

Incredible how fast it is

Awesome!

[artrag]

John, about sprites, how do you plan to implement scaling and clipping ?

The most effective way (from the visual point of view) would be to use MOB for far distance and software sprites for close distance.

But this would be also the most clumsy and expansive way to implement sprites.

Essentially you should develop two engine to manage sprites...  

 

Probably the simplest thing to do is to start with the SW sprite engine

For each sprite frame, I would store pre-computed data in rom for all scales and the four pixel alignments (in color square mode).  

In this way one could build four fast column renderers able to mix data from the walls and from the selected scale of the sprite frame   

 

[artrag]

John, just an idea, why not developing an intybasic front end for your raycaster?

Intybasic can embed ASM routines and share variables between the two environments 

It could allow other people to implement 3D games using your library 

[JohnPCAE]

I've started looking at the Wolfenstein 3D source to try to understand how software sprites are done. It seems to be computationally expensive so keeping it fast will be tricky. I also looked at a ton of Wolf3D gameplay videos to understand what features are desirable. First I think I need to try to squeeze as much speed out of this new implementation as I can.

[JohnPCAE]

raycast_20200614.zip

 

Many, many speed improvements to the CS version. With some more changes, this could eventually support larger maps. For instance, Wolf3d maps are 64x64 in size.

[JohnPCAE]

Been sitting on this for a while. The movement logic had some bugs that would let you walk through walls under certain circumstances. This fixes those bugs.

 

raycast_20200709.zip

[First Spear]

On 8/14/2020 at 2:25 PM, JohnPCAE said:

Been sitting on this for a while. The movement logic had some bugs that would let you walk through walls under certain circumstances. This fixes those bugs.

 

raycast_20200709.zip 87.8 kB · 35 downloads

Hi. Have you had a chance to look at this further, maybe incorporating @artrag's ideas?