Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Getting a null reference exception when selecting NDI source #223

Open
lightsailvr opened this issue Dec 18, 2024 · 7 comments
Open

Getting a null reference exception when selecting NDI source #223

lightsailvr opened this issue Dec 18, 2024 · 7 comments
Assignees
@keijiro
Labels
question Further information is requested

Comments

@lightsailvr
Copy link

I'm getting a full blown app quit on Quest 3 when selecting my NDI source. Using Klak NDI 2.1.3 with Unity 2022.3.47.

This started when I enabled Passthrough in the app. But it is inconsistent as in some times it will work, and some times it will crash.

I don't even know where to begin starting to hunt for this, but here is what logcat spits out.

12-17 15:37:22.462 3628 3628 F DEBUG : x0 0000000000000000 x1 b400006ee0a4f180 x2 0000000000000006 x3 0000000000000000
12-17 15:37:22.462 3628 3628 F DEBUG : x4 0000000000000010 x5 0000006f4cbe0c90 x6 0000006e43164540 x7 0000006e431645c0
12-17 15:37:22.462 3628 3628 F DEBUG : x8 0000000000000006 x9 b400006ee0a4f190 x10 0000000000000002 x11 0000000000008f37
12-17 15:37:22.462 3628 3628 F DEBUG : x12 0000006f7bc4f4d0 x13 0000000000000001 x14 0000000000000003 x15 0000000000000002
12-17 15:37:22.462 3628 3628 F DEBUG : x16 0000006f4ca03a28 x17 0000007015ef2120 x18 0000006e42dca000 x19 0000006ec0fb5290
12-17 15:37:22.462 3628 3628 F DEBUG : x20 0000000000000000 x21 0000000000000002 x22 0000000000000010 x23 0000000000000000
12-17 15:37:22.462 3628 3628 F DEBUG : x24 0000000000008f37 x25 0000006f0097221c x26 0000006f0196c000 x27 0000006ec0fb5290
12-17 15:37:22.462 3628 3628 F DEBUG : x28 0000006ed0195790 x29 0000006e431642e0
12-17 15:37:22.462 3628 3628 F DEBUG : lr 0000006f012d9a18 sp 0000006e43164210 pc 0000006f4caf1d9c pst 0000000060001000
12-17 15:37:22.462 3628 3628 F DEBUG : backtrace:
12-17 15:37:22.462 3628 3628 F DEBUG : #00 pc 000000000025ad9c /vendor/lib64/egl/libGLESv2_adreno.so (!!!0000!a7e45d2acf798882931be6f8fe2e66!b2997f8627!+36) (BuildId: 7babd39e60faaddda93f0aea6293944c)
12-17 15:37:22.462 3628 3628 F DEBUG : #1 pc 0000000000ac7a14 /data/app/~~e2jmxcmo0H0veVfdFVoacg==/com.lsvr.vrndi_quest-Z_9khKO6G1XZs7v8GptjlA==/lib/arm64/libunity.so (BuildId: 6a295a61b048efc2)
12-17 15:37:22.462 3628 3628 F DEBUG : #2 pc 0000000000aa42c0 /data/app/~~e2jmxcmo0H0veVfdFVoacg==/com.lsvr.vrndi_quest-Z_9khKO6G1XZs7v8GptjlA==/lib/arm64/libunity.so (BuildId: 6a295a61b048efc2)
12-17 15:37:22.462 3628 3628 F DEBUG : #3 pc 0000000000ab80ec /data/app/~~e2jmxcmo0H0veVfdFVoacg==/com.lsvr.vrndi_quest-Z_9khKO6G1XZs7v8GptjlA==/lib/arm64/libunity.so (BuildId: 6a295a61b048efc2)
12-17 15:37:22.462 3628 3628 F DEBUG : #4 pc 0000000000c05f90 /data/app/~~e2jmxcmo0H0veVfdFVoacg==/com.lsvr.vrndi_quest-Z_9khKO6G1XZs7v8GptjlA==/lib/arm64/libunity.so (BuildId: 6a295a61b048efc2)
12-17 15:37:22.462 3628 3628 F DEBUG : #5 pc 0000000000bfe9c0 /data/app/~~e2jmxcmo0H0veVfdFVoacg==/com.lsvr.vrndi_quest-Z_9khKO6G1XZs7v8GptjlA==/lib/arm64/libunity.so (BuildId: 6a295a61b048efc2)
12-17 15:37:22.462 3628 3628 F DEBUG : #6 pc 0000000000bfe708 /data/app/~~e2jmxcmo0H0veVfdFVoacg==/com.lsvr.vrndi_quest-Z_9khKO6G1XZs7v8GptjlA==/lib/arm64/libunity.so (BuildId: 6a295a61b048efc2)
12-17 15:37:22.462 3628 3628 F DEBUG : #7 pc 000000000057e674 /data/app/~~e2jmxcmo0H0veVfdFVoacg==/com.lsvr.vrndi_quest-Z_9khKO6G1XZs7v8GptjlA==/lib/arm64/libunity.so (BuildId: 6a295a61b048efc2)
12-17 15:37:22.462 3628 3628 F DEBUG : #8 pc 00000000000efcec /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: e8421e7b89d5e6fedc9c62db779bda26)
12-17 15:37:22.462 3628 3628 F DEBUG : #9 pc 000000000008c340 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: e8421e7b89d5e6fedc9c62db779bda26)
@keijiro keijiro self-assigned this Dec 18, 2024
@keijiro keijiro added the question Further information is requested label Dec 18, 2024
@keijiro
Copy link
Owner

keijiro commented Dec 18, 2024

Which Graphics API are you currently using? If it’s not Vulkan, could you try switching to Vulkan?

@lightsailvr
Copy link
Author

I am using OpenGLES3 since I noticed the frame rate tanks hard with Vulkan (20fps vs 72sfps when rendering 4K video). I'll give it a try though and see if it's more stable.

@lightsailvr
Copy link
Author

Definitely more stable, but the app no longer runs at the required frame rate when Vulkan is selected.

@lightsailvr
Copy link
Author

Following up on this - the NDI source that's sent makes a big difference in the frame rate of the app. 4096x2048 playing smoothly at 29.97 yields an acceptable frame rate.

However, if the NDI source is sending a lower frame rate, it seems to lower the frame rate of the app. Maybe the GPU is waiting for a frame?

@keijiro
Copy link
Owner

keijiro commented Dec 19, 2024

I suspect that ComputeBuffer.SetData might take longer on Vulkan compared to GLES3. While I haven’t specifically heard of this behavior, handling a full 4K texture is quite demanding for mobile devices like the Quest, so it’s not entirely surprising.

@lightsailvr
Copy link
Author

Is there any chance of the plugin working more reliably with GLES3? The frame rate difference is noticeable. But either way, just happy to have it working for now!

@keijiro
Copy link
Owner

keijiro commented Dec 20, 2024

Have you tried reducing the resolution on GLES3 as well? Streaming a full 4K video might be causing memory pressure on the device.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@keijiro keijiro

Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@keijiro @lightsailvr