Mirrored_Repos/nvidia-patch
1
0
Fork 0
mirror of https://github.com/keylase/nvidia-patch.git synced 2024-12-23 05:13:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #360 from Snoop05/patch-1

Browse Source 
win: nvfbcwrp: mention registry entry
This commit is contained in:
Snawoot 2021-01-09 00:53:08 +02:00 committed by GitHub
commit 5cddd254cc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
win/nvfbcwrp/README.md
View File

@ -27,3 +27,11 @@ Hence, if default magic baked into nvfbcwrp doesn't work for you, you have to:
1. Specify environment variable `NVFBCWRP_DUMP_DIR` in your configuration with path to existing writable directory. Here is a [guide](http://web.archive.org/web/20191207221102/https://docs.oracle.com/en/database/oracle/r-enterprise/1.5.1/oread/creating-and-modifying-environment-variables-on-windows.html) about environment variables edit. It's sufficient to add "user" environment variable.
2. Run some NvFBC application with valid `privateData` keys and initiate recording session.
3. Grab some output file and specify it's path in `NVFBCWRP_PRIVDATA_FILE`. At this point you can unset `NVFBCWRP_DUMP_DIR` to stop `privateData` capture.
## 3rd-party software
For some software (e.g Steam) it is also needed to add registry value to use NvFBC, which you can do by running:
```batch
reg add "HKEY_LOCAL_MACHINE\SSYSTEM\CurrentControlSet\Services\nvlddmkm" /v NVFBCEnable /d 1 /t REG_DWORD /f
```
(reboot / driver restart required to take effect)