为什么 iPhone XR、XS 和 XS Max 不将环境图像应用于 ARKit 中的场景? [英] Why iPhones XR, XS and XS Max, doesn't apply environment image to scene in ARKit?
本文介绍了为什么 iPhone XR、XS 和 XS Max 不将环境图像应用于 ARKit 中的场景?的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
从后端下载所有内容(纹理、环境、3D 对象)到应用程序后，我以编程方式创建了一个新的 SCNScene，包含所有这些内容.
After download everything from backend (textures, environment, 3D object) into the app, I created a new SCNScene programmatically, with all this stuff.
它在所有设备上都能完美运行，但在 iPhone XR、XS 和 XS Max 上，需要环境图像的这些型号的纹理显示为黑色.好像设置了无"环境.
It works perfectly on all devices, but on iPhones XR, XS and XS Max the textures of those models, that need environment image appear black. As if "None" environment was set.
我不能发布代码或图片，这不是我的项目.我只想知道是否有人在使用 iPhone XR、XS 或 XS Max 和 ARKit 时遇到过此类问题.
I can't post code nor images, it's not my project. I'd just like to know if anyone has experienced any problems of this kind, with iPhone XR, XS or XS Max and ARKit.
奇怪的是，它不会在其他设备上发生.
It's strange that it doesn't happen on other devices.
谢谢.
编辑 1:
这是错误的痕迹，我会尽快发布有关该项目的更多信息.
Here is the trace of the error, I'll try to post more info about the project soon.
2019-02-13 11:21:33.573842+0100 BugAR[508:29509] [DYMTLInitPlatform] platform initialization successful
2019-02-13 11:21:33.769664+0100 BugAR[508:29469] Metal GPU Frame Capture Enabled
2019-02-13 11:21:33.769884+0100 BugAR[508:29469] Metal API Validation Enabled
2019-02-13 11:21:33.974845+0100 BugAR[508:29469] [MC] System group container for systemgroup.com.apple.configurationprofiles path is /private/var/containers/Shared/SystemGroup/systemgroup.com.apple.configurationprofiles
2019-02-13 11:21:33.975620+0100 BugAR[508:29469] [MC] Reading from public effective user settings.
=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState]
PID: 508, TID: 29535, Thread name: com.apple.CoreMotion.MotionThread, Queue name: com.apple.root.default-qos.overcommit, QoS: 0
Backtrace:
4 libobjc.A.dylib 0x000000021ddff534 <redacted> + 56
5 CoreMotion 0x0000000224688040 CoreMotion + 307264
6 CoreMotion 0x0000000224688574 CoreMotion + 308596
7 CoreMotion 0x0000000224688484 CoreMotion + 308356
8 CoreMotion 0x00000002246b9c64 CoreMotion + 511076
9 CoreMotion 0x00000002246b9cc4 CoreMotion + 511172
10 CoreFoundation 0x000000021eb98354 <redacted> + 28
11 CoreFoundation 0x000000021eb97c38 <redacted> + 276
12 CoreFoundation 0x000000021eb92f14 <redacted> + 2324
13 CoreFoundation 0x000000021eb922e8 CFRunLoopRunSpecific + 452
14 CoreFoundation 0x000000021eb9304c CFRunLoopRun + 84
15 CoreMotion 0x00000002246b95fc CoreMotion + 509436
16 libsystem_pthread.dylib 0x000000021e80c974 <redacted> + 132
17 libsystem_pthread.dylib 0x000000021e80c8d0 _pthread_start + 52
18 libsystem_pthread.dylib 0x000000021e814ddc thread_start + 4
2019-02-13 11:21:34.312731+0100 BugAR[508:29535] [reports] Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState]
PID: 508, TID: 29535, Thread name: com.apple.CoreMotion.MotionThread, Queue name: com.apple.root.default-qos.overcommit, QoS: 0
Backtrace:
4 libobjc.A.dylib 0x000000021ddff534 <redacted> + 56
5 CoreMotion 0x0000000224688040 CoreMotion + 307264
6 CoreMotion 0x0000000224688574 CoreMotion + 308596
7 CoreMotion 0x0000000224688484 CoreMotion + 308356
8 CoreMotion 0x00000002246b9c64 CoreMotion + 511076
9 CoreMotion 0x00000002246b9cc4 CoreMotion + 511172
10 CoreFoundation 0x000000021eb98354 <redacted> + 28
11 CoreFoundation 0x000000021eb97c38 <redacted> + 276
12 CoreFoundation 0x000000021eb92f14 <redacted> + 2324
13 CoreFoundation 0x000000021eb922e8 CFRunLoopRunSpecific + 452
14 CoreFoundation 0x000000021eb9304c CFRunLoopRun + 84
15 CoreMotion 0x00000002246b95fc CoreMotion + 509436
16 libsystem_pthread.dylib 0x000000021e80c974 <redacted> + 132
17 libsystem_pthread.dylib 0x000000021e80c8d0 _pthread_start + 52
18 libsystem_pthread.dylib 0x000000021e814ddc thread_start + 4
2019-02-13 11:21:42.015414+0100 BugAR[508:29514] Execution of the command buffer was aborted due to an error during execution. Caused GPU Hang Error (IOAF code 3)
2019-02-13 11:21:42.015509+0100 BugAR[508:29514] Execution of the command buffer was aborted due to an error during execution. Caused GPU Hang Error (IOAF code 3)
2019-02-13 11:21:42.015940+0100 BugAR[508:29514] Execution of the command buffer was aborted due to an error during execution. Discarded (victim of GPU error/recovery) (IOAF code 5)
2019-02-13 11:21:42.016002+0100 BugAR[508:29514] Execution of the command buffer was aborted due to an error during execution. Discarded (victim of GPU error/recovery) (IOAF code 5)
2019-02-13 11:21:42.016152+0100 BugAR[508:29514] Execution of the command buffer was aborted due to an error during execution. Discarded (victim of GPU error/recovery) (IOAF code 5)
2019-02-13 11:21:42.016185+0100 BugAR[508:29514] Execution of the command buffer was aborted due to an error during execution. Discarded (victim of GPU error/recovery) (IOAF code 5)
2019-02-13 11:21:42.018755+0100 BugAR[508:29514] Execution of the command buffer was aborted due to an error during execution. Discarded (victim of GPU error/recovery) (IOAF code 5)
2019-02-13 11:21:42.018795+0100 BugAR[508:29514] Execution of the command buffer was aborted due to an error during execution. Discarded (victim of GPU error/recovery) (IOAF code 5)
2019-02-13 11:21:42.019140+0100 BugAR[508:29514] Execution of the command buffer was aborted due to an error during execution. Discarded (victim of GPU error/recovery) (IOAF code 5)
2019-02-13 11:21:42.019166+0100 BugAR[508:29514] Execution of the command buffer was aborted due to an error during execution. Discarded (victim of GPU error/recovery) (IOAF code 5)
推荐答案
这是 Apple 的 bug，发生在场景的环境图像分辨率过大时.将场景的环境图像调整为 1000x500 即可解决问题.
This is an Apple bug, happens when the resolution of the environment image of the scene is too large. Resizing the environment image of the scene to 1000x500 solves the problem.
这篇关于为什么 iPhone XR、XS 和 XS Max 不将环境图像应用于 ARKit 中的场景?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
查看全文
