-
Notifications
You must be signed in to change notification settings - Fork 5
Description
Following the README.md
in this repository, I attempted to build the solari example from the Bevy repository. I placed the DLSS SDK in C:\Packages\DLSS
and executed the following command in the Bevy repository, which eventually compiled successfully:
cargo build --release --example solari --features=bevy_solari,dlss
After that, I moved target\release\examples\solari.exe
to D:/solari/solari.exe
and copied the relevant files from the assets
directory to D:/solari
for packaging. When I double-clicked to run D:/solari/solari.exe
in File Explorer, everything ran smoothly. However, this struck me as somewhat odd because I had set the DLSS_SDK
environment variable in my config.nu
(I use Nushell), so theoretically, double-clicking to run it directly in File Explorer shouldn’t have picked up the DLSS_SDK
variable. Yet the runtime performance was good—the on-screen information indicated that Ray Reconstruction was enabled, and there were no visible artifacts. At the time, though, I didn’t pay much attention to this issue.
Then I copied nvngx_dlss.dll
and nvngx_dlssd.dll
to D:/solari/
. However, strangely enough, when I tried to run solari.exe
again, it now reported that Ray Reconstruction was no longer supported:
2025-08-27T16:07:28.342784Z INFO bevy_anti_aliasing::dlss: DLSS is not supported on this system
Then I tried deleting these two DLL files from D:/solari/
and renamed C:\Packages
to C:\PackagesAAA
(to prevent the program from accessing the SDK and rule out the influence of the DLSS_SDK
environment variable). The result was that Ray Reconstruction was no longer supported. So the current situation can be summarized as follows:
DLSS_SDK env |
Real DLSS SDK Path | Copied dlls to game directory | Support DLSS |
---|---|---|---|
C:\Packages\DLSS |
C:\Packages\DLSS |
❌ | ✅ |
C:\Packages\DLSS |
C:\Packages\DLSS |
✅ | ❌ |
C:\Packages\DLSS |
C:\PackagesAAA\DLSS |
✅ | ❌ |
C:\Packages\DLSS |
C:\PackagesAAA\DLSS |
❌ | ❌ |
Only the first scenario worked correctly. I find this quite strange, but I don’t have a reasonable explanation for it. Of course, it’s also possible that the issue was caused by some misconfiguration or incorrect operation on my end.
System Info:
OS: Windows 11
GPU: Nvidia RTX 4070 Super