FAQ

1. How do I get access to the ODK?

Please reach out to your representative at Yuga who can organise your onboarding, as part of this process you need to supply all emails that will need access to the ODK tooling.

Once you have been given access please follow the quick start guide which can be found here: https://docs.otherside.xyz/odk-documentation/documentation/quick-start-guide/getting-setup-with-odk-development

1. I am unable to Login to the ODK Launcher

Please ensure that you are logging in with the email that you have sent to your Yuga contact to get whitelisted. If this step has been completed please ensure that you are logging in via Otherside and not Msquared on the Launcher. There is also a known issue where it may take two attempts to login. If you are still facing problems then please reach out to your Yuga representative.

1. I am unable to enter admin mode within the engine.

Please review the breaking change here

For any role that you want to have access to the Inspector (historically just Director) add the Capabilities.Morpheus.InspectorEnabled capability to the GrantedCapabilities field within your data table for those roles.

1. I am unable to sign in via the Editor

Please follow the guide here: https://docs.otherside.xyz/odk-documentation/documentation/quick-start-guide/faq/guide-on-clearing-credentials

If you continue to encounter sign-in failure, please collect your unreal logs and share them in your ODK support channel.

1. I am unable to open the web overlay within my experience/or my account details are incorrect on privy on the overlay/ or I am getting errors when opening the overlay.

With the move to using Privy the way you access deployments has changed, if you go in via the Otherside Dashboard you won't go through the Privy auth process, so when access deployments please append the following link with your WorldID and ProjectID. Please note you don't need the [] on either project ID or world ID

We've noticed on rare occasion the web browser can fail to process the content URL that it's attempting to display. We're continually working to resolve these types of errors. If you do encounter this error, please toggle the web browser to resolve (pressing Tab). If the error persists, please raise it within your ODK support channel.