-
Notifications
You must be signed in to change notification settings - Fork 484
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Poorly optimized FSR and NIS. #638
Comments
Magpie and LS have comparable performance in most cases, but LS has some aggressive optimization techniques that give it an edge in certain scenarios. Unlike LS, Magpie does not aim to boost the performance of 3D games, but rather to enhance the usability and support more filters.
Magpie cannot support FSR 2 due to technical limitations, as discussed here: #284 (comment)
|
The point of FSR is to increase performance in the game with minimal image loss and increase FPS. What is the point of Magpie filters if they negatively affect the game and instead of increasing FPS, it jumps like a roller coaster, Therefore it is necessary to increase performance in the game by upscaling. |
There are many factors that affect performance, such as hardware, drivers and games. You can try switching capture modes, increasing Magpie’s priority, etc. to improve performance. If LS is faster on your computer, use it. I will close this issue because there are no constructive suggestions. |
Magpie version 程序版本
0.10.2
Windows version 系统版本
Win11Pro/ x64/10.0 build 22621
Related screenshot (optional) 相关截图(可选)
No response
Reproduction steps 复现步骤
Developer hello. NIS and FSR are very poorly optimized. When FSR is running, the picture is twitching, the framerate is unstable, FPS is unstable, but the processing delay between frames is from 0.400 ms to 1.000 ms, in Lossless Scaling, FSR performs stably and well, unlike Magpie.The code for FSR v 2.0-2.2 has already been posted, this integration is needed for Magpie, please integrate this for greater performance on a PC.
Log files 日志文件
DxDiag.txt
The text was updated successfully, but these errors were encountered: