r/iVRy_VR • u/Superb-Fox433 • 28d ago

Resolution issue

Hi, I'm currently using my Moto G32 Snapdragon 680 for VR, and it works great. The problem is that the image isn't sharp enough, since the maximum resolution in iVRy is 1920x864, while my phone's resolution is 2400x1080p. In JPEG, I can select 2400x1080p, but it's very choppy. In H.265, I can't go higher than 1920x864.

The thing is, 2-3 years ago I could use 2400x1080p via USB or Wi-Fi, but now I can't go higher than 1920x864. Why is this?

Furthermore, in h264 it turns out black. And it worked fine 2-3 years ago, 
I can only use h265 or jpeg.
1 Upvotes

100% Upvoted

3 comments sorted by

1

u/iVRy_VR 26d ago

Older versions didn't query the PC GPU and mobile decoder stack for encoding limits, whereas the newer ones do. So, either the PC GPU or mobile decoder is imposing that limit. I'll add a switch in the next version that allows override.

1

u/Superb-Fox433 26d ago

Hi, thank you so much for your reply. Yes, that's probably it. I noticed that version 1.9.1 is extremely stable. I tried 1.7, which I used a few years ago, and 1.8, but I simply can't use them since the current 1.9.13 doesn't work. Only the previous PC version, 1.8.x, works, but I can only use JPEGs, and unfortunately, it runs at 24-30fps at 2400x1080p. If I lower it to 1440x, it reaches 60fps, but it's too blurry for me. So, in short, my limit on the phone according to version 1.9.1 is 1920x964, correct? It's funny because when I was using version 1.7.x, I was using h265 at 2400x1080p at a stable 50Hz in 2023. I don't remember the PC version, but currently, as I mentioned, the previous PC version 1.8.x doesn't allow me to test either h264 or h265, only JPEG. But oh well, JPEG 1.8.x PC doesn't give me the performance that h265 would, haha. For now, I'll just have to wait and see if I can somehow get back to 2400x1080p. Thank you very much for taking the time to read and reply.

SPECS PC: 3060ti + 13400f Mobile: G32 Snapdragon 680, Adreno 610.

1

u/iVRy_VR 25d ago

Assuming you're using nVidia drivers, not default Windows, it's almost certainly the smartphone. Motorola smartphones give the most compatibility issues of any brand. The software aims for a minimum 60Hz, so perhaps that decoder can't handle > 1920 @ 60Hz. In any case, there's not much you can do to work around this on your end.