DeoVR app version 14.4 (My photos, login info saved)

Kieshi

New version of DeoVR app 14.4 is available on Quest, Pico and Steam.

New feature

Added “My photos“ section

Improvements

Username and email are now saved for login

Bug fixes

Search restored for favorite playlist
Shuffle not working in playlists fixed
Thumbnails in playlists not updating fixed
Drop in FPS while adjusting sharpness in passthrough fixed
URL history not working correctly fixed
App crashing when pre-setting "reset to default" fixed

Yoooi

Kieshi
Not sure if this is known but there is an issue with remote control api which I think was introduced in 14.4.

The remote api server uses VideoPlayer.CurrentTimeAsync to send current video time which has flawed logic. While video is paused the value will fluctuate because CurrentTimeAsync adds CurrentAppTime - lastCurrentTimeUpdate to the actual current video time. lastCurrentTimeUpdate is updated on each frame in Update() but if the remote api server reads CurrentTimeAsync between frames the value will not be stable.

Sample values with video paused:

This also has another issue on some headsets. If the device stops rendering, Update() will not be called and VideoPlayer.CurrentTimeAsync will grow infinitely even when paused.

marklck

i have checked 14.4 same bugs in my quest 3, horizontal offset missing in transform menu with regular side by side 3d photos, 180 side by side photos work but not regular side by side photos, and the sharpness in 14.3 instead of turning bright when slider is moved now it don't work at all the sharpness slider acts like a 2nd contrast slider.

Kieshi

marklck we have this issue listed, will try to solve for next release

osamumatsumoto

A-B loop don't work.

Kieshi

osamumatsumoto Could you please give more details? Which device are you using? Is it Steam or Meta/Pico store version? What exactly doesn't work?

osamumatsumoto

Kieshi
・quest2
・The A and B parts of the A-B loop are automatically placed at the end of the video. I can't move them.

Kieshi

osamumatsumoto we are looking into it right now, should be fixed with next version release