Make Annwvyn follow the Oculus Technical Requirement for submission of Apps to the Oculus Store

[Ybalrid]

This game engine must be a "viable option" to publish content to the Oculus Store for the Oculus Rift (and Touch) platform.

There are multiple points that may need adjustment regarding the interaction of the engine with the Oculus Platform itself.

The engine is by default only dependento on the "raw" Oculus SDK, not the Oculus Platform SDK, and this is not a problem.

The guidelines are here : https://developer.oculus.com/distribute/latest/concepts/publish-rift-app-submission/

Some of theses are dependent of the "user program", I will remove them from this list.

• [x] In-game menus must be activated with the menu button on the gamepad controller or the menu button on the left Oculus Touch controller.
• [x] When your app starts, you must target the audio device selected in the Audio Output in VR setting in the Oculus app. You only need to do this on app start.
• [x] Renders head-locked UI elements such as cursors and in-game dialog in a separate layer from the main game to avoid judder if the app misses frames or runs with Asynchronous Spacewarp. See VR Compositor Layers.
• [x] Meets all reserved interaction requirements:
  • [x] Apps must not submit frames or accept input while the Universal Menu is open.
  • [x] Single-player apps must pause while the Universal Menu is open.
  • [x] The reorientation option in the Universal Menu must reorient appropriately:
    • [x] Apps that do not use the Oculus Guardian System play area should reset the user's home position and orientation to their current position and orientation, using the built-in Oculus API functionality.
    • [x] Apps that use the Oculus Guardian System play area may use more advanced reorientation logic.
      • [x] If Oculus Guardian System bounds are not configured, re-center must work regardless of app tracking or movement type.
  • [x] The Exit to Home function must work.
• [x] Meets all functional requirements:
  • [x] Does not crash, freeze, or enter an extended unresponsive state.
  • [x] Correctly uses entitlement checks to prevent unauthorized access. See Getting Started and Checking Entitlements.
  • [x] Does not launch with a Windows Firewall interruption or a Unity configuration prompt.
  • [x] Does not contain extraneous files such as debug builds, marketing assets, or DLL libraries from other distribution platforms.
  • [x] Displays graphics and responds to head tracking within 4 seconds of launch. Longer launch times are allowed if there is a loading indicator.
  • [x] Has no data loss. All saves, settings, and content persist through the user’s experience.
  • [x] Users do not get stuck in any section. For example, if you require a login, we must be able to successfully create an account. Game levels must not have broken logic that prevents progressing to the next level.
  • [x] Does not tie animation or physics to a 90Hz frame rate. Dropped frames and asynchronous spacewarp reduce frame rates below 90FPS and cause such animations to play out of sync with the displayed frame.
  • [x] If the app supports a desktop mode, it must launch and be playable on the standard display without the use of the HMD or Oculus Touch controllers.
• [x] Meets all Oculus PC SDK and game engine version requirements:
• [x] Runs on the recommended system:
• [x] Oculus PC SDK version 1.8 or later.
• [x] Meets all performance requirements:
  • [x] Maintains 90 FPS through most of the app.
  • [x] No systemic judder. Asynchronous Timewarp can help with minor rotational judder, but your application still needs to be at 90 FPS most of the time. You should disable Asynchronous Spacewarp for performance testing because it can mask brief performance drops.
• [x] Meets all audio requirements:
• [x] Meets all graphics requirements:
• [x] All graphics resolve correctly into 3D images with no convergence issues or unusual distortion. See Binocular Vision, Stereoscoping Imaging and Depth Cues.
• [x] Has no major graphics issues. This includes z-fighting, depth conflicts, and so on.
• [x] Meets all input requirements:
  • [x] Map all the buttons required to allow a user to play through your application with all the controllers you support.
• [x] If you indicate Oculus Touch as a supported input device for this app, you must use Touch position and orientation data to either manipulate the environment or facilitate player movement. Apps that merely emulate gamepad control schemes using Touch must not indicate Oculus Touch as a supported input device and shall indicate Touch (as Gamepad) instead.
  • [x] Meets all player mode and tracking mode requirements for the modes select on your Submission Info page:
  • [x] Sitting. The app must be completely playable while seated.
  • [x] Standing. The app must be completely usable within a 7' x 5' play area.
  • [x] Roomscale. The app must be completely usable within a 7' x 5' play area with a 3-sensor experimental roomscale setup. Additionally, you must also select the 360° checkbox and meet the 360° requirements as well.
• [x] Front-facing. The app must be completely usable with the standard setup of 2 sensors on a desk. Additionally: Ensure objects on the floor can be picked up or reached even if the floor is partially occluded by the desk.
  • [x] Ensure users are never required to interact with content behind them. If the app places interactive content behind the user, the app must take some steps to keep the user facing forward. This prevents them from unknowingly occluding the sensors with their body while trying to interact with the content.
    • [x] 360°. The app must provide interactive content behind the user. If the app only provides interactive content in front of the user, it is Front-facing instead of a 360° app. Front-facing apps are already assumed to work with a 3-sensor setup, and don't need additional flags to indicate compatibility. Additionally:
    • [x] If Roomscale is selected, the app must be completely usable with an experimental 3-sensor 360 setup.
    • [x] If Roomscale is not selected, the app must be completely usable with an experimental 2-sensor 360 setup.

[Ybalrid]

So, I checked everything on the list that is either not a problem, or that is not the engine responsibility, but the actual game.

[Ybalrid]

The entitlement check is part of the Platform SDK. I don't really want to put call to a DRM system inside the engine itself. I want to have, however, a "plugin" that is an 'user-space subsystem'. - OR- Implemented by the client game entirely.

[Ybalrid]

fixed "not rendering when universal menu is up" and delegated not accepting inputs to the client game.

[Ybalrid]

Annwvyn is also following the Oculus "focus aware" directives for the futrue Oculus Core 2.0 software

[Ybalrid]

This is waiting for #105 to be dealt with