I thought the longest, well known game was Dwarf Fortress and had no contenders but I guess I'm wrong. I've never really used a review to buy a game. I go off of LP's, trailers, and the opinions of those who don't run a review site for a living ;)
TigSource(the homepage) gives some good reviews. I don't really like the forums though, because some of the boards tend to be filled with derailers, and common circle jerk.
Yeah, I mostly avoid gaming forums completely because the community at large is awful. Indie forums tend to be better, but it's still a lot of work to keep on top of everything.
The exception is IndieGameStand, where I am a forum moderator.
I think I snagged Pid a while back. I think it was free at one point in time. Shelter looks like an amazing game. I remember reading about it when it was about to release. I love the art style. Nice low-poly look.
The problem with TigSource is that the forum-moderators don't encourage on-topic conversation enough. They will actually participate in the circle jerk themselves. It's not just for gamers but developers as well.
The problem
The problem lies in your method of collision resolution. Your method goes as follows:
Move the player.
Check for collision.
Determine the shortest collision depth.
Resolve collision.
The problem with this, is that it can easily move the player in the wrong direction. You can see ...
If the movement is free (like flying without gravity, like asteroids game) then the prioritising the axis might work better. But if the game is platformer with constant gravity pulling down, then it might be better to prioritize to Y axis first and check collision to the ground, and only after that obstacles that the player can't walk thru x-axis
after last night and today, my body is actually so excited to process an avocado, that the pleasure is so intense it's painful like a non-consensual tickle when it hits the bottom of my gut
Yeah totally nerd friendly, except when I have to clear all of them out because they have fucking negative game and actively cockblock from rooms away just by sitting still
Well I've got to crash out, have a wonderful existence humans! :)
Vertex shaders make the necessary transformations from model-space to view-space to screen-space so that the rasterizer can rasterize the fragments, and then the fragment shader is applied on each fragment produced by the rasterizer.
This chat is always here, the question section isn't that friendly on beginner questions though so I recommend some place like gamedev.net for any kind of forum questions you have.
I recently got to the point where, I learned so much during my 6 months of no access to a computer that I could program on, that I don't start any new projects because it takes so much work to make the "clean" engine I have in mind.
It sucks, I have some great ideas I just can't wait to code, but I don't want to put in the tremendous time into making an over-engineered engine (which is what I want to do, as a learning experience).
I put clean in quotes because it is clean to my current standards, but in a year I'll look back and say "Wow, I could have done this so much better." At least I better! Otherwise it'll mean I haven't learned anything :)
I had the render() and update() and initialize() and I put some vertex array initialization there and got something on screen, and thought "well, I can abstract this"
I want to make it have a good debugger with info overlays and such
2D
So it won't be as hard as the 3D engine you're making
But I've learned so much about certain things
Like time management, abstracting libraries/APIs, various little things...
It's crazy
I went without internet for 6 months
So whenever I got a chance I'd go down to the store with a little laptop we have and download a ton of articles on programming and game engine architecture
To give people a little boost up, share the loads of info I found over those 6 months in a big project. Will be in the future, but it should help some people :)
Eh, once you get to a certain point with engines that have no game in mind, it kind of just gets dropped. You learn enough from the project to improve with the next one. :)
You can pick something that is only a fraction of what is needed for a game and follow the rabbit hole for months, constantly learning more efficient ways to do new things with it.
Engine architecture is my fire when it comes to programming, the idea of abstracting everything and making it clean and easy to work with just fascinates me
The problem
The problem lies in your method of collision resolution. Your method goes as follows:
Move the player.
Check for collision.
Determine the shortest collision depth.
Resolve collision.
The problem with this, is that it can easily move the player in the wrong direction. You can see ...
