xgl | llpc | |
---|---|---|
5 | 1 | |
204 | 160 | |
1.5% | 2.5% | |
6.0 | 9.7 | |
about 1 month ago | about 1 month ago | |
C++ | C++ | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
xgl
Posts with mentions or reviews of xgl.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-01.
-
Resources for trying out Graphics driver development :
API layer is here: https://github.com/GPUOpen-Drivers/xgl
-
Do graphics companies ever use C or "C style C++"?
Not sure if you mean games or drivers, but AMDVLK uses C++ for it's usermode driver, it disables features like exceptions, RTTI etc. From my experience, games are generally the same. The kernel is still C though.
-
dear nvidia driver developers.
That's the wrong repo for AMDVLK. You have to look at these https://github.com/GPUOpen-Drivers/llpc https://github.com/GPUOpen-Drivers/xgl https://github.com/GPUOpen-Drivers/pal And this is also just the user space vulkan driver that nobody uses, the real driver you should look at is radv, which was initially written by red hat and Bas Nieuwenhuizen, and is maintained by Bas (afaiu as a hobby) and a team of Valve contractors. And then there's radeonsi, which is now mostly maintained by AMD, but has seen a lot of third party contributors over the years, and amdgpu + the display stack, which is mostly worked on by AMD.
-
New AMDVLK: add AMD switchable graphics layer to switch AMD Vulkan driver between amdvlk and RADV
The problem is not the global variable, maybe I've expressed my self wrong. The issue is that this doesn't store the needed function pointers for each instance, just for one and it will get overwritten if you create another instance. In many other layers you have some kind of map. (well not the VkInstance itself but the loader's dispatch table pointer, but that's probably too much details)
llpc
Posts with mentions or reviews of llpc.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-01.
-
dear nvidia driver developers.
That's the wrong repo for AMDVLK. You have to look at these https://github.com/GPUOpen-Drivers/llpc https://github.com/GPUOpen-Drivers/xgl https://github.com/GPUOpen-Drivers/pal And this is also just the user space vulkan driver that nobody uses, the real driver you should look at is radv, which was initially written by red hat and Bas Nieuwenhuizen, and is maintained by Bas (afaiu as a hobby) and a team of Valve contractors. And then there's radeonsi, which is now mostly maintained by AMD, but has seen a lot of third party contributors over the years, and amdgpu + the display stack, which is mostly worked on by AMD.
What are some alternatives?
When comparing xgl and llpc you can also consider the following projects:
pal - Platform Abstraction Library
AMDVLK - AMD Open Source Driver For Vulkan
PAL - Performance Analysis of Logs (PAL) tool
bgfx - Cross-platform, graphics API agnostic, "Bring Your Own Engine/Framework" style rendering library.