Tag: vulkan

Hide portals (doors/windows) when the surrounding wall piece is hidden

The portal saga continues – but we are getting closer to the end of it. While at first glance the portals and the surrounding walls are a unit they are actually drawn very differently, as the portals themselves are actually models, while the wall pieces are geometry which is calculated programmatically.
This distinction requires a special solution to determine when portals need to be hidden. Luckily, the code that determines whether a given wall piece needs to be drawn lowered could be refactored and re-used, getting the information into the shaders was slightly more tricky, but it got there in the end. Check it out below! 🙂

Add diagonal movement

This improves the navigation by adding diagonal movement, which seems a lot more natural:

Make sure to always rotate in the right direction

If you remember some of the earlier videos, sometimes the characters would rotate in the wrong direction, which seems even more odd now that animations work. Let’s fix this:

– Add functions to more comfortably change animations on objects
– Automatically switch to a walking state for moving objects. Set the  idle state when the destination is reached.

This makes it possible to quickly change the animation on the fly. Also, changing the animations like this makes the movement seem a lot more natural.

– Resolve deadlock when changing resolutions
– Very minor optimisation: pre-calculate what is essentially a static value

This is a recurring issue, once again fixed in its most current iteration.

Only re-calculate animation states after at least 20ms have passed

Do not eat up all the CPU. Or at least not as much.

– add mapping from animation name to index
– undo accidental renaming of the model class cpp file
– reformat the build targets in the CMakeFile

Specifying indices is not as much fun as just using the animations human readable name.

Add missing file, remove dead code and fix the usage of more than just the first animation in a file

So far only the first animation was used – that also meant that the offset to anything that is not the first animation was not calculated properly.

First working version of the model transformations

After two very demanding months, a lot of debugging and trying many, man things, it is working:

More animation progress

This included a lot of research and trial and error. How well this is going is best illustrated by the following screenshot: