Forum Discussion
anyone using prototype or probuilder, can't use rift in game
in editor game mode, the only way is "build and run"
btw, "build and run" always put me in vsync and with a "heavy" lag or latency compared to in editor play, any idea? Thanks.
btw, "build and run" always put me in vsync and with a "heavy" lag or latency compared to in editor play, any idea? Thanks.
3 Replies
Replies have been turned off for this discussion
- I solved the first issue, was my bad. I have a OVRCameraController and OVRPlayerController at the same in the scene...
by mistake I dragged one of the cameras of player so to make it easy I deleted all camera and player controllers and create a new OVRPlayerController, then the issue was solved (I could play in editor game mode). "radomiro" wrote:
btw, "build and run" always put me in vsync and with a "heavy" lag or latency compared to in editor play, any idea? Thanks.
Even if you have Vsync off in Quality Settings, the Oculus Unity integration will force it on. You can stop it from doing this by editing the bottom of OVRCameraController.cs so that it's not setting QualitySetting.vsyncCount to 1.
Also, if your project is set to use DirectX 11, that could also be making the latency even worse with Vsync on.- ProBuilder guy here- I would be very interested to hear any issues you run into while developing for the Rift with ProBuilder/Prototype. We definitely want to make sure the tools are top-notch for Rift dev. Jumping in soon, myself!
