vjiaoblack / terrain-gen Goto Github PK

Or alternatively, decide what framework to use.

With a good way to store them and such.

I really don't want to use an external framework /just/ for this, so I'll have to create a decent UI system.

That may require some basic screen-space physics or collision testing for now, but we'll see!

The main image is from early in development. It looks way nicer now! This should totally reflect that.

A gif displaying the water sim might be nice too!

Instructions that are current might also look good.

Hi there, just wondering if you guys are still working on Athena. Looks great!

Information from from the Google Doc currently linked in the README (https://docs.google.com/document/d/1xySCdTcphTbBVFzzvw51X8ISexEsv2MM4zNanQW6Hbc/edit) would be a great start for some in-repo documentation!

Since we're working with pixels, mostly, it has been fine so far to just use a pixel grid for everything - color, height, water level...

But if we are to move towards more advanced rendering or simulation techniques, we need to have a consistent way to index into the data (instead of just copy-pasting bilinear interpolation everywhere). Drawing inspiration from CMSC 23710 @ UChicago, I can create a system that uses preset kernels to index into the data and generate estimates of data values at non-integer coordinates.

This will let us simulate day-night cycles! It'll probably look really cool.

Come on man.

There's unregulated TODOs everywhere, and variable naming etc. isn't super great...
Should the TrGame instructor have all the SDL init code /within/ it, or should the SDL init code be separate?

Good (or at least consistent) code style is vital for the efficient continuation of any software development project, so let's fix it.