Original Discord Post by tyke_18 | 2024-08-30 07:03:18
Hi, in my MR app I’m having issues with the Convai NPC not detecting the player in order for a conversation to happen (I’m getting the Not Close Enough message or NPC Not Active message), it’s probably something I’m doing wrong but I don’t want this feature in my app if possible, the user should be able to speak to the NPC wherever they are etc, can I remove this? I’ve tried increasing the collider size so it’s really big and setting the ray size to very large and view angle to 360 but no luck.
I don’t want a Ground gameobject in my app so I’ve removed it but then the player kept falling through the floor, so I edited ConvaiPlayerMovement line 27 to this private float gravity = 0f;
Also, I don’t want to use the VR upgrade package if possible, my app is an MR app on a Meta Quest 3 which uses dynamic occlusion, I need to use Unity Standard Shader shaders and I think the VR upgrader requires URP to be installed? Another reason is because I don’t want to have to install the XR Interaction Toolkit so I can use the VR controller as an input.
My app already has code to detect the right trigger being pressed for Talk, I appreciate I could remap this in the Input Manager but there’s nothing I can see that lets me use the Menu button (I use this button)? I would prefer it if I could just have access to the code that sends the audio to the Convai servers, with Inworld I called an Inworld method called SendAudio() when the right trigger was pressed for push to talk, is there a similar method or bit of code in Convai?
Sorry for the wall of text, I’m really liking what I’m seeing so far, it’s a bit difficult learning a new SDK and API again but your docs are very good, loving the new Long Term Memory and how easy it is to implement!
Hmm my project when run in the Unity editor runs ok but when I build for Quest 3 it crashes on startup, so I can’t show you the NPC NotActive messages I get in the Quest 3 debugger window at the moment, sorry. Here is some info and a video I prepared but I need to get the Quest 3 build version working to show you what’s happening in the Quest 3, do you think the Quest 3 build is failing because of these URP warnings after I build and deploy to the headset?
-I did the manual method of setting up VR, the only package I did not install was URP (Universal Render Pipeline) as I don’t want to use these shaders.
-I chose all of the options during the import process after the ConvaiVRUpgrader package was double clicked.
-I then did Add the Convai Essentials VR prefab to your scene.
Add NPCManager and GRPCApi components to your Meta Quest Player.
Add the ConvaiHandPanelHolder object to your left hand (you can find it by searching Hiearchy).
Remove Convai VR Player.
-I have the Unity active input system set to ‘new’
-How do I install the Convai VR package without having to make my project URP? I think the package changes some settings to do with URP shaders because my avatar when applying dynamic occlusion using BiRP / Standard shader has errors and crashes the app when run in the Quest 3.
With Meta Quest Developer Hub, just tried again with VR Player deleted, crashes at start up. Yesterday it was just crashing sometimes. What do you think about the Input Manager script not listing keys/buttons etc?
,
