Hello everyone.
I’m developping a game in VR with steam VR. I have a bunch of differents levels and everything worked well until now.
But now I have some lags, the game is jerky while I move my head in the space.
The rotation work fine and the same for the motions controller.
But when I try to move in the room everything begin to lag and I don’t understand why.
I tried to reduce the quality settings but nothing change.
I have a good configuration so the probleme is not there.
So if anyone have an idea it really would help me
I don’t know if the cause is similar, but I tried to run some unit test for VR on a GTX1070/i7 with very simple scenes (30k polygons, 40 drawcalls, running at some 700FPS without VR, and from what I see in the Oculus Debug Tools (lost frame capture), I do get frame drops regularly, causing stutter when reprojection is off (turned of via the oculus tool).
I am very surprised that even such a simple scene would result in reprojection (every 2 or 3 seconds). I have no scripts, just a camera and that simple geometry. So there is no reason for being GPU or CPU bound, but still I do get frame drops. I’m running my tests from a build, not from the editor. Debug tool says I’m dropping only to 87FPS, so that’s usually just on frame dropped but that’s enough to break what should be a really smooth experience.
Does anyone have experience with the oculus debug tool ? Can you get your simple scenes to consistently render at 90FPS ?
I’m puzzled…
I have some similar experiences in Android Cardboard VR builds. Though it’s not even near 90 fps (say more like 5-10 or so…) I get the impression the fps is getting lower (jerkier) when built with newer Unity versions, especially on older devices with for example Android 6.0.
1 Like
Turn on Continuous interpolation for your rigidbody?
Are you outputting much debug stuff? That causes framerate hits for me…
1 Like
@Urkins and @unisip - did you ever find a solution for this? I’m running into similar problems with builds for the quest even when stripping it down to the simplest possible scene with all the recommended configs… any lessons learned would be much appreciated!
3 Likes
Joining. Having the same issue with close unmoving objects in quest. When moving the head next to it you get double vision thingy, it’s nauseating, and without any fps drop. Tried everything I could think of, will be happy to have this solved.
1 Like
This is a known issue/regression that works OK in 2018.4 (or is it 2018.3). You can find (and vote!) on the issue here. Unity Issue Tracker - [Oculus GO][Oculus Quest] Object is jittering when position is being affected by Time.deltaTime
I seen this bug report before and tested in 2018.3, currently we are working in 2018.4.1f1 as Oculus recommended.
Physics aren’t in use, the blurred object can be static and the HMD doesn’t have any rigidbody (the object don’t have one).
I did tried to change the Time settings but it didn’t made it any better.
Any idea anyone?
It’s still an issue on 2019.3.0a12 despite the release notes saying it was fixed, I have submitted a bug report as downgrading to 2019.2 didn’t fix it either.
Still an issue in 2019.3.13.
Very lightweight scene; getting stutter when I move my head, about 15% of the time.
Using Application.onBeforeRender to process lightweight tracking updates to the screen - I’m certain I’ve optimized for performance and it doesn’t seem to make a difference.
1 Like
UE5 looking awfully attractive…
Hello. I am facing similar issues. When using oculus go when I move it is very laggy and when I move my head, the scene get blurry and changes Color sometimes. I really need a solution to this problem. thank you.
This is really vague for anyone to help.
WHEN i export to oculus go, the users movement is lagging. It is not smooth. When you move around to look at the scene, i takes time for the scene to load which causes it jitter. it all of a sudden becomes green or purple before being able to load. main problem is the user movement. I is not smooth at all. I tried to edit settings e.g. shadows etc… none of them have a major impact.
I am a beginner. I don’t really know how to explain in the right terms.
1 Like
do you have any advice?
I can’t really help much without more description, this is the equivalent of saying ‘my car doesn’t work’ without saying the model of car (apologies for sounding snarky).
Please detail the draw calls/batches and set passes in your scene, what is the framerate (fps) of your scene when running on the Oculus headset , how many objects are there, what’s the vertex count in your scene for most of the play time?
At first impression it just sounds like there is too much going on in the scene and the framerate is dropping
I highly recommend referring to the Oculus developer docs, there is lots of information out there for beginners to refer to and most of it is extremely useful. It’s not easy starting out but you will learn from referring to these guidelines:
https://developer.oculus.com/documentation/unity/unity-perf/
I’m also running into slight stutters in my scene even when I turn all of my settings to the lowest. I’m developing for the quest and even when I port it to play it stutters on a basic scene. Any advice is appreciated.
I have the same problem.
I think I found a solution. Edit the Maximum Allowed Timestep to the Fixed Timestep. You may also need to disable locking the Fixed Timestep to frame time inside of SteamVR Settings.
1 Like
i can confirm this with surprise but it does make sense. Equaling the max allowed and fixed threshold was enough for me. Plus setting it to 0.1 speeds the steps up making it less jittery or in my case completely gone! Remember, speed/velocity constants that were used with previous fixed timestamp will feel slower now if the values were lowered, so remember to check and correct your velocity constants across the project. Thanks man, life saver!!!