https://github.com/iveevi/kobra

Research oriented game engine exploring state of the art rendering techniques
https://github.com/iveevi/kobra

game-development game-engine game-engine-3d gamedev

Last synced: about 2 months ago
JSON representation

Research oriented game engine exploring state of the art rendering techniques

• Host: GitHub
• URL: https://github.com/iveevi/kobra
• Owner: iveevi
• Created: 2021-09-18T01:03:12.000Z (over 3 years ago)
• Default Branch: development
• Last Pushed: 2023-06-16T05:50:14.000Z (over 1 year ago)
• Last Synced: 2024-01-25T23:53:47.000Z (12 months ago)
• Topics: game-development, game-engine, game-engine-3d, gamedev
• Language: Cuda
• Homepage:
• Size: 220 MB
• Stars: 20
• Watchers: 1
• Forks: 3
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
![](kobra_logo.svg)

# Kobra

Kobra is a 3D rendering engine written in C++ using the Vulkan API. It is

designed with research development in mind, so that more time can be spent

towards experimentation rather than implementation. This project is still in

progress.

## Current Features

Kobra targets physically-based path-tracing pipelines. Currently, only

path-tracing with OptiX/CUDA is supported (see the **Upcoming** section

for platforms that will be supported in the future).

However, Kobra provides other facilities that enables convenient development of

rendering applications, such as rasterization (with customizable shader

programs) and UI rendering (currently built directly off of ImGui).

These facilities can be accessed as *layers*; for example, `ForwardRenderer`,

`UI`, and `Denoiser` are layers which perform computations related to forward

rendering, UI rendering, and image denoising. Multiple layers can be

sequentially dispatched in the same command buffer. The documentation for such

operations are still in development.

Furthermore, Kobra provides an (basic) interface for editing scenes and

rendering, shown below:

![](media/editor.png)

Note that this is not final by any means, and any suggestions for improving this

interface are welcome.

Scenes are currently specified with a file describing components in

the entity-component system; see `scenes/` for examples. The file specification

for scenes is not fixed, and still being developed.

### Layers

The following list includes the currently available layers.

- `MeshMemory`: manages mesh memory, which is often shared across other layers

- `ForwardRenderer`: performs forward rendering, with customizable `ShaderProgram`s

- `UI`: does UI rendering, by attaching user-defined `ImGuiAttachment` objects

- `Denoiser`: denoises input images

- `Framer`: renders a plain image to the swapchain; useful for raytracing, where

  the image is generated outside of Vulkan

- `System`: manages raytracing buffers and acceleration structures for a given

  scene

- `ArmadaRTX`: performs raytracing of arbitrary programs; the functionality of

  the RTX kernels can be programmed via `AttachmentRTX` objects -- see

  `path_tracer.cuh` and `restir.cuh` in the `include/armada/` directory for

  examples

## Renders

The following are example renders generated from Kobra's OptiX path tracer (+AI

denoising).

### Bathroom [1]

![](media/bathroom.png)

### Breakfast Room [1]

![](media/breakfast-room.png)

### Fireplace [1]

![](media/fireplace.png)

### Kitchen [2]

![](media/kitchen.png)

### Living Room [1]

![](media/living-room.png)

### San Miguel [1]

![](media/san-miguel.png)

### Sibenik [1]

![](media/sibenik.png)

[1] [McGuire Computer Graphics Archive](https://casual-effects.com/data/)

[2] [Rendering Resources](https://benedikt-bitterli.me/resources/)

# Upcoming

- [ ] Revive the GLSL path tracer (using RadeonRays as backend)

- [ ] VulkanRTX port

- [ ] Implement an applet for presenting image difference with various metrics

  (e.g. MAPE, FLIP)