-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
Nvidium #752
Comments
|
Hey, seems like its been a long time since we discussed this. I would like to know if lately there have been any considerations adding it since it seems like today the mod seems to be a bit more free from critical bugs. |
Not really, but we have to note that the mod went from alpha to beta and the dev fixed quite a few bugs/memory leaks |
I'll request it in non-CF mod list but I'll not consider it before Sodium 0.6 is out, due to its drastic changes. |
Little update on the mod: |
CurseForge link
No response
CurseForge Mod Distribution
Unknown
Modrinth link
https://modrinth.com/mod/nvidium
Source/other link
https://github.com/MCRcortex/nvidium
Mod file size
142.36 KB
License
(any other license)
What it does
The mod replaces the sodium rendering system and uses nvidia-only opengl extensions to increase framerates by a considerable amount.
With mesh shaders, a near fully gpu driven rendering pipeline is used, enabling very fast and performant geometry culling of terrain meaning your gpu can work much more efficiently.
Why should it be in the modpack
It gives a lot of fps to RTX users (with that modpack + nvidium i get so much more fps compared to Bedrock Edition itself)
I have some screenshots to prove it (16 chunks & default settings for both editions but no anti-analysing in bedrock)
Why shouldn't it be in the modpack
Not available on Curseforge. (maybe it will one day ?)
The mod is on beta (Even if I tested it and i had no issues with the other mods included)
Only working for GTX 1600+ users and RTX users (note that the mod disables completely by itself if the graphics card isn't compatible)
Additional details
No response
The text was updated successfully, but these errors were encountered: