ValveSoftware / ValveSoftware/Proton

Add information about DLSS support to Proton Log

Open
#4,924 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature Request
Dominant language
C++
Stars
32.8k
Forks
1.6k
PR merge metrics
PR metrics pending

Description

Feature Request

I confirm:

  • that I haven't found another request for this feature.
  • that I have checked whether there are updates for my system available that
    contain this feature already.

Description

I've packaged the latest beta 470.42.01 nvidia-drivers for Exherbo Linux letting the two {_,}nvngx.dll files getting installed to /usr/x86_64-pc-linux-gnu/lib/nvidia/wine/, using Proton Experimental I'm able to select DLSS within No Man's Sky and it appears to work, however I'm not able to tell if it actually does. I can't find the dlls being copied into the proton prefix compatdata/275850/pfx/drive_c/windows/system32/ and there doesn't seem to be any log output whether it actually tries to copy the files, does so succesfully, or fail to find/copy them.

It would be nice to have steam report the DLSS support or {_,}nvngx.dll files in the steam system information or the pressure-vessel information output.

Additionally it would be nice if Proton could throw something on the command line like it does for fsync fsync: up and running.

Attached is my steam system-information.txt

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the attached system-information.txt and the existing Steam system-information, pressure-vessel information, and Proton command-line output paths. Determine where DLSS or {_,}nvngx.dll availability and copy results should be reported. Done means Steam or pressure-vessel output identifies support and Proton logs whether the files were found and copied successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.