Spite

November 22, 2019

Trailer

Details

• 3D Top Down RPG
• 10 Weeks Part-Time
• Made in our own DirectX11 based C++ engine

Contributions

• Synced Based Threading - Early in the project I got the task of multi-threading our rendering and logic work. I wanted to make this generalized and expandable, so I created a way of defining thread work and sync work. In this case, the sync work would execute double buffer flips for render commands or even other types of data. Both thread work and sync work could be nestled, which gives the potential of creating big “thread trees” if the user wishes. I had plans to even integrate this into our Component System, where you could easily define a thread tree which is based on which dependencies each component have. Unfortunately, this is not something I had time to implement at the end, but it’s something that I’d like to revisit in the near future.

• Node Editor Implementation - An in-engine ImGui-based node graph editor for creating level scripts (one script that runs on a single level), based on the node-editor we got from the scripting course.

• Event Node Interfacer - A method to expose events to the node system, where the user of the node editor could both register flows on receiving an event, and trigger an event. Exposing an Event was as easy as registering the event in a variadic templated class as seen here:

  NodeEventInterface::GetInstance().ExposeEvents
  <
        Event::EmitterSlotRefresh,
        Event::FreeCamOff,
        Event::FadeIn,
        Event::FadeOut,
        Event::NoFade,
        Event::AllFade,
        Event::Interacted,
        Event::FlashlightTurnedOn,
        Event::FlashlightTurnedOff,
        Event::WalkieTalkieTurnedOn,
        Event::WalkieTalkieTurnedOff,
        Event::WalkieTalkieBreak,
        Event::GameOver,
        Event::FlashlightPickedUp,
        Event::PlayerCanSprint,
        Event::StartRiser
  >();
  

• Enemy AI - Wrote the base state-machine that controls the AI, and the enemy AI’s behaviour, which includes its movement, attacks, animation states and other response behaviours to the players attacks.

• Boss AI - Wrote the behaviour for the final boss based on the state-machine I mentioned earlier. States includes melee attack, fire attack, and transitional states between different phases.

Screenshots