VizVid's user interface is facing backwards on Android/Quest platform.

[AARaidenMK]

Unity Version: 2022.3.22f1
VizVid Version: 1.7.6-beta.2

How to describe a issue that is this confusing? Um...

So, it all started when I went on my phone and checked if VizVid is working perfectly fine without running into issues on the Android/Quest platform. But, the moment I toggle on VizVid, I noticed right away something is way too off. The screen appeared black because the user interface only shows on the back instead of the front, making it look like it's invisible. But on PC platform, the user interface is on the front and the back of the media player is invisible, like it always supposed to be.

I've provided video proof if you like to check them out yourself, to understand what's happening. But anyways, is there a way to fix this, or will this be fixed in the next update? Please respond and thank you.

PC-side:
No changes.
Screen and Main UI separated.

Quest-side:
No changes.
Tried interacting with VizVid while a video is playing.
Screen and Main UI separated.

---

Edit (July 7, 2026): I forgot to mention this before posting this issue. I unpacked the VizVid prefab after adding it to my Avatar World's hierarchy. I've checked the installation guide and it didn't say anything about unpacking prefabs. Hopefully that didn't break VizVid on Quest, did it? Or was it always like this since the day VizVid was released?

[JLChnToZ]

Let me investigate this. Did it reproducible when entering demo world?

https://vrchat.com/home/world/wrld_7239d09c-7b25-43a5-8ccd-502d986b016a/info

[AARaidenMK]

Let me investigate this. Did it reproducible when entering demo world?

https://vrchat.com/home/world/wrld_7239d09c-7b25-43a5-8ccd-502d986b016a/info

I've tested it in the demo world, and other worlds that has VizVid, like Nest ネスト for example. Yes, this issue is reproducible.

[JLChnToZ]

Wondering what Android model are you using? I have just tested with my own device and it works normally.

[AARaidenMK]

Wondering what Android model are you using? I have just tested with my own device and it works normally.

I'm using a Galaxy Note 10. I'm not sure if it'll help because yesterday, my friend, who's on a Quest headset, had to go behind the media player in order to see where he was clicking on when trying to put up an anime music video, so this isn't a mobile-only issue.

Have you tried testing this issue on the any world with VizVid, like Nest ネスト?

[AARaidenMK]

I don't own/have any Oculus Quest headset, but I can getting someone who's on Quest to help test this issue if you want. Like I said, I don't think this is a mobile-only issue.

[JLChnToZ]

I just tested that as well, no issues for me.

I think this issue is specifically to some old Android devices, as the graphics API (shader) in it has some quirks, especially on how the culling programmed in my UI shader (technically speaking, how the VFACE returns).

This actually not the issue in VizVid, it should be in my foundation package. I will investigate it anyway, but no guarantee can be resolved.

[AARaidenMK]

I just tested that as well, no issues for me.

I think this issue is specifically to some old Android devices, as the how the graphics API (shader) in it has some quirks, especially on how the culling programmed in my UI shader (technically speaking, how the VFACE returns).

This actually not the issue in VizVid, it should be in my foundation package. I will investigate it anyway, but no guarantee can be resolved.

Weird. I didn't know some shaders can mess up on older models, but I still can't my head wrapped around on how the UI is facing backwards when it's supposed to be on the front. Maybe I'm overstressing about it.

I did tried flipping some parts of the UI to face the other way to see if it solved this weird issue. It didn't seem to work as I thought it would.
But anyways, if this issue can't be resolved because it seems this issue is only happening on older model, then it's fine. I don't want to keep stressing myself out trying to fix this issue.

[JLChnToZ]

I have patched the shader, please update the vrcw-foundation package to latest and retry.