echinopsis posted:

dont post

theadder posted:

Doc Block posted:

You have to keep track of which direction you're casting the ray in relative to the world. If the ray was going left and up when it hit then round both X and Y down to get the correct tile coordinates. If it was going right and up, then round X up and Y down. If it was going left and down then round X down and Y up. If the ray was going right and down, round both X and Y up.

I don't know how this particular ray caster does it, but a lot of raycasters used in actual games cast two rays for each vertical slice. One that only checks for intersections with vertical walls, and one that only checks for intersections with horizontal walls. Then compare the distance and choose whichever one is closer. Makes the code easier when deciding whether or not to round up or down, and there are some other benefits but I forget what they are.

This link and this one were pretty much considered to be the on-line resources for info about writing ray casting engines back when I was playing around and wrote one.

computer toucher posted:

hows my spare time project doing? glad you asked! https://kyber.ninja is looking a lot better. I've spent some (tens of) hours on it and finally fixed the horrible database I first made, improved a lot of stuff and have been gathering the latest relevant news to the site to have content. it's waiting to be bumrushed by hundreds of active users any minute now!. it also got some more memory and a new free "home" behind cloudflare. thanks cloudflare!

It might be a piece of poo poo php/bootstrap forum but at least it's mine!

echinopsis posted:

what is it and should i be an admin

echinopsis posted:

nothing

Doc Block posted:

LOL I tried to download PyGame so I could help out Luigy Thirty (he rewrote the article's raycaster in Python) and the PyGame website is not only eye-gougingly ugly, the whole site is broken as gently caress. There isn't a single download that's post-2010. Welp.

Luigi Thirty posted:

hmm, well I know the angle that the ray was cast at and I know whether my intersection is vertical or horizontal (X or Y is always a whole number) but it doesn't seem to be adding up. a ray moving at an angle of 234 degrees should be going left and down (I pointed my player in that direction and went forward and that's what happened to my coordinates) but flooring x and ceiling y doesn't give me a valid tile and it draws Tazz. I set up the whole set:

code:

				ray_angle = math.degrees(rotation + angle) #the ray is cast at (player.rotation+angle)

				if(ray_angle >= 0 and ray_angle < 90):
					texture = tilemap.tilemap[int(math.ceil(step.x))][int(math.floor(step.y))].texture
				elif(ray_angle >= 90 and ray_angle < 180):
					texture = tilemap.tilemap[int(math.floor(step.x))][int(math.floor(step.y))].texture
				elif(ray_angle >= 180 and ray_angle < 270):
					texture = tilemap.tilemap[int(math.floor(step.x))][int(math.ceil(step.y))].texture
				elif(ray_angle >= 270 and ray_angle <= 360):
					texture = tilemap.tilemap[int(math.ceil(step.x))][int(math.ceil(step.y))].texture
				else:
					raise AttributeError("ray_angle invalid: " + str(ray_angle))

				if texture is None:
					texture = Image(IMAGES["texture_tazz"])
				else:
					True
					pass

but it keeps trying to figure out angles over 360 degrees and under 0 degrees? and the texture will flip to Tazz on random columns when my angle to them changes? something's hosed up. uh, also the geometry makes no sense to me because i have one of those math learning disorders so i don't know what it's doing to cause that. i think my coordinate system is rotated or something as well but i don't know how to fix that

graphics are hard

Doc Block posted:

What the code should do is just have the raycaster return the X and Y of the block it hit, so you don't have the big if-else statement checking the angle of the ray. Especially since for some cases it won't ever be right.

Doc Block posted:

Reading through your Python code, it seems you are casting two separate rays or some poo poo, IDK. I hate "Pythonic" code, it's always so unclear.

echinopsis posted:

curious why is pythonic code so unclear to you when pythonic code means basically clarity

Trig Discipline posted:

well isn't that pythonic? don't you think?
a little too pythonic?

Jonny 290 posted:

still dont get lambdas at allllll

Doc Block posted:

since when? when i was learning python a few years ago pythonic basically meant "the clever solution" and all "pythonic" code that i saw was full of lambdas and maps and poo poo when there didn't need to be.

quote:

To be Pythonic is to use the Python constructs and datastructures with clean, readable idioms. It is Pythonic is to exploit dynamic typing for instance, and it's definitely not Pythonic to introduce static-type style verbosity into the picture where not needed. To be Pythonic is to avoid surprising experienced Python programmers with unfamiliar ways to accomplish a task.

Jonny 290 posted:

still dont get lambdas at allllll

echinopsis posted:

since forever man. go read

pythonic means "not clever".

http://blog.startifact.com/posts/older/what-is-pythonic.html
tjats from 2005


pythonic means it should be very clear. python by itself makes this easy coz python is the best and is very easy to read and understand