Author: s20

enforce the right texture sizes when loading tile data and make the tile manager a little less verbose

That is what it does, but it also adds the beginnings of the wall (as in the vertical counter-parts to floor tiles) book-keeping code (no renderer code yet) to the Floor class. What that means is more detailed are functions for getting vertex data (non-functional), calculating a wall state hash and references to the yet almost empty WallManager.
The wisdom of this is more than questionable and it will in all likelihood get moved elsewhere.

WiP approach to get real y values for objects on non-even planes

Tries to do a better job at determing good elevation for objects that cross non-even planes (tiles).

show tile borders when pressing v. implemented using push constants.

Once again, comes as advertised.

add floor tile type state hash

Now that we actually have more than one tile type make sure the renderer knows when to update things.

render objects centred around the middle of a tile, not at its corner

That makes it look a lot less weird.

actually render different floor tile types

This completes the support of multiple tile types. Let there be floor.

remove debugging output and do no longer access indices that corrupt the heap

Once again, this one comes as advertised.

   – clean ups
   – begin support for rendering of different tile types (WiP)
   – add some temporary debugging output

Starts support for drawing multiple floor tile types, this also means starting support for concatenating floor textures into one and upload it to the GPU as a sprite.

…and it initialise the state hashes properly.

– move to smart pointers wherever reasonably possible
– initialise member variables in class defintions where reasonably possible
– use a crude way to actually render object elevations properly
– take the elevation back into consideration when drawing the floor

This adds a whole bunch of shared_ptrs. A lot.
Brings back the height element when drawing the floor (and its height map).