Skip to main content
motorsep
Inspiring
June 19, 2018

[Go / Gear VR] How to determine what HMD user uses ?

@imperativity

I just tested my app on Go and was instantly disappointed with the controller. It's not the same as Gear VR and I am gonna have to adjust a lot of things for it :/

That being said, now I have to know what HMD user uses and based on that select control scheme.

How can I determine whether it's Gear VR or Oculus Go in use, using Blueprints in UE 4.19.2 (or in upcoming 4.20) from Oculus github repo ?

Thanks beforehand
This topic has been closed for replies.

5 replies

MaxArch
MaxArch
Inspiring
June 19, 2018
I think you could test if the 72 Hz display frequency is available. If so its a Go
mousebear
mousebear
Honored Contributor
June 20, 2018
@motorsep Let me inquire internally to see what's the best practice here.
If you need immediate help or want additional support/context on an issue you are having with our platform or integrations: 1. Gather any and all logs , screenshots, and version numbers of relevant software (Oculus SDK, engine, etc.) 2. Please submit a ticket here through the "Contact Us" link (include what you've gathered in step 1). 3. Tag me @mouse_bear once you have done so!
Anonymous
July 20, 2018
Here's what I used to detect which device is which - just the simple "get device name" node:



Note it was changed to "Oculus Go" in 4.19. In 4.18 it was something else like "Pacific" but don't really remember now. If you're still using 4.18 just print string it out.
motorsepAuthor
Inspiring
July 20, 2018
@aussieburgerVR

Nice, thanks. How did you figure the names? (specifically why GearVR has no space between Gear and VR, but Oculus Go has space between the words)
Anonymous
July 20, 2018

motorsep said:

@aussieburgerVR

Nice, thanks. How did you figure the names? (specifically why GearVR has no space between Gear and VR, but Oculus Go has space between the words)


Just did a print string from the "Get Device Name" output while the device was connected to the Dalvik Debug Monitor before I realized the newish "Debug Canvas in Layer" VR rendering option (in project settings) makes it even easier to read your print strings while in VR :)
Terms & ConditionsAccessibility statement