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

Explore in Desktop Mode needs update #99

Open
JulianGro opened this issue Nov 25, 2020 · 7 comments
Open

Explore in Desktop Mode needs update #99

JulianGro opened this issue Nov 25, 2020 · 7 comments
Labels
needs more info Severity: Low This is an optional enhancement

Comments

@JulianGro
Copy link
Contributor

JulianGro commented Nov 25, 2020

Explore in Desktop Mode could use an update, so it can be linked in the Create App vircadia/vircadia-native-core#880
https://docs.vircadia.com/explore/get-started/desktop.html#create-and-edit-mode
I suggest renaming Explore in Desktop Mode to Controls in Desktop Mode as it only contains controls and it makes the keyboard shortcuts a little easier to find.

@daleglass
Copy link
Contributor

Just a rename or something else?

@daleglass daleglass added the Severity: Low This is an optional enhancement label Jan 2, 2021
@JulianGro
Copy link
Contributor Author

A lot of new shortcuts are missing. Also at least some functions need a description.

@Penguin-Guru
Copy link

Second link is dead.

@JulianGro
Copy link
Contributor Author

Updated

@Penguin-Guru
Copy link

Yeah... Why is this called "Explore"?

@Penguin-Guru
Copy link

Penguin-Guru commented Nov 22, 2021

The available controls do depend on which mapping is loaded. For example, standard_navigation or standard_nomovement. That might be worth mentioning.

Also note that some controls are added by scripts, like pressing escape to toggle Away status. They aren't all defined in one place.

The intro/tutorial world new users are eventually connected to has a sign that shows the controls-- that should probably also be updated to match the docs once the docs are complete. It might even be worth having that sign dynamically identify mappings for the user's current input device(s).

@Penguin-Guru
Copy link

Penguin-Guru commented Nov 22, 2021

I think it's worth considering whether "Desktop Mode" should actually be introduced to users as a mode. There is no logical reason why nobody wearing a V.R. headset would ever want to use a keyboard and mouse, or nobody using a desktop monitor would ever want to use V.R. controllers. I know there are some differences in the code depending on whether a headset is detected, so it is reasonable to call it a mode in the technical sense, but I assume there aren't many differences in the actual U.X. aside from the I/O configuration settings in the U.I. and the fact that some settings might or might not be applied (which should be obvious). Using different hardware seems more like using a different platform than a different application mode.

The web page detailing the V.R. controls isn't titled "V.R. Mode".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs more info Severity: Low This is an optional enhancement
Projects
None yet
Development

No branches or pull requests

3 participants