If you are experiencing this issue, please help us get the problem fixed with AMD's driver team by clicking here and following the listed instructions.

Expected Behavior

The world renders without massive glitches.

Actual Behavior

There are massive graphical glitches.

Reproduction Steps

1. Load/generate any world.
2. Set chunk renderer to 'OpenGL 4.6'
3. Look at the massive glitches

Attachments

Expected behavior. (Made with chunk renderer set to 3.0)

Actual behaviour. (Made with chunk renderer set to 4.6)

Behaviour with mesa drivers with chunk renderer set to 4.6. (Mirrors expected behavior)

System Information

• Java Version: 14.0.1, AdoptOpenJDK (hotspot)
• CPU: AMD Ryzen 5 3600 6-Core Processor
• GPU: AMD Radeon RX 5700 XT
• Full DxDiag.txt

This is a widely reported issue with the newer AMD drivers on Windows, and to my best investigation it looks to not be the fault of Sodium but rather a driver issue. I'm not sure what the best channel is for reporting this issue to AMD, but if anyone has pointers, please let me know.

For future stumblers of this issue, you will need to use Sodium's OpenGL 3.0 renderer, which can be found in Video Settings > Performance.

We might want to blacklist these AMD drivers from using Sodium's OGL 4.6 renderer before the 0.1 release.

It would also be helpful to link the download page to the mesa drivers for AMD users.

@Siuolthepic The Mesa drivers are included in most linux distributions by default. If not they are most likely available in your package repository. They aren't available for windows.

There are apparently some OGL fixes scheduled for the next Adrenaline driver release, it may or may not fix this (although I personally think the chance is very slim considering the track record of the driver team). We'll just have to wait and see.

Multi-draw rendering is now disabled by default on the proprietary AMD drivers. See jellysquid3@bcbef57. I'll be keeping this issue open until the underlying problem is solved.

Resolved with c41a0af.

How do i apply the fix?

Resolved with c41a0af.

How do i apply the fix?

compile any commit of sodium after that commit or download the experimental build in the pinned of the #testers channel on jellysquids discord

Resolved with c41a0af.