Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vulkan Mod Question #477

Open
SergioK29 opened this issue Jul 29, 2024 · 5 comments
Open

Vulkan Mod Question #477

SergioK29 opened this issue Jul 29, 2024 · 5 comments

Comments

@SergioK29
Copy link

SergioK29 commented Jul 29, 2024

Describe the request

What is the point of this if sodium is faster? Do you plan on making it compatible with sodium? i.e sodiums chunk render optimizations + using vulkan instead of opengl for extra performance?

Also vulkan mod + nvidium could allow nvidium to work on AMD gpus, since amd will never have mesh shaders for opengl, but does have mesh shaders for vulcan

Correct me if im wrong on any of this, im not a graphics guy

@redzrush101
Copy link

Why r comparing sodium with vulkanmod it's an entirely diff thing ?

@Felix14-v2
Copy link

Felix14-v2 commented Jul 30, 2024

What is the point of this if sodium is faster?

Sodium is not faster. It's just different. Performance highly depends on your hardware.

Do you plan on making it compatible with sodium?

VulkanMod already use Sodium chunk building (and maybe some other stuff).

Also vulkan mod + nvidium could allow nvidium to work on AMD gpus

That's not how the things work. Nvidium highly depends on Sodium structure, it will never be compatible with VulkanMod. But you can implement mesh shaders support without it (for example, Voxy also can use mesh shaders).

amd will never have mesh shaders for opengl

They are already working on it: GPUOpen-Drivers/AMD-Gfx-Drivers#4

@NXTler
Copy link
Contributor

NXTler commented Aug 25, 2024

What is the point of this if sodium is faster? Do you plan on making it compatible with sodium? i.e sodiums chunk render optimizations + using vulkan instead of opengl for extra performance?

Sodium and VulkanMod will never be compatible, as Sodium relies on a lot of OpenGL calls. It's correct that the Chunk building originated from Sodium, but it's the only part and is heavily modified.

Also vulkan mod + nvidium could allow nvidium to work on AMD gpus, since amd will never have mesh shaders for opengl, but does have mesh shaders for vulcan

That's not how it works... Nvidium relies completely on Sodium and uses OpenGL mesh shaders, which as you already said only works on Nvidia. You can't just put a OpenGl program into Vulkan and have it working, these APIs are completely different from another.

This issue can be closed.

@SergioK29
Copy link
Author

What is the point of this if sodium is faster? Do you plan on making it compatible with sodium? i.e sodiums chunk render optimizations + using vulkan instead of opengl for extra performance?

Sodium and VulkanMod will never be compatible, as Sodium relies on a lot of OpenGL calls. It's correct that the Chunk building originated from Sodium, but it's the only part and is heavily modified.

Also vulkan mod + nvidium could allow nvidium to work on AMD gpus, since amd will never have mesh shaders for opengl, but does have mesh shaders for vulcan

That's not how it works... Nvidium relies completely on Sodium and uses OpenGL mesh shaders, which as you already said only works on Nvidia. You can't just put a OpenGl program into Vulkan and have it working, these APIs are completely different from another.

This issue can be closed.

I if you replaced the opengl calls made by both sodium and nvidium, what would happen? (probably would be a ton of work though)

@NXTler
Copy link
Contributor

NXTler commented Sep 10, 2024

As it was already said, these are two very different APIs, you can't just translate a few calls and have it working with +200% FPS, that's not how it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants