Guys!
Today we have released DeoVR ver. 8.54 for Windows and Oculus Quest.
New versions should appear in stores soon.
Update:
- Mesh type selection for local files updated,
- Clock added to the player UI (could be enabled from global player settings),
- Small bugs fixed.
DeoVR ver. 8.54 for Windows and Oculus Quest.
When is the major upgrade scheduled?
I'd also like to know.
What does "Mesh type selection for local files" mean?
devon19591 it probably has something to do with the correct projection of 200° fisheye videos with the _MKX200 sufix
Something went wrong, i cannot stream anymore from my custom software. Something change?
Is It possible downgrade it?
mauroamore I ran into the same problem with xbvr. I was able to fix it by removing the categories field from the JSON sent with the scene. It looks like this field changed at some point and the new version of DeoVR was choking on the old format.
2pacalypseNow Major update is coming in May. There will be one more update coming soon
Hey can you Please describe better in layman's term how to fix this? I dont know where the categories fields are or the JSON etc. Is this a glitch that DEOVR will fix? Please tell me how to make it work for the time being, thanks!
adnar321 Hey can you Please describe better in layman's term how to fix this? I dont know where the categories fields are or the JSON etc. Is this a glitch that DEOVR will fix? Please tell me how to make it work for the time being, thanks!
Yar Something's wrong!! I just updated Quest 2 to the newest DeoVR but XBVR videos won't stream anymore!! How can this be fixed? Also a bug I found before, when it was working, was when I clicked to the right most tab of the "unmatched" scenes in XBVR through DeoVR, the app crashes.
But anyways, what can I do to make streaming on DeoVR through XBVR work again? When would a new release be to fix this major problem?
DeoAesthetics Any word on 90hz support and a fix for dropped frames?
DeoAesthetics There a bunch of people noticing the problem with the usage of categories field breaking DEO VR. is there a response? do you guys recognize this problem with the release? or is this something that will stay broken and devopers will need to rewrite connection code?
Tony It seems like an unintended side-effect, would it be easier for you guys to fix it or XBVR? Please work with them to resolve the issue rather than pushing the responsibility. A lot of your users rely on XBVR working on DeoVR.
Tony Or is there any work around for the time being? Could you provide me the previous version of DeoVR apk for quest 2 so I can sideload? thanks
elixirrone XBVR has to fix it: https://github.com/xbapps/xbvr/issues/426
elixirrone XBVR has been updated. The new release (https://github.com/xbapps/xbvr/releases/tag/0.3.7) should fix your problem.
Thanks for letting me know about the fix!