Viewport Orbit Snap Modifier key conflicts with Modo navigation scheme, and is still active after deletion in Editor Settings

[Nodragem]

Tested versions

4.6rc1

System information

Godot v4.6.rc1 - Windows 11 (build 26200) - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2060 (NVIDIA; 32.0.15.8183) - Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 threads) - 15.84 GiB memory

Issue description

I deleted the ALT key in the shorcut menu, and Godot still snaps the view when I press ALT.

NOTE: I am using ALT for orbitting the viewport, ALT+CTRL to zoom and ALT+SHIFT to pan (Modo 3D Navigation), so that's quite problematic 😄 !

Steps to reproduce

Delete the ALT key from the shortcut menu for "Viewport Orbit Snap Modifier key".

Try using ALT to snap the view, and it still works.

Minimal reproduction project (MRP)

Default project is enough.

[ryevdokimov]

The issue seems to be rather, that when deleting the shortcut, the behavior defaults to always snapping regardless of what key is or isn't pressed.

[Nodragem]

could we get this fix merged before release? as this issue makes the viewport unusable for people using the Modo 3D Navigation controls. I really thought it would be in RC2!

[akien-mga]

I assume you can work it around by assigning a placeholder shortcut that you won't hit when navigating (e.g. Windows key or ;) instead of deleting the default one.

So this doesn't seem a critical issue as it happens only on a non standard config, has a workaround, and thus not a priority at RC stage (with the potential for regressions that come from any last minute change).

[Nodragem]

The workaround is working, didn't think of that 😄 yet, I would not say that my config is non standard: the Modo navigation scheme is part of the standard options given to the users in the editor settings.

[ryevdokimov]

We should probably track this as at least a noncritical release blocker though, since it is technically a DX regression that affects Modo and Maya users. My PR doesn't actually address the real nature of this regression in that there is a default conflict with those navigation modes that now requires a work around that might not be obvious. That will require a different fix, separate from the linked PR.

[Nodragem]

As I like to say, we need to be careful each time we want to use a modifier key; they tend to create conflicts! 😸

The Modo scheme is essential when you use a pentablet (no middle button, no scrolling wheel), so I would agree with @ryevdokimov that this needs to be at least tracked, even if not prioritised at the moment.

[akien-mga]

What change caused the issue? Is it a regression in 4.6?
If so, and the proposed fix doesn't fully solve the problem, we should probably revert what caused the regression.

[ryevdokimov]

Viewport orbit snapping was added in 4.6 with this PR: #111509

I just created another PR, that combined with the PR linked to this issue will address the regression: #115298