-
-
Notifications
You must be signed in to change notification settings - Fork 43
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.
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
Phone VR working so slow #95
Comments
i solved with change qp settings to 10 from 20 |
If you solved it can you close the issue? |
I'd happy to close it but it doesn't work i didn't solved it
…On Fri, 18 Nov 2022, 12:20 Jason Hendricks, ***@***.***> wrote:
I solved with change qp settings to 10 from 20
If you solved it can you close the issue?
—
Reply to this email directly, view it on GitHub
<https://github.com/ShootingKing-AM/PhoneVR/issues/95#issuecomment-1319636458>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARE3E5N6X2WVVNJ74H3RDMTWI4U2NANCNFSM6AAAAAARVKS5BY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Ok. I'm not a dev, but you'll probably get a faster fix if you post the crash logs and other data listed in the readme. (To be clear, what you submitted is not a log). |
Yes please attach the required logs. I am confused too is it slow or is it a crash or is it two different issues ? |
i don't where can i find log it was you was long time age but the problem was it does not crashing but working slow latency to high I guess. I have tried USB cable and wifi I have seen USB cable work well a little bit more than wifi but it is still too slow. i have tried changing configurations. yesterday I have used it and it worked well I guess you guys fix it. alas there is some latency still. you can close this issue |
This has been solved in latest release by using hardware encoding provided by ALVR Server. If its not feel free to reopen the issue. |
Hi, PVR Devs, I am facing a crash with the following Error:
You are doing a good job. Hope this helps ;)
The text was updated successfully, but these errors were encountered: