Original Discord Post by boomslanghegemony | 2024-08-26 18:51:26
Greetings. I’ve been using and promoting Convai from it’s introduction. Initially I found it easy to use. Just drag in the sample scene and then transfer scripts and setup to my characters and player. I just hid the UI canvas and everything worked great. Sadly the Unity asset is now way too complex and it changes the Unity workspace, hides panels and is impossible to adapt to my already set up Quest 3 VR project. It’s a bit of a step back for me. Does anyone have a methodology to return to the old days of the original ‘all in one’ package? Amazing product BTW and I get the impression InWorld is struggling so that’s good? Maybe, but I wish everyone well.
I have an existing Android project for the Quest 3. It works great. I have now got the Convai stuff working in it (just in the last hour) by importing the very basic scene contents. I remembered a few things about setting up the player and NPC and that worked!! My final challenge is the equivalent of holding down ‘T’ to talk on the Quest controller. I’m using the Controller Buttons Mapper from the Meta Building Blocks and that works great but I’m not sure how to map a trigger or button to the push to talk routine? I’m sure it’s dead simple. Thanks for your response!
,
