GamEngine — Preview Release
This release provides a first public preview of GamEngine, a C++23 / Vulkan 1.4 3D game engine focused on modern GPU-driven rendering, real-time graphics, and scalable rendering architecture.
GamEngine is still under active development. This release is intended primarily for testing, experimentation, feedback, and development rather than production use.
What's Included
This release includes the GamEngine Editor and runtime with major engine systems already integrated:
Rendering
- Vulkan 1.4 renderer
- Forward physically based rendering
- GPU-driven scene rendering
- GPU instance and frustum culling
- Hi-Z occlusion infrastructure
- Meshlets and hierarchical meshlet processing
- GPU indirect rendering
- Directional Virtual Shadow Maps
- GTAO
- Temporal Anti-Aliasing
- MSAA
- Image-Based Lighting
- Reflection probes
- Bloom
- ACES tonemapping
- HDR rendering
- GPU particle simulation
- GPU-driven grass rendering
- Experimental Virtual Water system
Engine
- Entity Component System
- Scene system
- Parent/child transform hierarchy
- Prefabs
- Asset management
- glTF / GLB support
- Custom cooked mesh and texture formats
- PhysX integration
- Input system
- Runtime UI
- Task scheduling
- CPU/GPU profiling
- Diagnostics and logging
Editor
- Scene viewport
- Hierarchy panel
- Components / Inspector
- Asset Manager
- Shader Graph
- Profiler
- Console
- Integrated terminal
- Terrain tools
- Play / Pause / Stop workflow
- Script hot reload
- Shader hot reload
- Game build pipeline
C++ Scripting
Gameplay scripts are written in native C++ and compiled into a separate GameScripts.dll.
The scripting system supports:
- script lifecycle callbacks
- scene access
- entities and actors
- transforms
- parent/child relationships
- physics
- native hot reload
Standalone Game Builds
The Editor can export standalone Windows games.
A game build contains its own executable, runtime libraries, compiled gameplay scripts, shaders, and cooked project content.
System Requirements
The current release primarily targets Windows x64.
Recommended requirements:
- Windows 10 or Windows 11 64-bit
- Vulkan 1.4 capable GPU
- Recent GPU drivers
- Dedicated GPU recommended
GamEngine is still being tested across different GPU vendors and hardware configurations, so compatibility reports are especially useful.
Important
This is a development preview.
You may encounter:
- crashes
- rendering artifacts
- unstable or incomplete features
- driver-specific Vulkan issues
- incorrect rendering on some GPUs
- performance regressions
- editor workflow issues
Some systems, especially Virtual Water and parts of the GPU-driven rendering pipeline, should currently be considered experimental.
Reporting Crashes
If GamEngine crashes, please create a GitHub issue and attach the log from the crashing session.
On Windows, Editor logs are stored in:
%LOCALAPPDATA%\GamEngine\Editor\Logs\
You can paste the following path directly into the Windows Explorer address bar:
%LOCALAPPDATA%\GamEngine\Editor\Logs
Logs are organized by date. Please attach the newest .log file corresponding to the session that crashed.
For exported games, logs are stored under:
%LOCALAPPDATA%\GamEngine\Games\<GameName>\Logs\
If crash-related files are generated, also check:
%LOCALAPPDATA%\GamEngine\Editor\Crashes\
or, for an exported game:
%LOCALAPPDATA%\GamEngine\Games\<GameName>\Crashes\
Please include your hardware specifications
When reporting a crash, please also provide:
- Operating system and version
- GPU
- GPU driver version
- CPU
- RAM
- whether you are using a laptop or desktop
- GamEngine release/version
- what you were doing immediately before the crash
- steps that reproduce the crash, if known
For rendering-related problems, screenshots or short recordings are also extremely helpful.
A good crash report should look similar to:
OS: Windows 11 64-bit
GPU: NVIDIA GeForce RTX 3060
Driver: 6xx.xx
CPU: AMD Ryzen 5 5600X
RAM: 32 GB
Problem:
Editor crashes when enabling TAA after loading the scene.
Steps to reproduce:
1. Open the project
2. Load Main.scene
3. Enable TAA
4. Enter Play Mode
5. Editor crashes
Attached:
- latest Editor log
- screenshot / video if applicable
Crash reports without logs and hardware information may be very difficult to diagnose, especially for Vulkan or GPU-driver-related problems.
Reporting Rendering Bugs
For visual problems such as:
- missing shadows
- flickering
- TAA ghosting or instability
- GTAO artifacts
- incorrect materials
- missing textures
- broken reflections
- culling problems
- corrupted geometry
please include:
- screenshot or video
- GPU model
- GPU driver version
- selected graphics preset
- scene or asset that reproduces the problem
- latest Editor log
If the issue changes depending on the camera position or viewing angle, a short video is preferable to a screenshot.
Feedback
Feedback, bug reports, performance results, and hardware compatibility reports are welcome.
In particular, reports from different:
- NVIDIA GPUs
- AMD GPUs
- Intel GPUs
- laptop GPUs
- older Vulkan-capable hardware
are useful for improving compatibility and performance.
When reporting performance, please include the resolution, graphics preset, GPU, CPU, and approximate scene complexity.
Known Limitations
- Windows x64 is currently the primary supported platform.
- Standalone game export currently targets Win64.
- Some rendering systems are still undergoing optimization and stabilization.
- Virtual Water is experimental.
- GPU and driver compatibility has not yet been validated across a wide hardware range.
- APIs and project formats may change between releases.
License
GamEngine is released under the Apache License 2.0.
Thank you for testing GamEngine and helping improve the engine.