manta-ray
RayTracingInVulkan
| manta-ray | RayTracingInVulkan | |
|---|---|---|
| 6 | 16 | |
| 732 | 1,116 | |
| - | - | |
| 0.0 | 5.0 | |
| over 2 years ago | 16 days ago | |
| C++ | C++ | |
| - | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
manta-ray
RayTracingInVulkan
-
AMDVLK Release v-2023.Q2.2
on raw tests AMDVLK is about 100% faster than RADV like this one
-
RADV RayTracing on RDNA 2 doesn't work
This Vulkan RayTracing Test also only runs with AMDVLK
-
Anyone having better luck with the Intel Arc A750/770? It seems only Vulkan games are working well.
I did some more testing in regards to raytracing on Linux/Vulkan and could get this benchmark to run (albeit horribly slow) with the Arc 750
-
Doom Eternal : Ray traycing on RX5600XT
Oh sorry. That's nice! The only RT stuff that worked nicely for me (except FPS, offcourse) was this: https://github.com/GPSnoopy/RayTracingInVulkan
- How do we write a ray tracer in opengl?
- Valve announces the Steam Deck
-
Vulkan not enabled for my graphics card, can anyone help?
Have you tried testing it? Here is a benchmark someone created.
-
Vulkan Ray Tracing: Blocky edges when there is another object behind
Reminds me of this bug caused by missing "non-uniform" hints: https://github.com/GPSnoopy/RayTracingInVulkan/issues/36
-
Cyberpunk 2077 Ray Tracing Performance: NVIDIA 60% to 80% faster!
The man himself admitted he started celebrating way too early. Just look at the github issue: https://github.com/GPSnoopy/RayTracingInVulkan/issues/28
-
[Hardware Unboxed] Don't Buy GeForce? Are We Testing GPUs Wrong? Nvidia Driver Overhead Discussion
With xbox and PS5 using AMDs ray tracing architecture, it would be dumb for devs to not optimize for AMD. 22% improvement with basically a code line swap. https://github.com/GPSnoopy/RayTracingInVulkan/issues/28#issuecomment-792966138
What are some alternatives?
yocto-gl - Yocto/GL: Tiny C++ Libraries for Data-Driven Physically-based Graphics
vulkan-compute-ray-tracing - Interactive ray tracer made with Vulkan compute shader.
RayTracer - Ray Tracer in C++ with openGL.
bgfx - Cross-platform, graphics API agnostic, "Bring Your Own Engine/Framework" style rendering library.
HybridRenderingEngine - Clustered Forward/Deferred renderer with Physically Based Shading, Image Based Lighting and a whole lot of OpenGL.
clray - Realtime GPU (OpenCL) polygon mesh raytracer
RayTracer - A ray tracing program
dxvk - Vulkan-based implementation of D3D9, D3D10 and D3D11 for Linux / Wine
FastNoise2 - Modular node graph based noise generation library using SIMD, C++17 and templates
RenderBender - A third party program to change Minecraft RTX's internal settings externally, directly in-memory, at runtime.
path-tracer - A physically-based Monte Carlo Path Tracer (Ray Tracer) from scratch
Lift - Vulkan Path Tracer with Optix Denoiser integration