this happens when you switch tools without hitting b after copying. if you have the copy stuck on screen you can use the fill tool anywhere to get rid of it. just fill an area with the clear color and the glitch will stop.

raytracing is slower than raycasting because you shoot a ray to every pixel on screen 400x240 pixels is 96000 pixels but gives a better image because raycasting only shoots rays equal to the horizon(which is 400 because it is the length of the screen. raytracing produces shading and a better image. I dont think raycasting can produce shaded walls,floors and ceilings.

you put an o instead of a zero at if I then spofs o,x,y right here ^

calc84 is already making one and its awesome i think he will release it soon, go check it out on his miiverse acount: Calc84

try this website for help http://permadi.com/1996/05/ray-casting-tutorial-table-of-contents/

if the ray that you cast hits a wall then draw the vertical line

something like this: for rayangle=cameraangle-fov/2 to cameraang+fov/2 step fov/horizon ' this is where you cast rays ' if you hit a wall draw a vertical line with a height according to the distance of the wall from you(the length of the ray) next

raycasting is where you scan each column of pixels on the x axis for a wall and if you find a wall, draw the walls height for that column according to distance away from you. so you cast 400 rays because that is the amount of pixels on the x dimension on screen. the screen width is 400x240. the fov is how big your viewing angle is usually 60 or 66 degrees and horizon is the width of the screen.

i tried raycast but i could not get rid of the "fish eye" view. ill just let calc84 make one and use that.