Forum Discussion
Unity build odd behavior in direct mode
I finally have direct mode working on my laptop! The desk demo works fine however I am experiencing something strange with the Unity builds.
All of my test so far have been with the pre-built Tuscany demo (with the -force-d3d11 flag) and my own Tuscany demo built in Unity 4.5.5f1 in DX11 mode.
After the demo starts I turn of mirroring (hitting m) since it seems to cause judder on my laptop with it on. The demos then seem to work fine for about 30 seconds or so. I start to see a couple of hiccups, then it quickly gets more, and more until it is juddering wildly. The frame rate counter is jumping all over the place. Turning off timewarp in my Tuscany build did not stop this from happening.
I have reproduced this the same way with the pre-built Tuscany demo and my own. I also reproduced in on one of my own projects.
I am wondering if it is Unity specific because the desk demo works great in direct mode so I know that it is working properly. I am so happy direct mode is working. I want to run my own stuff in it. It is awesome for about 30 seconds only.
All of my test so far have been with the pre-built Tuscany demo (with the -force-d3d11 flag) and my own Tuscany demo built in Unity 4.5.5f1 in DX11 mode.
After the demo starts I turn of mirroring (hitting m) since it seems to cause judder on my laptop with it on. The demos then seem to work fine for about 30 seconds or so. I start to see a couple of hiccups, then it quickly gets more, and more until it is juddering wildly. The frame rate counter is jumping all over the place. Turning off timewarp in my Tuscany build did not stop this from happening.
I have reproduced this the same way with the pre-built Tuscany demo and my own. I also reproduced in on one of my own projects.
I am wondering if it is Unity specific because the desk demo works great in direct mode so I know that it is working properly. I am so happy direct mode is working. I want to run my own stuff in it. It is awesome for about 30 seconds only.
4 Replies
Replies have been turned off for this discussion
- What did you do to get direct-to-rift mode to work on Tuscany using Unity free 4.5.5f1 and OVR 0.4.3? I just get a blank screen on the Rift. (I just created a new empty project in Unity free and imported the Tuscany demo package. Then exported the game and tried to run DirectToRift).
P.S. using Win7 64-bit "MichaelSchenck" wrote:
The demos then seem to work fine for about 30 seconds or so. I start to see a couple of hiccups, then it quickly gets more, and more until it is juddering wildly.
Can you attach the profiler and see what is making it miss the 13ms frame deadlines? Does the issue still happen at the "Fastest" quality setting? You can set that in the editor or by holding ALT when the app starts.- Three screenshots from the profiler connected remotely to the tuscany build running with the Rift in direct mode. They were taken at the beginning of the problem and then as it got worse. The third one i cleared so the frame count is wrong but it is far after when it is worst. I tried to do the deep profile however it doesn't seem to work remotely. I put in profile begin and end but it didn't show anything in the middle. If you want me to do some more testing I can put in a bunch of those in different places to see what is happening inside the update function. I just need some direction where you would like me to do the probing. I am on Windows 8.1 on a laptop with an Intel 4600/Nvidia 870M. I can send you a dxdiag if you need more details. It seems like it shifts from the update function to being a problem in the driver maybe - not exactly sure what Overhead means.
EDIT: Also, I forgot to mention these tests were with the quality set to fastest. I have not had any performance problems with Tuscany. It runs very nicely in extended mode. The latency reduction is so good now that it feels almost the same as direct mode.
- Thanks for the profile. It sounds like a timing issue with our driver. I'll point it out to the team.
