My Roles

  • Technical Designer
  • Camera/Controls Programmer
  • Character Animations
  • Co Project Management

  • DOWNLOAD NIMBUS Download Nimbus (480mb)

    * For best experience, play using a gamepad controller

    A 2.5D sidescrolling platformer about an inventor named Griff Zochran. He must navigate the machinery inside the airship Nimbus, in order to finaly bring it to an end. Its Mechanical crew have set course to bomb the metropolis of Emery City. Griff is their last hope, but will he survive his objective?

    Griff has a Machine Control ability that allows the player to move and rotate the platforms typical of the platformer genre.


    Design Notes

  • Made in UDK (Unreal Development Kit)
  • 4 Month Dev Time
  • 4 Man Team
  • 5 LVLs (+45 challenges)
  • 10 to 20 Minutes of Gameplay
  • The Team

  • Jason Dreger
        Level Design, Kismet Logic, Front End Design
  • Justin Nichols
        Level Design, Puzzle Design, Character Design.
  • Christopher Pesce
        Cinematics, 3D modeling, Technical Artist.
  • Top >>



    The Camera System

    Nimbus features a Dynamic Sidescrolling Camera.

    The Nimbus Camera has functionality to accept predetermined settings in the game world, and smoothly transition to those new settings around the player.

    The camera logic was implemented in Unrealscript. Functionality was exposed into the UDK Editor through Kismet. This gave Level Designers the power to control what the player sees.

    Trigger volumes were created in the game world to track the player's position in the level, and the camera logic would dictate the camera's behavior in code.



    Case Study:

    The following is a short example of how level designers can readjust the camera's behavior in the UDK Editor using the Nimbus Dynamic Camera without having to deal with scripting:


    Camera-01

    1) This is a typical view in the Nimbus game. The entire room is encompassed by one Camera Volume that is preset to the values that result in this screenshot. But one issue arises when the player jumps down to the platform below them.

    Camera-02

    2) A foreground element blocks this area of the room when the player jumps down. The current settings for the camera is insufficient.

    Camera-03

    3) In the UDK Editor, we can select the volume that is influencing the camera. In the image, the foreground element is blocking the platform the player lands on.

    Camera-04

    4) Raise the bottom floor of the volume to a level where the player will not interact with it when he jumps down.

    Camera-05

    5) Create a new volume that encompasses the lower platform. This new volume will hold new camera settings.

    Camera-06

    6) In Kismet, create a new Touch Trigger node and a CameraSetting node. The values for the CameraSetting node were taken from the older volume.

    Camera-07

    7) The result is that the camera will automatically readjust now when the player jumps down to the lower platform, framing the character and platform he's standing on.

    Top >>

    Postmortem

    What went right

    Flexibility of cutting back scope in one area to support a different area

    "As [one] area of the game was falling behind, scope was cut from another, more complete portion of the game so as to free up a team member to aid in the player character. In the end, the combined effort to strengthen the quality of the character model paid off."


    What went wrong

    Pacing Crunch

    "...the entire team often stayed even later than the core hours to keep working on the game. This contributed to a lot of Nimbus' success, but was also wearing everybody down in post-Beta."


    Download Full Postmortem

        Download DOC     Download PDF


    Top >>



    The Character Controls

    The character in Nimbus features an Analog Jump, where the height of the jump is determined by the duration in which the Jump Button is held down for. This was a simple mechanic implemented to give players more control and flexibility over the platforming, and increase the sense of mastery.
    It was important to make the platforming feel natural and responsive in the game, as that was the most frequent action players would be doing. So a lot of time was spent tuning the Jump Profile. Telemetry Data was also used to analyze the effects of various values, and communicate to the team which goalpost values were the most desired.

    Nimbus Jump Data
    Screenshot of Telemetry Data used to tune the jump values.

    Top >>



    Screenshots

    Nimbus-01 Nimbus-02 Nimbus-03 Nimbus-04

    Top >>



    System Requirements

    Minimum

  • Operating System: Windows XP SP2, Windows Vista
  • Processor: 2.0+ GHz processor
  • Memory: 2 GB system RAM
  • Video: SM3-compatible video card
  • Hard Disk Space: 500 MB free hard drive space
  • Recommended

  • Operating System: Windows 7, 64
  • Processor: 2.0+ GHz multi-core processor
  • Memory: 8 GB system RAM
  • Video: NVIDIA 8000 series or higher graphics card
  • Hard Disk Space: 1 GB free hard drive space
  • Top >>