Skip to content
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

Warn about the high performance cost of JINC2 and xBR filtering #2889

Merged

Conversation

Calinou
Copy link
Contributor

@Calinou Calinou commented Sep 22, 2022

These options (especially xBR) have a very high cost. In my experience, xBR has a greater impact on the framerate than enabling 4× SSAA or PGXP in CPU mode (whose quality increase is much more obvious).

These options are also essentially unusable on mobile, regardless of how powerful your device is. As a result, this adds warnings both in the option names and the description.

Bilinear filtering is not affected by this performance cost, as GPUs can perform this in hardware without having to emulate filtering through a shader.

Benchmark

System information

System

OS: Fedora 36
CPU: Intel Core i7-6700K (4.4 GHz)
GPU: GeForce GTX 1080 (NVIDIA 515.65.01)

DuckStation settings

Renderer: Vulkan
Resolution scale: 6× (+ 16:9 widescreen)
Crop: All Borders
PGXP: Enabled (with Culling Correction, Texture Correction, Preserve Projection Precision, Vertex Cache)

Note: "No Edge Blending" modes perform identically to the standard modes.

Nearest-Neighbor

2022-09-22_14 13 31

Bilinear

2022-09-22_14 13 57

JINC2

2022-09-22_14 14 40

xBR

2022-09-22_14 15 02

These options (especially xBR) have a very high cost. In my experience,
xBR has a greater impact on the framerate than enabling 4× SSAA or PGXP
in CPU mode (whose quality increase is much more obvious).

These options are also essentially unusable on mobile, regardless of
how powerful your device is. As a result, this adds warnings both
in the option names and the description.

Bilinear filtering is not affected by this performance cost, as GPUs
can perform this in hardware without having to emulate filtering
through a shader.
@stenzek stenzek merged commit 7ef600a into stenzek:master Sep 24, 2022
@Calinou Calinou deleted the texture-filtering-warn-performance-cost branch September 24, 2022 14:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants