Jasoco wrote:I've been trying to figure out how to do that for years. That point is always behind the camera. So it gets calculated as being inverted and on the screen in a weird location, which causes the polygon it belongs to to become a "backface" which then results in it being excluded from rendering (Which is what is being seen here.) The only way I've found to bypass it is as I mentioned, by either adjusting the camera location or making the tiles smaller. Either way is going to screw things up a bit. I wish there was a way to somehow figure out where that point should be for reals. Possibly using super amazing maths. Maybe someone on this forum can figure it out.
What we need is a shader that does this for us using a reference image. (Which would be a canvas with all the floor textures on it or something.) It'd probably be more efficient too. No idea how though.
I did it! It's complete, it's perfect! I kinda fixed the wall collisions.
The way I did it was to generate 4 corner images automatically (that was fun) for each tile and in case of a tile not drawing, I would check for the four corners and draw them.
Too jarring. I'd say just stick to normal sprites with 8 directions. It would look too weird in action. Do you have a demo with it implemented? Maybe it might look better in action.
Alright guys, I redid the sprite system. That took way too long than it should have. I also re-implemented head-tilt as I redid the floors.
What do you think? Better?
PM me on here or elsewhere if you'd like to discuss porting your game to Nintendo Switch via mazette! personal page and a raycaster
When you going to put in a ceiling though? The sky doesn't really make sense and I only really put it in my engine because I was too lazy at the time to code the opposite of floor code for it.
