You have an off-by-one frame rendering error; your camera is not synced with the player (tested on both MacOS and windows). I also got 10s hitching on load on a beefy windows rig -- might be missing some shader compiles on the loading screen.
You're probably optimizing for XR, but 99% of people will experience your app for the first time on a different platform, so it's worth fixing the desktop render path.
I am sceptical of these things however since they are a well worn path that so far has taken off only to a limited extent. In reality, you get bored very quickly in these environments, and it's impossible to implement impressive visual fidelity in worlds that users build themselves. Horizon Worlds is probably the marquee example of that. Am curious what the differentiating angle is here to previous efforts?
The main difference is that these worlds are from User Generating. Not just limited to us developers. The visual is rather simpler than realistic graphics but I think the freedom users will have could be more important. but we will have to see.
Might have a lot of potential, but you need some kind of a showcases right at the start, highlighted to show what is possible. I clicked around and first worlds I saw were very basic. Maybe if users saw something incredible right at the start, they'd be motivated to be more creative
You're probably optimizing for XR, but 99% of people will experience your app for the first time on a different platform, so it's worth fixing the desktop render path.
I am sceptical of these things however since they are a well worn path that so far has taken off only to a limited extent. In reality, you get bored very quickly in these environments, and it's impossible to implement impressive visual fidelity in worlds that users build themselves. Horizon Worlds is probably the marquee example of that. Am curious what the differentiating angle is here to previous efforts?
I wonder which is better...