-
Notifications
You must be signed in to change notification settings - Fork 218
Conversation
The spinner animation is not the final one, @keianhzo is working on the shapeshifter exported version |
There is a build fail on this merge:
|
f786c4c
to
6f7a696
Compare
Fixed |
I notice the controller icons only be shown when entering the immersive mode at the 1st time. Is it what we want? |
For now it’s displayed for 3 seconds the first time you enter immersive (on each app restart) After trying it I think it would be good to wait for a user click to dismiss the how-to information, and remove the forced time. IMO:
Thoughts? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a good approach. I think the controller images could be a little bigger maybe? |
I feel we can remove the spinner if we are showing the how-to-exit information, the spinner sometimes catches my attention other than the how-to-exit. However, if users end the information icon, WebXR pages are still loading. We should still show the spinner instead. Make the controller image bigger can let me see the words more easy. I also feel if we already allow users to press a button to end the how-to-exit information, maybe longer time like 5 secs would be great for user have more time to understand it. |
e3943e9
to
b1db18a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can remove spinners_v3.obj
, spinners_v3.mtl
, and spinners_v3.ktx
.
case ViveFocusPlus: | ||
name = "Vive Focus Plus"; | ||
break; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need a ViveFocus
also?
m.drawHandler = [=](device::Eye eye) { | ||
DrawLoadingAnimation(eye); | ||
DrawWebXRInterstitial(eye); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Looks like there are two extra spaces added?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we still want to have support for the regular Focus controller.
import org.mozilla.vrbrowser.BuildConfig; | ||
|
||
public class DeviceType { | ||
// These values need to match those in Device.h | ||
@IntDef(value = { Unknown, OculusGo, OculusQuest, ViveFocusPlus, PicoNeo2, PicoG2 }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like Device.h
needs to be updated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need ViveFocus as well
Do we have an alpha blending problem on the spinner image? I can see its rectangle background when we are going to end the animation. |
@daoshengmu @bluemarvin I implemented the flow we talked about. Let me know what you think. Feel free to change the new text |
It seems like pressing squeeze btns on Quest can't exit the how-to-exit page. |
Fixed |
I noticed that too but it seems a driver bug. It only happens with the first layer displayed on a black background. If I change the order the alpha blending moves to the first layer rendered. I'll look into it next week, we can address that as a follow-up |
|
||
// This is always false in Oculus Browser. | ||
const bool thumbRest = false; | ||
controller->SetButtonState(controllerState.index, ControllerDelegate::BUTTON_OTHERS, 5, thumbRest, thumbRest); | ||
} else { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks odd to me. This is thumbRest instead of the grip button, and thumbRest is always false. If thumbRest
will cause problems to you, Neo2 will have it too because it also has thumbRest
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can remove this commit now. I already gave a fix at #2521 by defining a new btn state BUTTON_SQUEEZE
. That makes sense for us to use it in app.
95115f6
to
a94ddbf
Compare
a94ddbf
to
6452dc9
Compare
6452dc9
to
af1f81d
Compare
Fixes #1966 Fixes #3123