Fly mode vs. Walk Mode Navigation Keyboard Controls #38561

New Issue

Sir Torx Screwdriver · 2014-02-09T16:46:23+01:00

2014-02-09 16:46:23 +01:00

System Information
(irrelevant for this issue, no need to read)
Win8.1 64Bit
Intel Xeon e3
Nvidia gtx 670

Blender Version
Broken: 15f449c

Short description of error
Fly Navigation and Walk Navigation use different bottons for up/down for no reason.
Exact steps for others to reproduce the error
The recently added walk navigation uses WASD for moving back&forth sideways movement and Q and E for moving up/down in space.
The issue here is, that the existing "fly navigation" uses R and F for exactly that!

I would suggest to give those two navigation modes the same controls by default, I'd personally prefer the R and F method, as those keys are below each other, which supposedly makes more sense than having keys that are in the same row on the keyboard. Another reason would be that most people are probably most familiar with the controls of the existing fly mode navigation.

PS: This is more of a UI inconsistency issue than a bug, if it belongs somewhere else and I'm unnecesarily cluttering the bugtracker here please let me know :)

**System Information** (irrelevant for this issue, no need to read) Win8.1 64Bit Intel Xeon e3 Nvidia gtx 670 **Blender Version** Broken: 15f449c **Short description of error** Fly Navigation and Walk Navigation use different bottons for up/down for no reason. **Exact steps for others to reproduce the error** The recently added walk navigation uses WASD for moving back&forth sideways movement and Q and E for moving up/down in space. The issue here is, that the existing "fly navigation" uses R and F for exactly that! I would suggest to give those two navigation modes the same controls by default, I'd personally prefer the R and F method, as those keys are below each other, which supposedly makes more sense than having keys that are in the same row on the keyboard. Another reason would be that most people are probably most familiar with the controls of the existing fly mode navigation. PS: This is more of a UI inconsistency issue than a bug, if it belongs somewhere else and I'm unnecesarily cluttering the bugtracker here please let me know :)

Sir Torx Screwdriver commented

2014-02-09 16:46:23 +01:00

Changed status to: 'Open'

Sir Torx Screwdriver commented

2014-02-09 16:46:23 +01:00

Added subscriber: @particleemitter

Thomas Dinges commented

2014-02-09 23:18:17 +01:00

Added subscribers: @dfelinto, @ThomasDinges

Dalai Felinto was assigned by Sergey Sharybin

2014-02-17 10:12:36 +01:00

Sergey Sharybin commented

2014-02-17 10:12:36 +01:00

Added subscriber: @Sergey

Sergey Sharybin commented

2014-02-17 10:12:36 +01:00

@dfelinto, please have a look here :)

Dalai Felinto commented

2014-02-18 03:45:29 +01:00

Added subscriber: @ideasman42

Dalai Felinto commented

2014-02-18 03:45:29 +01:00

I can't remember why we didn't change the shortcuts to the Fly Mode. @ideasman42 do you remember that?
I suspect it was because we were not showing the shortcuts, so we wanted to avoid changing known shortcuts (for fly mode).

For Walk mode it's better to use Q/E since we need the fingers free to use alt, ctrl, space. So my suggestion is to change Fly Mode to use Q/E.
Any objections?

I can't remember why we didn't change the shortcuts to the Fly Mode. @ideasman42 do you remember that? I suspect it was because we were not showing the shortcuts, so we wanted to avoid changing known shortcuts (for fly mode). For Walk mode it's better to use Q/E since we need the fingers free to use alt, ctrl, space. So my suggestion is to change Fly Mode to use Q/E. Any objections?

Campbell Barton commented

2014-02-18 04:46:27 +01:00

@dfelinto no objections.

Thomas Dinges commented

2014-02-21 01:39:55 +01:00

Changed status from 'Open' to: 'Resolved'

Thomas Dinges closed this issue

2014-02-21 01:39:55 +01:00

Thomas Dinges commented

2014-02-21 01:39:55 +01:00

This has been fixed: https://developer.blender.org/rBcbbc67a0b5759ef5153d9b18a825c42ad9a3792b

@dfelinto: "Fix #38561" should be used to auto close a report, "fix - #38561" doesn't work. See http://wiki.blender.org/index.php/Dev:Doc/New_Committer_Info#Commit_Logs

This has been fixed: https://developer.blender.org/rBcbbc67a0b5759ef5153d9b18a825c42ad9a3792b @dfelinto: "Fix #38561" should be used to auto close a report, "fix - #38561" doesn't work. See http://wiki.blender.org/index.php/Dev:Doc/New_Committer_Info#Commit_Logs

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Fly mode vs. Walk Mode Navigation Keyboard Controls #38561