Sevgi Engine update boosts Amiga game performance with triple-buffered BOBs

The latest Sevgi Engine update is not a flashy cosmetic release. It is the kind of deep, practical improvement that matters to people actually making games: faster BOB handling, cleaner screen restoration, better memory choices and stronger editor support. Some software updates announce themselves with screenshots, new demo levels or a dramatic list of visible features. This Sevgi Engine release is different. Its biggest changes happen below the surface, in the part of an Amiga game where performance is won or lost: the rendering pipeline. For developers working with moving objects, tilemaps, back buffers and the blitter, this is the kind of update that can change how a project feels in motion. The headline feature is QuickBOBs, described as triple-buffering for BOBs. It sounds technical because it is, but the basic idea is easy to understand. Sevgi Engine is becoming better at moving software objects around the screen quickly and cleanly, without making the developer fight every detail by hand.

The main feature is QuickBOBs

On the Amiga, BOBs, or blitter objects, are one of the classic ways to animate game graphics. They give developers far more freedom than hardware sprites, but that freedom comes with work attached. A BOB has to be drawn, removed, restored and drawn again somewhere else, all while the game continues to run at a steady pace. When that process works well, the player simply sees a smooth, lively game. When it goes wrong, the player sees flicker, trails, glitches or slowdown. That is why QuickBOBs feels like an important addition rather than just another item in the changelog. It suggests that Sevgi Engine is maturing around one of the hardest parts of real Amiga game production: keeping motion clean while still respecting the limits of the machine.

The hidden art of unblitting

One of the most meaningful changes in this release is the redesigned BOB unblit system. Unblitting is not glamorous, but every smooth BOB-based Amiga game depends on it. Drawing the object is only half the job. The engine also has to repair the background when that object moves away. That background might be a tile, a platform edge, a piece of scenery or part of a larger map. If the engine restores it incorrectly, the illusion breaks immediately. Trails and corruption are small visual errors, but they can make a game feel unfinished. By redesigning the unblit implementations, this update strengthens a part of the engine that players may never think about, but developers will notice straight away.

Tileset-based restoration

A particularly smart addition is unblitting using the tileset option. In many Amiga games, the world is built from tiles. If the engine already knows which tiles make up the background, it can use that information to restore the screen after a BOB has moved. That is a practical and very Amiga-minded idea. Instead of always saving a separate copy of the background behind every moving object, the engine can rebuild the affected area from the tileset. For the right kind of game, this can reduce memory pressure and create a cleaner rendering strategy. On classic Amiga hardware, that matters because memory is never just an abstract figure. It shapes the number of objects, the size of maps, the amount of animation and sometimes the entire design of a game.

More control over memory

Another useful new option is the ability not to allocate a BOBsBackBuffer. This may sound like a small setting, but it could be a real advantage for certain projects. A dedicated back buffer can be useful, but it also consumes memory. If a game can rely on QuickBOBs or tileset-based restoration instead, that memory can be spent elsewhere. That might mean more animation frames, larger levels, extra sound data, more enemies on screen or simply a safer fit on lower-spec machines. What matters here is choice. Sevgi Engine is not forcing one rendering approach onto every project. It is giving developers more ways to tune their game around the hardware they are targeting.

Cleaner game object logic

The update also refactors game object states into flags. This is the kind of structural change that can become more valuable as a project grows. Game objects often need to be several things at once: visible, active, collidable, animated, paused, dying or triggered. Using flags makes those combinations easier to manage. It can reduce awkward state handling and make object behaviour cleaner in larger projects. For an engine that aims to help people build complete games rather than isolated technical demos, this sort of internal cleanup is important.

Better support for Tiled

The release also fixes GameObject Properties for Tiled. That matters because Tiled has become a familiar tool for many indie and retro developers, giving artists and designers a more approachable way to build maps without placing everything directly in code. A reliable connection between Tiled and the engine is important for production. When object properties do not transfer properly, level design becomes slower and more frustrating. Fixing that path makes Sevgi Engine feel more dependable as a tool for building actual game content.

The editor catches up

One of the best signs in this update is that the new features are not only hidden in the engine. Options for the new systems have also been added to the Sevgi Editor. That matters because tools shape how people work. A feature buried in source code is useful to experienced programmers. A feature exposed in the editor becomes part of the normal development flow. By adding editor options for QuickBOBs, unblitting choices and related systems, Sevgi Engine makes these improvements easier to discover, test and use.

Smaller fixes with real impact

The changelog also includes several practical fixes that should make development smoother. The non-interleaved BOB sheet check has been corrected, which helps with asset validation and BOB sheet handling. Requesters that could get stuck in DoSaveMode have been fixed, removing the kind of workflow bug that can quickly become irritating during repeated saves and edits. The template games have also been updated to reflect the new systems. That is especially welcome because templates are often the first place new users look when trying to understand an engine’s preferred way of working. Documentation has been refreshed too, which is essential for features like QuickBOBs and tileset-based unblitting. Technical power is only useful when developers can understand how and when to apply it.

Why this update matters

The bigger story here is not just QuickBOBs. It is maturity. Sevgi Engine is moving deeper into the real problems of Amiga game development, beyond simply loading assets, generating a project or opening an editor window. This release focuses on the difficult, important business of moving objects on screen at speed while keeping memory use under control. That is where Amiga development becomes interesting, and also where it becomes difficult. With this release, Sevgi Engine gives developers more choices. They can use QuickBOBs, rethink unblitting, restore from tilesets, skip a BOB back buffer when it makes sense, manage object states more flexibly and access more of these decisions through the editor. That is not a cosmetic update. That is an engine becoming more useful.

Verdict

Sevgi Engine’s latest update may not look spectacular from the outside, but for Amiga developers it is a meaningful step forward. The introduction of QuickBOBs gives the release its headline, while the redesigned unblitting system, tileset-based restoration and optional back-buffer allocation give it real substance. Add improved Tiled support, updated templates, refreshed documentation and editor integration, and this becomes a focused, practical release shaped around real development needs. For coders, it means more control. For designers, it means a smoother workflow. For players, the result should be simple: better-moving Amiga games. The headline is QuickBOBs. The story is confidence.

Spread the love