#Weird honestly. I still think there’s
1 messages · Page 1 of 1 (latest)
Ok fair enough. I’ll try and run some tests next week to confirm, but as I said I haven’t experienced your issue.
Are you specifically talking about 2022.3.18? Or is the latest 2022.3?
And you’re using the vr template vanilla you said
If you have links to other users experiencing this, it would be good
I would encourage you to write out what you tried in a forum post. It’ll make it easier for the graphics dev to engage with you and follow up if they see fit.
the entire 2022 stream, i've tried up and down that branch
ok i'll do that when i'm back from that unreal project and will have time to put together a small unity project
Sounds good. The more you can do to repro the issue, and post about it and ideally also file a bug report, the more I can get ressources into looking into your issue.
Here is the case number, with video capture showing the problem as well as the project IN-73602
I'll keep the project VR Core on my drive, if you have any question
Would you mind posting all that in a forum post I can link the devs?
Cheers I shared with the team
Hey so our graphics qa could not reproduce when using the latest 2022.3 lts in your repro project using quest 2 + link.
same OS/hardware/driver version etc,,,?
Well they used the latest 2022.3, which is newer than the one you’re using. Have you tried updating to the latest version? It’s possible a fix was introduced in intermediate versions.
same too
hardware?
I’m not sure what their hardware is
You said you’re using airlink though right? Have you tried using wired link?
they're prob testing on a mac 
they need to match my configuration step by step, could be OS, unlikely to be driver because i use the latest studio