OpenXRay/xray-16

Vulkan Renderer

Open

#447 opened on Aug 2, 2019

View on GitHub
 (18 comments) (12 reactions) (0 assignees)C++ (519 forks)auto 404
Developer ExperienceHelp wantedModmaker ExperiencePlayer ExperiencePortabilityRenderer

Repository metrics

Stars
 (3,524 stars)
PR merge metrics
 (PR metrics pending)

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

Research direction
Study the existing OpenGL renderer (xrRender D3D9 or similar) to understand the architecture, then pick a small subtask like HW (hardware abstraction) or Resources management to implement a minimal Vulkan backend.
Tech stack
None
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C++Vulkan APIGraphics Programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15