Normcore Setup not working on Headset
So i followed this tutorial https://www.youtube.com/watch?v=e69p60l07JM&list=PL6polqxDd8aXAfcjQcVu-auZ83jE2cWVt&index=1 , i was able to build in scene and the logs showed that i was connected to normcore the normcore avatar even shows. But then when i build and load to my VR headset nothing happens.
I have also attached the log issues incase
Black Whale Studio - XR Tutorials
YouTube
Part 1: Normcore Introduction & Setup - Make a Multiplayer VR game
In this new series, we are going to show you how to create a VR multiplayer game with Normcore. We will cover the basics such as the Avatar setup with the XR Interaction Toolkit, moving around and grabbing, as well as advanced features such as setting nicknames, changing the avatar's color, and muting the avatar on demand.
In this video, we wil...
13 Replies
Hi @GreenwoodRex. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry to hear that you're having trouble with setting up Normcore on your VR headset. Based on the information provided, it's hard to pinpoint the exact issue. However, there are a few things you could check:
1. Entitlement Check: If your app quits immediately on launch, it could be due to the entitlement check failing. Make sure the Meta account used by your Quest has been added to the release channel for your Oculus App ID. You can find more information about this in the Meta Avatars Setup Guide (https://normcore.io/documentation/guides/meta/meta-avatars-setup#set-up-meta-avatars).
2. RealtimeComponents: Normcore uses metadata on the prefab to connect RealtimeComponents on all clients. Make sure you're not trying to add RealtimeComponents at runtime as this is not supported. You can find more information about this in the Common Questions (https://normcore.io/documentation/realtime/common-questions#can-i-add-realtimecomponents-at-runtime).
3. App Key: Ensure that you've added your App Key to the Realtime component. This is necessary for the "Meta Avatar Player" to spawn. You can find more information about this in the Meta Avatars Setup Guide (https://normcore.io/documentation/guides/meta/meta-avatars-setup#set-up-meta-avatars).
If you're still having trouble, I recommend reaching out to the Normcore community on their Discord (https://normcore.io/discord) or forum (https://forum.normcore.io/) for further assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
<@638425022884478997> kapa.ai is still learning and improving, please let us know how it did by reacting below
are you using the openxr plugin?
if yes then read this https://discord.com/channels/393839515074297858/1243564631482695751/1243607527053332480
it fixed it for me
but remember to check that force remove internet is set to off before every build
because it tends to turn back on after a while
what do the device logs show?
nope
i haven't checked, let me do that
where do i find this?
oh its something in the open xr plugin
oh yes it was, sorry because i always use oculus i didn't check
i'm going through the solution
if i just change to oculus will that solve the issue tho?
see what the device logs say first
sorry if i sound dumb but how do i check device logs 🥲
the way i do it is i connect my quest to my pc , open sidequest and select the logcat option
use debug as a filter and enter unity in the searchbar
alright
oh thanks i've seen it
@MasterOX 水 there are several messages in the logs so is there anything specific i should be looking for?
anything related to normcore
see what they say when its supposed to connect you to the room
@MasterOX 水 i was able to solve it, i didn't do anything really i first did what you initially told me to which was to diable openxr from force removing internet permissions (test failed)
then i made sure that internet was required in the player setting configuration(test failed)
then i made a clean build (test failed)
then in the adb logcat i searched "normcore" and debugged and started it during the build process and after i loaded onto the quest it finally worked.
I went throught this same process in a new project to make sure i new what exactly the issue was
Thanks @MasterOX 水 💯