Upscaling and Anti-Aliasing Options and Controls Tab: Controller Layouts and Button Mapping #804

Closed

opened 2026-11-08 22:03:23 +00:00 by Adri90vm · 2 comments

Adri90vm commented

2026-11-08 22:03:23 +00:00

(Migrated from github.com)

The idea

Upscaling and Anti-Aliasing Options

The current Upscaling setting only offers Off, Catmull-Rom and Lanczos. It would be great to expand this section with modern upscaling and anti-aliasing technologies, giving users more control over image quality, performance and visual clarity.

The goal is to provide different solutions depending on the user's GPU, allowing NVIDIA and AMD users to benefit from their respective technologies.

Proposed options

Upscaler selection:

Off (Native Resolution).
Catmull-Rom.
Lanczos.
NVIDIA DLSS Super Resolution.
NVIDIA DLAA (Deep Learning Anti-Aliasing).
AMD FSR 3.1.6.
AMD FSR 4.1.2.

Upscaling Quality / Preset:

When supported by the selected upscaler, provide the following options:

Native AA (1.0x).
Quality.
Balanced.
Performance.
Ultra Performance.

Native Anti-Aliasing options:

DLAA: Use NVIDIA's Deep Learning Anti-Aliasing at native resolution, focusing on image quality and reducing jagged edges rather than increasing FPS.
FSR Native AA: Use AMD's native-resolution anti-aliasing mode (1.0x scaling) to improve image stability and reduce aliasing without rendering at a lower resolution.

Additional behaviour and considerations

Keep Sharpness as an independent setting, allowing users to fine-tune the final image regardless of the selected upscaler.
Preserve the existing Catmull-Rom and Lanczos options as lightweight alternatives.
Automatically detect GPU and driver compatibility. Unsupported options should be disabled or hidden rather than causing rendering errors.
Where supported, allow FSR 4.1.2 to be selected, with FSR 3.1.6 available as an alternative when the hardware or driver does not support the newer version.
When DLSS or FSR is active, the selected quality preset should determine the internal rendering resolution. Avoid applying the existing manual resolution scaling on top of the upscaler, which could result in unnecessary double scaling.
Temporal upscaling requires the appropriate rendering information, such as depth buffers, motion vectors and temporal jitter, to be provided by the Vulkan renderer.

The intention is to give users access to modern reconstruction technologies while retaining the existing scaling methods as fallbacks.

Controls Tab: Controller Layouts and Button Mapping

The Controls tab should provide a more complete input configuration experience, allowing users to select their preferred controller layout or keyboard configuration.

In addition to individual button and key rebinding, it would be useful to introduce predefined input profiles for the most common controller layouts.

1. Input Layout Presets

Add a Controller Layout selector with the following profiles:

Original (Nintendo / Switch): Preserve the original Nintendo button arrangement.
- Bottom: B
- Right: A
- Top: X
- Left: Y
Xbox: Use the standard Xbox button arrangement.
- Bottom: A
- Right: B
- Top: Y
- Left: X
PlayStation: Provide the familiar PlayStation button arrangement and symbols.
- Bottom: Cross (X)
- Right: Circle (O)
- Top: Triangle (△)
- Left: Square (□)
Keyboard & Mouse: Display keyboard and mouse bindings instead of controller button labels. Preserve the existing keyboard defaults, such as WASD for movement and the arrow keys for camera controls, while allowing the user to rebind individual actions.
Custom: Allow users to define their own button arrangement without being restricted to the predefined layouts.

2. Button Mapping and Rebinding

The Controls page should display the available game actions alongside their assigned inputs.

Suggested layout:

Each input should be individually configurable.

Selecting an input and pressing the desired controller button or keyboard key should assign it to that action.
Prevent accidental duplicate assignments, using the existing swap behaviour where appropriate.
Allow users to clear an assignment and restore the default configuration.
Preserve independent controller and keyboard bindings.

3. Interface and Visual Feedback

Display the appropriate button symbols depending on the selected layout: Nintendo, Xbox or PlayStation.
Update the button labels and visual prompts throughout the Controls interface to match the selected controller profile.
For Keyboard & Mouse, show the actual assigned keys instead of controller symbols.
Clearly highlight the currently selected action and its assigned input.
Keep the existing visual style of the redesigned Options menu, including its gold selection highlights and detail panel.

4. Configuration and Persistence

Save the selected controller layout and custom bindings in hookshot_options.ini.
Changing between predefined layouts should apply the corresponding mapping without unexpectedly destroying the user's custom configuration.
Allow users to switch between layouts at any time.
Keep the selected layout and individual bindings after restarting the game.

The idea is to make controller configuration more intuitive, especially for players coming from Xbox or PlayStation, while preserving the original Nintendo controls and providing complete keyboard customization.

This should build on the existing input rebinding and controller layout work introduced in PRs #350 and #372, extending it with PlayStation support and a more complete Keyboard & Mouse profile.

</html> </html>

Anything else

No response

### The idea <html> <body> <html><head></head><body><h2>Upscaling and Anti-Aliasing Options</h2>The current <code>Upscaling</code> setting only offers <code>Off</code>, <code>Catmull-Rom</code> and <code>Lanczos</code>. It would be great to expand this section with modern upscaling and anti-aliasing technologies, giving users more control over image quality, performance and visual clarity.The goal is to provide different solutions depending on the user's GPU, allowing NVIDIA and AMD users to benefit from their respective technologies.<h3>Proposed options</h3>Upscaler selection:<ul><li>Off (Native Resolution).</li><li>Catmull-Rom.</li><li>Lanczos.</li><li>NVIDIA DLSS Super Resolution.</li><li>NVIDIA DLAA (Deep Learning Anti-Aliasing).</li><li>AMD FSR 3.1.6.</li><li>AMD FSR 4.1.2.</li></ul>Upscaling Quality / Preset:When supported by the selected upscaler, provide the following options:<ul><li>Native AA (1.0x).</li><li>Quality.</li><li>Balanced.</li><li>Performance.</li><li>Ultra Performance.</li></ul>Native Anti-Aliasing options:<ul><li>DLAA: Use NVIDIA's Deep Learning Anti-Aliasing at native resolution, focusing on image quality and reducing jagged edges rather than increasing FPS.</li><li>FSR Native AA: Use AMD's native-resolution anti-aliasing mode (1.0x scaling) to improve image stability and reduce aliasing without rendering at a lower resolution.</li></ul><h3>Additional behaviour and considerations</h3><ul><li>Keep <code>Sharpness</code> as an independent setting, allowing users to fine-tune the final image regardless of the selected upscaler.</li><li>Preserve the existing Catmull-Rom and Lanczos options as lightweight alternatives.</li><li>Automatically detect GPU and driver compatibility. Unsupported options should be disabled or hidden rather than causing rendering errors.</li><li>Where supported, allow FSR 4.1.2 to be selected, with FSR 3.1.6 available as an alternative when the hardware or driver does not support the newer version.</li><li>When DLSS or FSR is active, the selected quality preset should determine the internal rendering resolution. Avoid applying the existing manual resolution scaling on top of the upscaler, which could result in unnecessary double scaling.</li><li>Temporal upscaling requires the appropriate rendering information, such as depth buffers, motion vectors and temporal jitter, to be provided by the Vulkan renderer.</li></ul>The intention is to give users access to modern reconstruction technologies while retaining the existing scaling methods as fallbacks.<div><hr></div><h2>Controls Tab: Controller Layouts and Button Mapping</h2>The Controls tab should provide a more complete input configuration experience, allowing users to select their preferred controller layout or keyboard configuration.In addition to individual button and key rebinding, it would be useful to introduce predefined input profiles for the most common controller layouts.<h3>1. Input Layout Presets</h3>Add a <code>Controller Layout</code> selector with the following profiles:<ul><li>Original (Nintendo / Switch): Preserve the original Nintendo button arrangement.<ul><li>Bottom: B</li><li>Right: A</li><li>Top: X</li><li>Left: Y</li></ul></li><li>Xbox: Use the standard Xbox button arrangement.<ul><li>Bottom: A</li><li>Right: B</li><li>Top: Y</li><li>Left: X</li></ul></li><li>PlayStation: Provide the familiar PlayStation button arrangement and symbols.<ul><li>Bottom: Cross (X)</li><li>Right: Circle (O)</li><li>Top: Triangle (△)</li><li>Left: Square (□)</li></ul></li><li>Keyboard & Mouse: Display keyboard and mouse bindings instead of controller button labels. Preserve the existing keyboard defaults, such as WASD for movement and the arrow keys for camera controls, while allowing the user to rebind individual actions.</li><li>Custom: Allow users to define their own button arrangement without being restricted to the predefined layouts.</li></ul><h3>2. Button Mapping and Rebinding</h3>The Controls page should display the available game actions alongside their assigned inputs.Suggested layout: Game Action | Gamepad Input | Keyboard / Mouse Input -- | -- | -- Movement | D-pad / Left Stick | WASD Camera | Right Stick | Arrow Keys Action / Confirm | Configurable | Configurable Cancel / Back | Configurable | Configurable Other game actions | Configurable | Configurable Each input should be individually configurable.<ul><li>Selecting an input and pressing the desired controller button or keyboard key should assign it to that action.</li><li>Prevent accidental duplicate assignments, using the existing swap behaviour where appropriate.</li><li>Allow users to clear an assignment and restore the default configuration.</li><li>Preserve independent controller and keyboard bindings.</li></ul><h3>3. Interface and Visual Feedback</h3><ul><li>Display the appropriate button symbols depending on the selected layout: Nintendo, Xbox or PlayStation.</li><li>Update the button labels and visual prompts throughout the Controls interface to match the selected controller profile.</li><li>For Keyboard & Mouse, show the actual assigned keys instead of controller symbols.</li><li>Clearly highlight the currently selected action and its assigned input.</li><li>Keep the existing visual style of the redesigned Options menu, including its gold selection highlights and detail panel.</li></ul><h3>4. Configuration and Persistence</h3><ul><li>Save the selected controller layout and custom bindings in <code>hookshot_options.ini</code>.</li><li>Changing between predefined layouts should apply the corresponding mapping without unexpectedly destroying the user's custom configuration.</li><li>Allow users to switch between layouts at any time.</li><li>Keep the selected layout and individual bindings after restarting the game.</li></ul>The idea is to make controller configuration more intuitive, especially for players coming from Xbox or PlayStation, while preserving the original Nintendo controls and providing complete keyboard customization.This should build on the existing input rebinding and controller layout work introduced in PRs #350 and #372, extending it with PlayStation support and a more complete Keyboard & Mouse profile.</body></html> </body> </html> <img width="1672" height="941" alt="Image" src="https://github.com/user-attachments/assets/2d6e7ea3-2ad7-4fcf-b7d0-8a2aa4981b74" /> <img width="1672" height="941" alt="Image" src="https://github.com/user-attachments/assets/bad8f109-0759-4212-ad8f-d9c10ec56fca" /> <img width="1672" height="941" alt="Image" src="https://github.com/user-attachments/assets/9e2522e9-2617-46c1-9c4b-55b2a9412f4e" /> ### Anything else _No response_

Bilau commented

2026-11-08 23:03:21 +00:00

(Migrated from github.com)

Incredible; if this menu were implemented, it would easily be the most beautiful and usable menu of all—highly recommended.

NotRexed commented

2026-11-09 05:57:45 +00:00

(Migrated from github.com)

Thanks for the idea. Feature requests are now collected in #1007, which lists this one with a link back here, so closing it in favour of that list (this is not a decision against the idea).

Commenting is not possible because the repository is archived.