OpenXRay / OpenXRay/xray-16

Vulkan Renderer

Open
#447 18 comments 12 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Developer Experience Help wanted Modmaker Experience Player Experience Portability Renderer
Dominant language
C++
Stars
3.6k
Forks
536
Avg merge
6d 1h
Merged PRs (30d)
3

Description

Note that it should not be a replacement for existing OpenGL renderer, but another renderer.

xrRender_VK:

  • HW
  • Backend
  • Resources management (textures, SH_RT, SH_Atomic etc)
  • State management
  • and more...
  • Shaders (two ways, should be supported both)
    • Use cross-compiler (see #258) to compile shaders from existing HLSL code.
    • Support own GLSL shaders in case if they are exist. (We should decide on folder name)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing OpenGL renderer and the shader cross-compiler work referenced in #258. The issue describes a separate xrRender_VK renderer with hardware, backend, resource, state-management, and shader requirements; done means implementing those areas without replacing the OpenGL renderer.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-graphics, game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.