So I tried my hand at raycasting(at least what I think it is, not sure) and it did not go well. I need help.



Note that to see how bad it is messed up you should probably try it.

http://www.mediafire.com/?m9hhj5wdh05k3rs Here is a link to the C# file.

I am new to this. What is aspect ratio?

Also, I looked it up and it is called the "fishbowl effect". Here is an Image explaining it. I got it from This: http://www.permadi.com/tutorial/raycast/rayc8.html#FINDING DISTANCE TO WALLS



However when I try to fix it this happens:

It really is not natural, if you download the program it looks awful. Also I use 40 degrees.

OK, but it looks bad.

No, the fishbowl effect is not natural. A straight line in 3D space should always be a straight line in a 2D perspective projection - look at a photograph of a building for example.

Fishbowl is caused by computing the ray vectors the wrong way. Right now you've got rays evenly spaced by angle, like the left side of the diagram below. There are two problems with this. The first, which has already been mentioned, is the since the rays are all the same length, the rays at more extreme angles take longer to get to the wall. The more subtle problem is that the rays don't hit the wall at evenly spaced points; the rays on the left and right sides hit the wall further apart than the rays in the center.

The right way to do raycasting is to imagine the game window as a literal window into your world: you want to make the player see what the in-game camera sees. Monitors are flat, not curved; as such the columns on the player's monitor are spaced a constant linear distance apart, not a constant angle apart, and the rays should be computed accordingly, like the right side of the diagram. (Edit: A simple way to compute each ray is to add the camera direction to a multiple of its perpendicular. Ranging the multiplier from -0.5 to +0.5 will produce a 60-degree field of view.)

This program actually has another problem: distance isn't translated to line height properly. The perceived height should be inversely proportional to the distance, i.e. a constant divided by the number of ray iterations, not subtracted.

Looking better, can you explain how to make the rays hit the wall at evenly spaced points?

Here is a picture of how it looks now! Thanks.

There is not hit collision if that's what you mean. You walk into blocks.

why are you trying to compensate for that effect? it is natural for it to be there, so removing it will make your program look less natural. you may have to adjust the angular width or the total horizontal space you can see at once, though. one that's used a lot is 60 degrees.

For some reasons, I don't think I have noticed any FPS for the computer with that effect , or maybe it's due to the fact that every FPS I played were made back in the days where computer screens were not flat. Also when I take pictures with my camera walls always look like figure 18