Softwarekatalog > Spieleentwicklung > LAB Engine
Communityhub
LAB Engine
An open, hackable Vulkan game engine with a deferred PBR renderer, optional hardware ray tracing, an ECS scene editor, Jolt physics, and Lua + visual scripting built solo, in Early Access, with the roadmap and known issues public from day one.
Veröffentlichung:
Bevorstehende Ankündigung
Entwickler:
Publisher:
Mihajlo Ciric

Melden Sie sich an, um dieses Produkt zu Ihrer Wunschliste hinzuzufügen, zu abonnieren oder als „Ignoriert“ zu markieren.

Funktionen
Sprachen:
Oberfläche Ton Untertitel
Deutsch Nicht unterstützt
Englisch ✔

Early Access-Software

Bringen Sie sich in die Entwicklung ein.

Hinweis: Diese Early Access-Software ist noch nicht fertig und könnte sich in Zukunft verändern. Wenn Ihnen die Software im aktuellen Zustand nicht gefällt, sollten Sie abwarten und sehen, ob sich die Software weiterentwickelt. Mehr erfahren

Was die Entwickler zu sagen haben:

Wozu Early Access?

„LAB Engine is a solo-developed renderer and editor with a large, genuinely useful core
already working deferred PBR rendering, optional hardware ray tracing with automatic
fallback, an ECS scene editor, physics, and two scripting paths. But several pieces that
matter for day-to-day use are still open: glTF import (today's mesh path is OBJ-only and
ignores materials), a finished node-based material editor (in progress), async asset
loading, and native file dialogs among them. Early Access means real projects can push on
the engine while those land, instead of everything being decided in isolation before a
single outside user has touched it.“

Wie lange wird diese Software ungefähr den Early Access-Status haben?

„Roughly one year, I'm aiming at a full v1 realease in end of 2027. Development is active and ongoing, as a solo developer working on the project part time it will take a bit of time. Unless I manage to work on this full time.“

Wie soll sich die Vollversion von der Early Access-Version unterscheiden?

„glTF 2.0 import with full PBR material support, replacing the current OBJ-only path
A finished node-based material graph editor (already rendering live on a development / compilation and live preview work; the node library and editor
polish are what's left)
Async asset loading off the main thread, so large scenes don't block the editor UI
A real linear/sRGB color pipeline (built, currently switched off pending scene
Character controllers, joints and constraints in physics
Native file dialogs, replacing today's typed-path New/Open Project flow
A wider Lua/visual-scripting API surface (physics forces, material color, entity
spawning, parenting, a proper quaternion type)
and much more “

Was ist der derzeitige Stand der Early Access-Version?

„Working today: the full editor (scene hierarchy, properties, asset browser, gizmos,
undo/redo), the deferred renderer with optional ray tracing and DDGI, Jolt-based physics
with collider gizmos and raycasting, Lua and visual scripting with collision callbacks,
projects with standalone Build > Build Standalone packaging, and a performance/profiling
panel. [ 24 automated tests currently cover shadows, physics, scripting, selection and
serialization, run against a real Vulkan device each time. ]

Not yet built: glTF import (OBJ only today), a finished material graph editor (in
progress), async loading, native file dialogs, character controllers/joints, and script
hot-reload. The public roadmap (docs/ROADMAP.md in the repository) lists these in the
order they're being tackled.“

Wird diese Software während und nach Early Access unterschiedlich viel kosten?

„We plan to gradually raise the price as we ship new content and features. But might be to early to tell
We might start free to play in the beginning, or a symbolic small price“

Wie werden Sie versuchen die Community in den Entwicklungsprozess miteinzubeziehen?

„The roadmap and known-issues list are public in the GitHub repository.
I will be active on a dedicated Discord Server and will involve community in voting for the next features to add and/or improve. As well as organizing Events like Game Jams and Plugin Hackathons that involve the community directly“
Weiterlesen
Dieses Spiel ist noch nicht auf Steam verfügbar

Geplantes Veröffentlichungsdatum: Bevorstehende Ankündigung

Interesse? Fügen Sie das Spiel Ihrer Wunschliste hinzu und erhalten Sie eine Benachrichtigung, wenn es verfügbar ist.
 

In den Diskussionsforen können Sie Fehler melden und Feedback zur Software abgeben

Alle Diskussionen anzeigen

Über diese Software

LAB Engine is a Vulkan deferred renderer and scene editor, developed solo and in the open.

This is Early Access because LAB is being built the way its own documentation is written in public, with the known problems listed next to the finished features, not after them.
What you get today is a real, working editor: you can drop in a mesh, light a scene, tune materials, script behavior, hit Play, and package a standalone build that runs without the editor. What's still being built is listed below, and it stays updated as things land.

What's in the engine today

  • Deferred PBR renderer : a render graph that declares each pass's reads andwrites and generates the barriers between them. Cook-Torrance lighting (GGX, Smith,Schlick), directional/point/spot lights with a clustered light grid, and shadow mappingfor every light type including cascaded sun shadows.

  • Hardware ray tracing : optional, never required. Traced sun shadows, ambientocclusion, reflections, and ReSTIR global illumination, behind an NRD-style denoiser. On aGPU without ray query support, every one of these has a raster fallback that looks rightwithout the scene needing to change.

  • Dynamic global illumination via DDGI probe volumes — traced on the GPU whereray query is available, on the CPU where it isn't.

  • An ECS scene (EnTT-backed) with a YAML scene format, transform gizmos, multi-select, undo/redo, and prefabs (.Lobj objects) with instance refresh.

  • Jolt Physics : box/sphere/capsule/mesh colliders, static/dynamic/kinematic bodies, raycasting, and collision callbacks reaching scripts.

  • Two ways to script: Lua 5.4 text scripts, or a visual node graph that compiles down to the same Lua, inspect the generated code any time.

  • Projects and standalone builds : open a self-contained, movable project folder; Build > Build Standalone packages a runtime + your assets into something that runs with noeditor attached.

  • A real performance panel : frame time with percentiles, per-pass GPU timing off Vulkan timestamp queries, CPU stall breakdown, and a report you can copy off for comparing two runs.

Why Early Access

Because a rendering and editor codebase this size benefits from real use before it calls itself finished, and because the alternative building it in isolation and announcing it "done" is exactly the kind of claim this project's own docs argue against. The roadmap and the known-issues list are public in the repository, not just in marketing copy.

Who this is for, right now

Technical users comfortable with an engine that is still filling in gaps glTF import, a finished material graph editor, async asset loading rather than someone who wants a turnkey, feature-complete toolchain today. If you want to render scenes with real-time ray tracing that gracefully degrades on older hardware, script gameplay two different ways, and watch (or shape) an engine's roadmap directly, this is built for you.

System requirements at a glance

Windows 10/11 64-bit only. A Vulkan 1.2-capable GPU is the floor; a GPU with ray query

support (recent RTX/RDNA2-and-up cards) is what unlocks the ray-traced path everything

still renders correctly without one.

Full feature list, known issues and the public roadmap:

Systemanforderungen

Windows
SteamOS + Linux
    Mindestanforderungen:
    • Betriebssystem: Windows 10 64-bit
    • Prozessor: x86_64 CPU with SSE4.2, or x86_32
    • Grafik: Vulkan 1.2-capable GPU
    • Speicherplatz: 1 GB verfügbarer Speicherplatz
    • Zusätzliche Anmerkungen: Ray tracing (shadows, AO, reflections, ReSTIR GI) is optional throughout. A GPU without ray query support automatically uses the raster equivalent no scene changes required.
    Empfohlen:
    • Betriebssystem: Windows 11 64-bit
    • Grafik: Vulkan 1.2 GPU with ray query support (RTX 20-series / RDNA2 or newer)
    • Speicherplatz: 1 MB verfügbarer Speicherplatz
    Mindestanforderungen:
    • Betriebssystem: Any distribution
    • Prozessor: x86_64 CPU with SSE4.2, or x86_32
    • Arbeitsspeicher: 4 GB RAM
    • Grafik: Vulkan 1.2-capable GPU
    • Speicherplatz: 1 GB verfügbarer Speicherplatz
    Empfohlen:
    • Betriebssystem: Any distribution
    • Arbeitsspeicher: 4 MB RAM
    • Grafik: Vulkan 1.2 GPU with ray query support (RTX 20-series / RDNA2 or newer)
    • Speicherplatz: 1 MB verfügbarer Speicherplatz
Filter überprüfen