问题描述
我正在尝试为 Oculus Quest 开发应用然而我在途中遇到了很多问题.该应用程序基本上包括一个房间和传送.我遇到的问题在 unity 2018.3.12 和 2019.1.8 上都发生.
I'm trying to develop an app to Oculus Quest yet i encounter many issues on the way.the app basically consist of a room and teleportation.the issue i encountered happens both on unity 2018.3.12 and 2019.1.8.
我使用 Oculus 集成 v1.35 创建了一个在 Quest 上按预期工作的应用程序.但是，当重新导出并安装到全新的 Quest 设备时:
I created an app that did work as expected before on Quest using Oculus integration v1.35.however, when re-exported and installed to a brand new Quest device:
- 在拒绝工作之前工作的传送
- 按下一个控制器上的按钮会隐藏另一个控制器.
- 手部活动受限
- 即使目标设备设置为 Quest，我仍然(在 v1.35 上)看到 oculus 的控制器
- 它只在导出到任务时发生，在 rift 上它工作得很好.
来自 Oculus 论坛中的帖子
from the posts in Oculus Forum
https://forums.oculusvr.com/developer/discussion/comment/702108#Comment_702108
似乎存在固件问题(但您应该也遇到了，不是吗?)
it looks like there is a firmware issue (but then you should be encountering that too no?)
我尝试过的事情:
从头开始一个新项目:
Start a new project from scratch:
遵循标准教程和文档https://www.youtube.com/watch?v=qiJpjnzW-mw&t=1s
https://developer.oculus.com/文档/任务/最新/概念/book-unity-gsg/
根本看不到手，也没有实现瞬移，据说目前v1.39有bughttps://forums.oculusvr.com/developer/discussion/79144/hands-not-showing-up-with-localavator-unity
could not see the hands at all, and no teleportation was implemented, it is said that there is a bug in current v1.39https://forums.oculusvr.com/developer/discussion/79144/hands-not-showing-up-with-localavator-unity
我尝试同时使用 unity OVR 资产和以下插件https://assetstore.unity.com/packages/tools/input-management/vr-movement-system-for-oculus-47292
I tried to use both the unity OVR assets and the following pluginshttps://assetstore.unity.com/packages/tools/input-management/vr-movement-system-for-oculus-47292
https://assetstore.unity.com/packages/tools/input-management/vr-arc-teleporter-61561并且在所有 3 中都遇到了相同的问题.
https://assetstore.unity.com/packages/tools/input-management/vr-arc-teleporter-61561and in all 3 encountered the same issue.
是否有人遇到过与所描述的类似的问题?
did anyone encounter any issue similar to what's described?
如前所述，我希望看到 ands 和控制器，以及附加到触发器上的代码被执行.这一切都没有发生.
as said, i expect to see the ands and controllers, and the code attached to the trigger press executed. none of this happened.
作为一些测试，(因为我没有其他任务)我在这里导出了一个构建和共享.如果您尝试过并且在您的任务中运行良好，请发表评论https://www.dropbox.com/s/uvcmhyar2qljb19/k14.apk?dl=0
as some test, (since i do not have another quest)i exported a build and sharing here.please comment if you have tried it and it workd fine on your quest or nothttps://www.dropbox.com/s/uvcmhyar2qljb19/k14.apk?dl=0
推荐答案
感谢所有帮助者.
更新1:如果手根本没有出现，那是因为 Oculus 集成 1.39 有问题恢复到 1.38https://developer.oculus.com/downloads/package/unity-integration-存档/
update 1:if hands don't appear at all, its because Oculus integration 1.39 is buggyrevert to 1.38https://developer.oculus.com/downloads/package/unity-integration-archive/
第二个:
问题是最新的固件更新添加了GO控制器支持并默认了它.所以 Quest 控制器开始以 GO 的形式出现诀窍是将 AndroidManifest 复制到 Assets/Plugins 并正确编辑它以专门定义正确的设置.您可以在此处查看建议的更改noreferr.nofol">/documentation/quest/latest/concepts/mobile-native-manifest/?fbclid=IwAR3AgasGPJFVGsz7lyzfJNfuTB8R1FOg88Quq8YZz67eQlwEFvgEMDGjSdo
the problem is that the latest firmware update added GO controller support and defaulted it.so Quest controllers begun appearing as GOthe trick was to copy the AndroidManifest to Assets/Plugins and edit it properly to specifically define the correct settings.you can see the recommended changes herehttps://developer.oculus.com/documentation/quest/latest/concepts/mobile-native-manifest/?fbclid=IwAR3AgasGPJFVGsz7lyzfJNfuTB8R1FOg88Quq8YZz67eQlwEFvgEMDGjSdo
这篇关于手在 oculus Quest 上没有按预期响应的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！