There are multiple steps involved in the review process, and you should receive notification throughout each stage of the review. If you have concerns about a deadline that you need approved by, we recommend submitting for review two to three weeks in advance.

While it is not a requirement to use the release channels, we recommend that you manage your builds in this way. This is the most effective method of deploying to specific users for testing as well as managing different builds.

GearVR

Samsung S7E: SM-G935A (USA AT&T)

Samsung S7: SM-G930A (USA AT&T)

Samsung S6: SM-G920A (USA AT&T)

Samsung S6E: SM-G925A (USA AT&T)

Samsung Note 5: SM-N920A (USA AT&T)

Samsung Note 4: SM-N910A (USA AT&T) (If your app supports Note 4)

Rift

NVIDIA GTX 970 / AMD 290

Intel i5-4590

8GB+ RAM

We require a variety of artwork so that your content looks beautiful and compelling across the Oculus ecosystem. Art guidelines are located here.

Sometimes there is a lag between approval of your app and display in the Store. Your app will go live the morning after approval has been granted.

Please contact the store submissions team at submissions@oculus.com to request price changes for your app.

Please contact the store submissions team at submissions@oculus.com referencing the need to suspend distribution of your app.

Samsung Galaxy S9

Samsung Galaxy S8+

Samsung Galaxy S8

Samsung Galaxy S7E

Samsung Galaxy S7

Samsung Galaxy S6

Samsung Galaxy S6E

Samsung Note 5

Please reach out to our parent company, Facebook regarding any finance related questions. You may contact them here.

Check your player settings and make sure "Virtual Reality Supported" is checked and that "Oculus" is in the list of supported devices.

There are two things you can look into to solve this problem:

1. Your copy of OVRPlugin.dll is modified or corrupted in some way.
2. You have tried running an executable that has non-english Unicode characters in the path name.

Check and make sure that you have added both OVRManager and OVRPlatform script files to your scene.

Right here.

The headset must be on your head for touch haptics to be activated.

Not typically. Depending on the type of projector being used this may be possible. Please see the forum thread here for more information.

Unity’s render statistics report a higher FPS than reality because they track all cameras. You should only take into account the Oculus script’s FPS reading.

Please see the blog post on optimizing for Gear VR here for a good break down of best practices.

Please see the forum post here regarding setting this up. There are also instructions regarding setting up a basic list of players in text format as well.

The command to set the pixel density in UE4 is 'hmd pd'. You need to detect what phone you're running on and scale it up to increase the quality.

Yes, but not unless you build from source. You can use Wwise and our plugin to render ambisonics and Media Framework to render video.

No. The stereo cubemap won’t line up with 3D content when the user’s head pose has any pitch or roll.

There are two ways to render a portal: rendering to a texture for the content on the other side of the portal and regular render and stencil in the foreground geometry. The second approach is definitely going to work better performance wise on the Gear due to bandwidth limitations.

Here are some helpful links:

https://wiki.unrealengine.com/Portals

https://answers.unrealengine.com/questions/49911/recreating-udks-utportals.html

We currently do not recommend using HDR on mobile platforms. This is because HDR consumes far more texture bandwidth than the regular pipeline.

In unreal engines 4.13+ there is the ability to use a cubemap overlays to perform this function.

You will need to tick the LeftTexture box in Cubemap Overlays Properties to enable it.

See the documentation here:

Yes. See the following instructions: All the parameters that in blueprint are given to AddLoadingSplashScreen can also be written in the DefaultEngine.ini file of their game (Config/DefaultEngine.ini), as shown:

(most of those parameters are optional)

[Oculus.Splash.Settings]

TexturePath=”path”

DistanceInMeters=translation (vec3)

Rotation=rotation (quaternion)

SizeInMeters=size (vec2)

DeltaRotation=delta (quaternion)

The General Data Protection Regulation (GDPR), which goes into effect May 25, 2018, creates consistent data protection rules across Europe. It applies to all companies that process personal data about individuals in the EU, regardless of where the company is based. Processing is defined as anything related to personal data, including how a company handles and manages data, such as collecting, storing, using and destroying data.

Each company is responsible for complying with the GDPR, just as they are responsible for complying with the laws that apply to them today.

Developers must implement and disclose their own complete and accurate privacy policy explaining how they collect, use, and disclose data as required by applicable law. Because each developer has different practices and uses information in different ways, using Oculus's privacy policy would not be appropriate.

Your privacy policy must explain your practices regarding the collection, use and disclosure of data, and we cannot write it for you. We suggest you contact your legal team or seek external counsel

No. We do not “process” data on behalf of our developers under the definition of the GDPR.

No. We do not offer a Data Processing Addendum, because we do not process data on behalf of our developers.

Whether or not your app is compliant depends on many factors that we cannot evaluate for you. It is your responsibility as the developer to make sure that your app complies with the GDPR.

In light of the GDPR, we are offering new tools and information to people who use our services to help them better control their privacy and understand how Oculus uses information. For information about some of the efforts we're taking to make sure we are complying with the GDPR, see our blog post here.