PICO.pdf

PICO How to guide Version 08/23 Table of Content Ctrl + Click on hyperlink to access content • 1. Setting Up • Equipment • • • • • • • • • • Headsets Headset Visual Comparison Controller Visual Comparison Setting Up Headset Adjusting IPD • PICO Neo 3 • PICO 4 Factory Resetting – Demo Logging i...

PICO How to guide Version 08/23 Table of Content Ctrl + Click on hyperlink to access content • 1. Setting Up • Equipment • • • • • • • • • • Headsets Headset Visual Comparison Controller Visual Comparison Setting Up Headset Adjusting IPD • PICO Neo 3 • PICO 4 Factory Resetting – Demo Logging in Installing and playing application Enabling Dev Mode PICO LINK to PC (Steam) • 2. Testing • Recording footage • What is ADB? • ADB - Pulling Logs • Pulling Media • Sideloading APK • 3. Pico Functionality Review • Categories • PICO Compliance (5 slides) • What to do? Headsets There are two different devices available: • PICO Neo 3 • PICO 4 Primary difference between PICO Neo 3 & PICO 4 is the aesthetics and hardware. Setup and application installation should be identical between devices. Headset Visual Comparison To turn on the devices, the hold the power button down for approximately 2 seconds. To turn them off hold the power button down for approximately 5 seconds. PICO Neo Link 3 • Black and white passthrough • Power button located on the top of the headset. PICO 4 • Full colour passthrough • Power button located on the right hand side of the headset below the strap. Controller Visual Comparison PICO Neo Link 3 • Battery replacement is completed similarly to the Quest devices PICO 4 • Small latch that removes the battery compartment Setting up headset To setup each headset all that is required is to plug the headset into a power socket and press the on button. If this is the first time the headset has be setup, the instructions will then be shown on screen in headset. Adjusting IPD PICO Neo 3 IPD stands for Inter Pupil Distance. All headsets will allow the user to adjust it ether via a wheel or a slider. Adjusting it allows the user to change the clarity for the screen. Adjusting the IPD will also provide addition comfort and decrease the likelihood of the tester becoming nauseous. To adjust the IPD for the PICO Neo 3, the user must manually move the lenses between: • The inner position (58mm) • Middle Position (63.5mm) • Outer position (69mm) Adjusting IPD PICO 4 To adjust the IPD you will have to do the following: 1. Access Settings menu 2. Locate the IPD/Display tab 3. Adjust the IPD using the plus or minus buttons The user may receive a warning if the IPD decreases bellow 62.5mm as the lenses may start to touch the testers nose. Factory resetting - Demo To completely reset the headset, the user must first be logged into an account. This should not be done unless told to by a lead. 1. Once logged in, access the settings menu 2. Go to the general tab 3. Select the subheading named “Factory Reset” 4. Following the instructions given will factory reset the headset. Watch video for further info. Signing in Login in will only require the following: • The headset itself • An email that the lead should provide to you NB: Unlike the Meta devices which require a phone, you can sign in directly to the PICO device. This should be identical for both PICO Neo 3 and the PICO 4 device. Once installed, the user should have access to all areas of the device. Installing and playing application To install the application, the user must locate the application within the library and select download. The library button will appear on the bottom bar on the home screen and will look like a square made of nine smaller squares (Pointed out on the image on the right). If the application is not in the library, the user must do the following steps: 1. Select “Store” 2. Select search and enter the titles name 3. Enter the titles store page 4. Press “Get” or “Download” and wait until the application installs Enabling Dev Mode Developer mode will allow the user access to options that are unavailable to other users. It allows the user to enable graph overlays and extract data from the headset. Without it, we will be unable to do the above. To enable this feature, follow the steps below. To enable developer mode on the PICO Neo 3 and PICO 4, you will need to do the following: 1. Head to "Settings“. 2. Select "General" tab and select "Software Version“. 3. Select "Software Version" 8 times until the developer option appears. 4. Select "Developer" to find available developer options. 5. You can then enable USB debugging. PICO LINK to PC (Steam) Headsets can also be used to link to Steam. This will only be used in rare occasions. PICO NEO 3 PICO 4 • To do this, you will require the cable and screwdriver that is located within the BOX Marked DP, PICO LINK Software and a Steam account. • To do this you will require a USBC Cable. 1. Connect the cable provide to the headset and screw it in place using the given screwdriver. 2. Connect the other end of the cable to the PC. 3. Open the PICO Link Software and log into steam account. 4. Go onto the headset and enable the DP connection. 5. Observe the Steam VR headset connecting without issue. 1. Connect the USBC cable to both the PC and the Headset. 2. Open the PICO Link Software and log into steam account. 3. Go onto the headset and enable the connection. 4. Observe the Steam VR headset connecting without issue. Recording footage There are multiple ways to record (Dependant on which headset you are using, and capture media on the headset. On the PICO 4, there is a dedicated button on the right controller with a picture of a camera. If you press the button once, it will take a snapshot, and holding it down will start a video recording To Record on PICO Neo 3 the user must press the dash button and select the record button. This is the same for taking photos. What is ADB? “Android Debug Bridge (ADB) is a command-line tool included with the Android SDK that is the main tool used to communicate with a Meta Quest headsets during all stages of development. ADB is a highly versatile tool required to install apps and issue other important commands from the computer to the headset.” – Developer Oculus More information can be found here: Use ADB with Meta Quest: Native/android | Oculus Developers ADB - Pulling Logs You can use ADB commands using CMD: 1. To do this, you will need to have "platform tools" downloaded and placed in a location on your machine. This is found on the Android Developer website. 2. Once the above is completed, plug in the HMD to the computer and allow all permissions that appear inside the headset. 3. To open CMD via platform tools, you will need to open the folder, and type "cmd" into the file directory tab in file explorer. 4. Hit "Enter", and CMD will open 5. You can then type in "adb devices", which will list any devices currently connected to the PC. If it is not authorised, it will say "unauthorised". If this is the case, simply place on the headset and authorise via the pop up. Pulling Media All that is required is a USB cable: 1. Plug the device into the PC 2. Open file explorer on the PC (Either search for it or click it on your PC's taskbar) 3. Navigate to "This PC" 4. Locate the PICO device within the file explorer 5. Enter either Screenshots (For images) or Movies (For Videos) 6. Locate the required file 7. Transfer the file from the PICO and place it onto the desktop (You can copy it over by dragging it or right click copy/paste) Sideloading APK Sideloading an APK (Android Package Kit) may be required if the application does not have a store page at this time. Sideloading is the process of loading the application file onto the headset via ADB commands. To do this, Developer mode must be enabled, and the headset must be connected to the PC. Please refer to Slide 12 for enabling this. Next, the user must use the ADB commands to install. This is as follows: 1. First the user must download and locate the Platform tools on the PC (This is found on the Android Developer website.) 2. 3. Start the Command prompt from within the file Then the user can enter the command “adb devices” as this will ensure that the headsets are connected After that, the user can enter “adb install “Build.APK”” which should install the build without issue 4. Pico Functionality Review Pico has certain compliance checks called "Pico Functionality Review". The categories are listed below. PACKAGE SOUND PERFORMANCE SYSTEM FUNCTIONALITIES INPUT PLAY AREA APP FUNCTIONALITIES Pico Compliance (Part 1) Package • The app's Icon should display correctly after app installation • The app icon and name should be consistent with that uploaded onto the PICO Developer Platform • The app name should be able to alter according to system language settings Sound • The default volume should be clearly discernible at 50% of the device volume. Sound quality should be high without abnormalities such as harshness, stuttering, or broken sound Pico Compliance (Part 2) Performance •The frame rate of all app content needs to be at least 72Hz •On a fully charged device, the app can run for 45 minutes without triggering the low battery warning •The app can run for 45 minutes without triggering the overheating warning •The VR screen or Loading screen is displayed within 5 seconds after the app starts •After installing and keeping the app running for 45 minutes, there should be no interruptions such as crashes, freezes, blurred screens, and unresponsiveness System •Standalone apps should pause and the previous progress should be resumed when users return to the app •The app must not contain any interruptive logic that impedes user experience or require information that is not available to users •If the app requires network connection for use, there needs to be a clear message to users when there is no network connection •For in-app downloadable content, the content must continue to be downloaded when users take headsets off •There is an appropriate distance between the UI elements and the eyes to avoid potential discomfort •For multiplayer games, users do not exit the app when they take headsets off or press the Home button •Supports monocular screen capture/recording when the app is running, during which the audio is normal and no abnormalities shall occur to block the app process •Supports monocular screen casting when the app is running, during which the audio is normal and no abnormalities shall occur to block the app process •Supports fast monocular seethrough when the app is running, during which the audio is normal and no abnormalities shall occur to block the application process •Users are able to reset the facing direction using the Home button Pico Compliance (Part 3) Security •User entitlement checks are active for the application •The app should be able to apply to users for the minimum Android permission as needed and should not be able to apply for permissions not supported by PICO VR headsets Tracking •The play mode described in the app's metadata must be one of the following: sitting, standing, space tracking Input •For app menu design, users should be able to call out by pressing the button (APP) on the controller or HMD menu •Users should be able to complete a pick-up action by pressing the Grip button on the side of the controller •Controller •Hand/Controller models in the app should be in the same position and orientation as the physical controllers in the real world •Haptic feedback is enabled in scenarios such as collision and shooting to enhance the immersive experience •Interactions with the app are in line with user experience •Users are provided with illustrations of recommended hand gestures, such as how to grip and hold in specific scenes and which buttons to use for interaction •In-Device Screen •The scene movement in the virtual world should match users' head movements in the real world •The in-device screen should completely, accurately, and clearly display the virtual spaces where users are located Pico Compliance (Part 4) Play Area • Application implements supported modes of play area • Application behaves appropriately when users exit the designated play area • A clear, adequate, and prominent safety notice is displayed if the play area is detected to be disabled In-app Functionalities • In-app functionalities work well and there is no disruption • All in-app functionalities have the necessary tutorials and guidelines • The app does not rely on Google Play services • The number and quality of content/functionalities/play modes in the app should not be lower than that on other device platform versions • App progress stored by users must be saved • When the app displays information about the headset or controller models, PICO hardware is displayed • The default language must match the system language • UI and text should be displayed correctly • In-app UI, text, model, and screen should maintain good visual sense and clarity • Controller positioning must match the hardware's positioning • Controller operation should conform to user actions • User generated leaderboard records must be saved • Text input must support the language of the target region Pico Compliance (Part 5) Online Functionalities • • • • • • • • • Users can remove friends from their friends list Friend information is displayed correctly Users can invite friends to play games (if supported) Users can chat with friends (if supported) In multiplayer mode, single matchmaking takes a reasonable time. If it takes too long, a clear notification should pop up or the matchmaking is automatically cancelled User can create/close/join multiplayer rooms Voice chat works as expected in multiplayer scenarios Voice chat can be turned on/off through in-game settings (if supported) Voice chat is not affected by Bluetooth connection/disconnection Pico Compliance (Part 6) • When finding issues relating to these cases they will always be marked as a critical issues. • This is as these are the PICO’s VRC case equivalent. • As such, these sections should be tested first before progressing onto the main test rail. • If at any point you find an issue relating to these cases, please ensure that they are reported immediately to the team lead. We want to keep this guide up to date and relevant for all departments. Want to add or edit some information? Want to remove outdated information? Send an email to [email protected] with the subject: How to guide – Suggestion – [HowtoguideName]