Skip to main content

Gameplay Mechanics 2 - The Red Beacon

This explains the bring mechanic. You need 1 dynamic object. 


Aim and fire the red beacon at the dynamic object.


If the red beacon hits a dynamic object, it will become marked, just like the blue beacon. Similarly, nothing will be marked if you hit a wall. One object can be marked at a time. 


Now, with the object marked, you can summon it under you. Even if the red object moves, it will still be marked. You can use this ability to place cubes where you want them (for example on a door switch, above an enemy...) You  could also build stacks of objects quickly(we will see this in detail in part 3). 




Comments

Popular posts from this blog

Painterly Shader with GLSL

Besides all the regular fancy shaders you would normally find (reflections, normal mapping...) the demo features one advanced fullscreen shader to produce the painterly effect. Its different from the usual cel-shading techniques because it doesn't rely on silhouettes or a different lighting model to produce the effect. Instead, the shader utilizes a brush pass ( the scene re-rendered with a brush texture applied to everything) and the depth pass, alongsde the main color pass to distort the image in a specific way. The brush pass is used to define the  magnitude  of the distortion, and some math applied to the depth pass to define the  direction  of the distortion. Its useful to note that the main color pass is rendered completely normally, the lighting is baked from Maya into the textures, and shaders are applied normally for reflections and normal mapping. Below are screenshots of the passes with a brief explanation of how it works. 1.  The brush pass. The color v

Q - PC Build

Q started out as a PC game. It was controlled with a mouse only, and you used it to connect nodes on the spell pad. We were only getting started with UDK, but we managed to get a look, feel, and some controls for a small demo. It relied heavily on post processing effects, cloth simulation, and real time accurate reflections. When we later moved to iPads, none of those features became viable, and the visual had to change drastically. It looked like this:

Physics

My demo uses the amazing (and opensource) BOX2D physics engine for C++. You can check it out at: http://box2d.org/ The gameplay involves a lot of discontinuity in the physics due to all the teleportation (character teleporting into objects, objects that teleport into spaces that dont fit them...), and BOX2D handled the resolution of these unstable states very well. In fact very little extra programming was required for the engine to reach a very stable steady state.  What the BOX2D test bed looks like.