Ramblings about hobbyist game development
add visual feedback when hovering over build markers
Now as soon as the user hovers over build markers they become taller to indicate which one is currently active. This required changes from the shaders to the hash calculation functions, but was definitely well worth it:
add a further check (for walls in the way) for the building marker start points
Some cases were not covered yet, now they are!
– move some static value to proper class members as opposed to defines
– move the render pass creation to the util class
– do not use depth testing when drawing the build markers (they’re always on top as they need to be seen)
– more tests about where to put valid build markers (do not build over existing walls or objects)
Another step to making the renderer less horrible.
Also, we now get more sensible potential positions for the build markers (2nd step), before that we would just place them everywhere.
This video demonstrates the new logic as well as the A* path finding .
add more mutex locks to fix a race condition
It seems to be the solution to many problems.
initial wall building support
Mostly wires up the code from the previous commits and adds the logic for first selecting a starting point and then a target for a new wall.
But maybe a short videos says it better: