Configuring Static and Parallax Backgrounds

Step 2: Creating and Initializing the Parallax Manager

Create a new object inside your manager folder and name it obj_parallax_manager. It does not require an assigned sprite. In its Create Event, cache references to our background layers using layer_get_id(). This function takes the layer's string name and returns its internal memory ID, avoiding expensive string searches every frame and keeping performance optimal.

// ====================================================================
// OBJECT: obj_parallax_manager
// EVENT: Create
// PURPOSE: Cache background layer IDs and define depth scroll factors
//          for the parallax effect.
// ====================================================================

// Retrieve internal IDs for the layers created in the Room Editor
capa_cielo     = layer_get_id("Background_0_Sky");
capa_montanas  = layer_get_id("Background_1_Mountains");
capa_bosque    = layer_get_id("Background_2_Forest");

// Horizontal relative motion factors (0.0 = static with camera, 1.0 = moves with room ground)
// Lower values push layers further toward the visual horizon.
factor_cielo    = 0.95; // Moves at 5% relative speed (nearly stationary on the horizon)
factor_montanas = 0.65; // Mid-to-distant mountain range
factor_bosque   = 0.30; // Foothills and trees sitting right behind the platforms

// Initial reference values to prevent startup position snaps
cam_x_previa = 0;
cam_y_previa = 0;

Notice how the factors are structured relative to the layer's placement formula: when calling layer_x(layer, cam_x * factor), a factor of 0.95 keeps the layer anchored closely to the moving camera, producing very little relative shift (the sky appears infinitely distant). Conversely, a factor of 0.30 creates a much larger shift relative to the camera viewport, making those elements appear closer to the foreground.

Step 3: Updating Layer Positions in the Step Event

To eliminate visual stutter or tearing (commonly referred to as camera jitter), background layer updates must happen either in the Step Event (after camera calculations are complete) or in the End Step Event. Assuming your viewport tracks the player using view_camera[0], retrieve its real-time coordinates:

// ====================================================================
// OBJECT: obj_parallax_manager
// EVENT: Step (or End Step)
// PURPOSE: Synchronize background layer coordinates with the active
//          room camera's current position.
// ====================================================================

// 1. Retrieve current camera coordinates for the primary view (View 0)
var _cam_x = camera_get_view_x(view_camera[0]);
var _cam_y = camera_get_view_y(view_camera[0]);

// 2. Apply updated X positions to each registered background layer
// Verify the layer exists in the active room first to prevent runtime errors
if (layer_exists(capa_cielo)) {
    layer_x(capa_cielo, _cam_x * factor_cielo);
}

if (layer_exists(capa_montanas)) {
    layer_x(capa_montanas, _cam_x * factor_montanas);
}

if (layer_exists(capa_bosque)) {
    layer_x(capa_bosque, _cam_x * factor_bosque);
    // If the stage features prominent vertical platforming, apply Y parallax as well:
    layer_y(capa_bosque, _cam_y * 0.15);
}

In GameMaker Visual (formerly Drag and Drop), this same mechanic is accomplished by dragging 'Function Call' blocks targeting layer_x with layer variables and camera math. In GML Code, however, the implementation is concise, easy to read, and quick to fine-tune during polishing passes.

Combining Relative Parallax with Continuous Drift

One hallmark visual technique found in classic 16-bit games is combining camera-reactive parallax with autonomous atmospheric drift. For instance, having distant cloud formations drift slowly across the sky while simultaneously reacting with subtle perspective shifts as the player sprints across the level.

To achieve this mathematical blend without modifying editor properties, introduce an independent time accumulator directly inside our GML controller:

// ====================================================================
// OBJECT: obj_parallax_manager
// EVENT: Create (Addition snippet for continuous drift)
// ====================================================================

deriva_nubes = 0;        // Wind offset accumulator
velocidad_viento = 0.2;  // Pixels per frame wind moves toward the left


// ====================================================================
// OBJECT: obj_parallax_manager
// EVENT: Step (Updated snippet for drifting layers)
// ====================================================================

var _cam_x = camera_get_view_x(view_camera[0]);

// Accumulate constant wind drift over time
deriva_nubes += velocidad_viento;

// Calculate final layer position by combining camera parallax with wind offset
if (layer_exists(capa_cielo)) {
    // Subtracting the accumulator shifts clouds continuously from right to left
    layer_x(capa_cielo, (_cam_x * factor_cielo) - deriva_nubes);
}

By adding a custom accumulator (deriva_nubes), the layer retains independent motion while still responding predictably whenever the camera pans across the world.

Performance Considerations and Graphics Optimization

While Background Layers are highly optimized, careless handling of oversized assets can quickly consume video memory (VRAM) and cause framerate drops, particularly on mobile hardware or low-power handhelds. To maintain a solid 60 FPS, follow these production standards:

1. Background Sprite Dimensions: Never create a single background image spanning the entire level dimensions (e.g., a massive 10000x1080 px graphic). Instead, design a seamless looping module at 320x180, 480x270, or 640x360 px and let GameMaker tile it automatically using 'Horizontal Tile'. This reduces texture memory usage from hundreds of megabytes down to a few kilobytes.

2. Texture Groups: Inside each background sprite's properties, assign them to dedicated Texture Groups. Placing all assets for 'Forest_Level' onto their own dedicated texture page prevents GameMaker from loading unused graphics from other stages into memory.

3. Empty or Unused Layers: If an indoor room (such as a dungeon or cave) has no visible sky, disable the layer's visibility or delete it from that room entirely. Never leave hidden layers running unnecessary calculations in the background.

Practical Consolidation Exercises

Reinforce and validate these concepts by completing the following practical exercises in your project: