A while ago, I said that we'd be forking / merging / hacking existing projects to make the new engine for Entropy. A while ago, I was given a suggestion that I've decided will be the base of the new engine: Spring. Spring is a really nice RPG engine that's under GPL. You can check out their screenshots section to see what their graphics engine can do - I think it covers most of what I was looking for. The main modifications we'll be making include ensuring that it runs perfectly on any Mesa-compatible graphics card - an important "Key Goal" of Entropy. We'll also be greatly modifying the terrain engine to make it work with our planet system (specifically, making spheres out of the terrain), and probably help contribute to making it generally better (I love helping out where I can). We'll also try and remove some of the limitations that exist in the engine (if we can). Overall, I think Spring is the best choice for something to start from, as starting from scratch would be ridiculously difficult and pointless. Plus, friendly forks are in the spirit of open source programming, aren't they?
System requirements look good enough for a start. We'll of course be doing everything in our power to optimize it (I know a lot of people who know a lot of things about optimizing OpenGL code). Again, look at the screenshots - they're great.
-Bacon (Posted by: BobtheGreatII)
Woah! The Spring engine! Isn't that a RTS engine, not RPG? GL anyways!
The Spring engine is just going to be the base. We'll mess with the coding quite a bit I imagine.
wait, so can you turn an RTS engine into a FPS? or is Entropy not going to be an FPS?
We're going to heavily modify the Spring engine. Yes, Entropy is a fps, no doubt about it.