You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m encountering a problem where crypto_aead_aes256gcm_is_available() always returns 0 when using DSharpPlus.Natives.Sodium on a Ryzen 9 5900X machine. This results in the exception message:
The current hardware is not compatible with AEAD AES-256 GCM, a requirement for VoiceNext support.
However, Ryzen 9 CPUs definitely support AES-NI instructions, so hardware incompatibility shouldn’t be the issue.
Steps to Reproduce:
Use DSharpPlus.VoiceNext in a .NET project with the DSharpPlus.Natives.Sodium package.
Run the Discord bot on a system with a Ryzen 9 CPU (e.g., 5900X).
Observe the bot immediately crash on startup with the above exception.
Expected Behavior:
AES-256 GCM should be detected as supported on Ryzen 9 hardware, allowing VoiceNext to initialize successfully.
Actual Behavior:
crypto_aead_aes256gcm_is_available() indicates AES is not supported, causing VoiceNext initialization to fail.
Workaround:
Switching to the official libsodium NuGet package resolves the issue, confirming that the hardware is actually compatible and that the error occurs only when using DSharpPlus.Natives.Sodium.
Possible Cause:
The libsodium native binary in DSharpPlus.Natives.Sodium may be compiled without AES-GCM support or could be targeting an unexpected architecture.
Environment:
CPU: AMD Ryzen 9 5900X
.NET Version: 9
DSharpPlus: Latest version
OS: Windows 11 x64 (and possibly others)
Thank you!
The text was updated successfully, but these errors were encountered:
Hi,
I’m encountering a problem where
crypto_aead_aes256gcm_is_available()
always returns0
when using DSharpPlus.Natives.Sodium on a Ryzen 9 5900X machine. This results in the exception message:However, Ryzen 9 CPUs definitely support AES-NI instructions, so hardware incompatibility shouldn’t be the issue.
Steps to Reproduce:
DSharpPlus.Natives.Sodium
package.Expected Behavior:
Actual Behavior:
crypto_aead_aes256gcm_is_available()
indicates AES is not supported, causing VoiceNext initialization to fail.Workaround:
DSharpPlus.Natives.Sodium
.Possible Cause:
DSharpPlus.Natives.Sodium
may be compiled without AES-GCM support or could be targeting an unexpected architecture.Environment:
Thank you!
The text was updated successfully, but these errors were encountered: