VR replacement

I'd like to know if someone investigated this already and know a good "replacement engine" for VR support.

The situation:

* I'm currently on oculus 1, and prefer steamvr, and might switch to pico 4 later.
* I'm fine with C++, and might even choose it over C#.
* Visual scripting support is non-factor.

Thoughts?

 

Unreal with their Forward+ rendering is really nice

 

Godot is also really solid. The upcoming 4.2 update redid the XR loaders, making it easier to support both quest and pico devices, as well as PCVR (via OpenXR).

It also has variable rate shading support for PCVR (and probably quest 3)

 

Would be very interested in experience reports about this topic as well. My main focus is ease of use and configuration, with image quality not being that important.

 

I second Godot, its xr support is pretty decent now

Unreal is good for VR too, surprisingly good for standalone VR although most people dont realise that or try that out

 

After you get it to build it is pretty good yeah. Spent 3 days getting a quest build working in unreal last time I tried lol

 

Yes the initial setup is awful, once you have a working build pipeline for it it works nice but yeah, initial setup flow needs some serious rework

 

On my setup (Quest 1 + VR Desktop), unreal VR lags and feels sluggish. There's subtle delay, as if it is always late by 1 frame. It affects all unreal games and unity does not have this problem. Although it is good that Unreal supports proper mirror out of the box...

So, still Godot, it seems. "All roads lead to Godot".

 

I would imagine godot will also lag reasonably on a Quest 1 - I should have read the post I automatically assumed that it was a quest 2. I can definitely vouch for the Pico 4, in our organisation we have used Quest 2, Pico 4, Vive Focus 3 and a bunch of others and Pico 4 is by far the highest quality and most powerful headset in terms of bang for your buck

 

Here's the thing. I'm talking about PCVR through Virtual Desktop, and this problem occurs only in unreal PCVR titles. "Sluggish movement".

Regarding Pico, I'll probably eventually order one. One thing I'm not a fan of is that there's no headphone jack. There's also apparently a small chance of getting defective lens, which is not quite good, as I'll be likely shipping it from china.

 

Probably something wrong with your setup or we would have more reports about the problem.

 

We're looking for a VR solution too, but with different requirements and constraints; we would be looking for something with visual scripting or 'codeless', and the most straightforward Android headset (ie Quest 1/2) build process possible, for student users who arent necessarily that technical, let alone programmers.

 

Evergine might be a possible candidate based on what I've read and the launcher options for starting projects but I'm having trouble finding much of anything on the engine. At one point it was known as WaveEngine but I can't find anything on that either. There doesn't appear to be a community at all.

https://evergine.com/

 

It's mostly a rendering engine. Bit of work required to support various controllers, possibly other missing features too.

 

I saw ippdev suggest it. Looks like it is more of a presentation engine and company oriented. Source access is pricey.

 

Yes, it's not a game engine, and isn't promoted as such.

 

One of the best Oculus games I have played is The Climb (and it's sequel) which purport to use CryEngine, not sure if that's an option (I know nothing about it really)

 

I think cry engine isn't in development anymore.
It got branched to lumberyard, which then started O3DE. Can't find much about VR in O3DE docs, bit haven't looked a lot

 

Cryengine was (in?)famous for quality of its documentation. Probably best to avoid it, whatever it is called these days. Like DevDunk said, it first became Lumberyard, then something else.

Thinking about it, I can probably go nuts and try raw libsdl OpenXR VR interfacing. I mean, why the hell not.

 

Actually in the end Godot seems to run good on XR on a quest 1 from what I can see so maybe it is a good bet

 

Just out of curiosity, what are the disadvantages of unity for VR? I was considering making a VR game using unity at some point using the XR packages in the unity registry, and would like to know why you guys feel the need to find a "replacement engine" for VR.

 

I don't think the problem is with Unity and VR. The problem is with Unity and trust.

This thread may help.

https://forum.unity.com/threads/unity-plan-pricing-and-packaging-updates.1482750/

 

The problem is recent breach of trust.
See this thread: https://forum.unity.com/threads/unity-plan-pricing-and-packaging-updates.1482750/

The API itself is fine.

 

I'm assuming thoughts of creating your own engine with that rendering framework you linked in the other thread are off the table? Because I saw it supports Quest 2.

 

They're not off the table, because at the moment I'm busy with other things, and this is something I'll be dealing with when I'm done with those "other things".

Additionally, I do not plan to support Quest 1/2 directly, due to issues with Meta as a company. I'm only interested in PCVR or Pico. And I still haven't gotten a Pico.