Fakenvapi system memory leak with MonsterHunterRise (Window 10)
Since there has been an active increase in new issues without any basic info to help troubleshooting, we're releasing this Issue Report Template that should help troubleshoot without our magic 8 ball. Going forward, issues that do not follow the Template will be ignored.
Game name and version:
MonsterHunterRise (Steam) 16.0.2.0
Mods and mod versions used
OptiScaler v0.7.7-pre9 (Daria) + Fakenvapi 1.2.1
GPU
AMD Radeon RX 9070 XT
OS
Windows 10 (10.0.19045) System Model: MS-7E12 BIOS: 1.H0 (type: UEFI) Processor: AMD Ryzen 7 9800X3D Memory: 65536MB RAM
Used automated or manual install?
- [x] Automated
If on AMD/Intel and Automated, used DLSS inputs?
- [x] Yes
Also please mention in description which upscaler inputs are used (which upscaler you selected in game settings). DLSS
Did you check the Wiki?
- [x] Yes
Please describe the issue and steps to reproduce it
Example: I am using DLSS in game settings and the game is crashing when switching to FSR4.
The in-game DLSS option would not show up with only DXGI Spoofing.
FakeNvapi is also required. As setting below.
OptiScaler.txt
It works with FSR 3 or FSR 4, but the system RAM will be occupied rapidly to the phycal maximum, as below.
Sometimes the occupied RAM would not released even when the game exited.
I have noticed Fakenvapi 1.2.1 release note with "Fix wrong memory free" but 1.2.1 still no help.
I have attached
- [x] OptiScaler.log (set
LogLevel=0andLogToFile=truein Optiscaler.ini, zip it if too big) OptiScaler.zip - [x] Screenshot of game folder (where you placed Opti)
- [x] Screenshot of Opti overlay in-game (opens with shortcut, default Insert)
If you believe this is a Fakenvapi issue, then it's more appropriate to post on Fakenvapi's Github.
At best I can recommend maybe trying the pre-release one from Actions tab - Fakenvapi 1.2.1.1.zip
Or trying setting in fakenvapi.ini - force_latencyflex=1, force_reflex=1
I am not sure is it pure Fakenvapi issue. The game is DLSS only and the opti built-in DXGI spoofing could not trick the game. So the DLSS in-game option only availible when opti work with Fakenvapi. Both [Fakenvapi 1.2.1.1.zip] or trying setting in fakenvapi.ini - force_latencyflex=1, force_reflex=1 not work.
I will post this issue to Fakenvapi Github. Thanks for your help.
Tried the same combination except dxgi.dll instead of d3d12.dll in microsoft flight simulation 2020, seems active in-game dlss option with no issue. Maybe it is a game exclusive problem.
Wouldn't be surprising as it's Capcom which requires REF, and if you're using other mods (maybe SpecialK), there could be some memory leak.
Btw what's the size of fakenvapi.log?
I had prohibited SpecialK but in case I tried again with SpecialK totally uninstalled. The fakenvapi.log is less then 1KB. fakenvapi.log
By the way for microsoft flight simulation 2020 this setup work with DLSS input could run XESS, FSR2 but not FSR3(FSR4).