모든 소프트웨어 > 게임 개발 > LAB Engine
커뮤니티 허브
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.

로그인하셔서 게임을 찜 목록에 추가하거나, 팔로우하거나 또는 제외로 지정하세요.

기능
언어:
인터페이스 음성 지원 자막
한국어 지원하지 않음
영어 ✔

앞서 해보는 소프트웨어

이 소프트웨어가 개발되는 과정에 참여하세요.

주의 사항: 이 앞서 해보기 소프트웨어는 완성되지 않았으며 앞으로 더 변하거나 변하지 않을 수 있습니다. 현재 상태의 소프트웨어가 흥미롭지 않다면 이 소프트웨어가 개발을 거치며 발전하는지 살펴보는게 좋습니다. 앞서 해보기에 대해 더 알아보세요.

개발자의 한마디:

왜 앞서 해보기를 진행하나요?

“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.”

이 소프트웨어는 대략 얼마간 앞서 해볼 수 있나요?

“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.”

정식 버전은 앞서 해보기 버전과 어떻게 달라지나요?

“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 ”

앞서 해보기 버전은 현재 어떤 상태인가요?

“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.”

이 소프트웨어는 앞서해보기 기간동안 가격이 달라질 수도 있습니까?

“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”

개발 과정에서 어떻게 커뮤니티와 소통할 계획인가요?

“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”
더 읽어보기
한국어(을)를 지원하지 않습니다

이 제품은 귀하의 로컬 언어를 지원하지 않습니다. 구매하기 전에 아래에 있는 지원하는 언어 목록을 확인해주세요.

이 게임은 아직 Steam에 출시되지 않았습니다

출시 예정일: 발표 예정

관심이 있으신가요?
찜 목록에 추가하고 출시가 되면 알림을 받으세요.
 

이 소프트웨어의 버그를 신고하고 피드백을 토론 게시판에 남겨주세요

모든 토론 보기

소프트웨어 정보

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:

시스템 요구 사항

Windows
SteamOS + Linux
    최소:
    • 운영 체제: Windows 10 64-bit
    • 프로세서: x86_64 CPU with SSE4.2, or x86_32
    • 그래픽: Vulkan 1.2-capable GPU
    • 저장 공간: 1 GB 사용 가능 공간
    • 추가 사항: 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.
    권장:
    • 운영 체제: Windows 11 64-bit
    • 그래픽: Vulkan 1.2 GPU with ray query support (RTX 20-series / RDNA2 or newer)
    • 저장 공간: 1 MB 사용 가능 공간
    최소:
    • 운영 체제: Any distribution
    • 프로세서: x86_64 CPU with SSE4.2, or x86_32
    • 메모리: 4 GB RAM
    • 그래픽: Vulkan 1.2-capable GPU
    • 저장 공간: 1 GB 사용 가능 공간
    권장:
    • 운영 체제: Any distribution
    • 메모리: 4 MB RAM
    • 그래픽: Vulkan 1.2 GPU with ray query support (RTX 20-series / RDNA2 or newer)
    • 저장 공간: 1 MB 사용 가능 공간
평가 필터 조건