Dave Edwards
My feedback
-
139 votesDave Edwards
supported this idea
·
-
57 votesDave Edwards
supported this idea
·
-
10 votes
An error occurred while saving the comment Dave Edwards
supported this idea
·
-
24 votesDave Edwards
supported this idea
·
-
58 votesDave Edwards
supported this idea
·
-
15 votesDave Edwards
shared this idea
·
-
21 votes
An error occurred while saving the comment Dave Edwards
commented
Optionally show the location and field of view of sensors within the Home environment, including where they overlap. This would allow the user to get a feel for their orientation in their real environment, and to also get an idea about how optimal their sensor setup is.
Also consider showing sensor issues through model effects (e.g. a sparking sensor might indicate that it's having trouble).
Dave Edwards
supported this idea
·
-
478 votesDave Edwards
supported this idea
·
-
40 votesDave Edwards
supported this idea
·
-
244 votesDave Edwards
supported this idea
·
-
4 votesDave Edwards
shared this idea
·
-
73 votesDave Edwards
supported this idea
·
-
369 votesDave Edwards
supported this idea
·
-
255 votesDave Edwards
supported this idea
·
-
477 votesDave Edwards
supported this idea
·
Agreed -- but introduce the concept of a generic 'viewport'. This would be a window that's not yet bound to an application. When you load up your game / app, you bring up the desktop, select your app and fling it into the viewport.
Further, create an SDK that allows the game to expose a number of 'scenes' that the user can bind to particular configurations. The game can then tell the Oculus runtime which scene is active and the configuration bound to that scene would show. This would allow you to have different setups for menus and cockpits, etc. Viewports would be named so that when you switch configuration, the app persists but the viewport moves.