Forum Discussion
ChrisX
10 years agoExplorer
Oculus Sample Framework for Unity 5 Rift Executable V1.0.0
I've been experimenting with the example program from the download page:
'https://developer.oculus.com/downloads/game-engines/1.0.0/Oculus_Sample_Framework_for_Unity_5_Rift_Executable/'
Can anyone tell me if this example executable is only meant to run against 'Oculus Runtime 0.8.0.0'?
I can't get it to show in the HMD if I remove the 0.8.0.0 runtime and install the new 'Oculus home' app / Runtime 1.3.0.
For me, the example executable worked perfectly on runtime 0.8.0.0, very smooth and no judder, however when I build the example from sources at:
'https://developer.oculus.com/downloads/game-engines/1.0.0/Oculus_Sample_Framework_for_Unity_5_Project/'
(using the 1.3 version unity plugin and utilities) the result only works with with runtime 1.3.0, and performs very poorly (low FPS and judder).
(using the 1.3 version unity plugin and utilities) the result only works with with runtime 1.3.0, and performs very poorly (low FPS and judder).
I'm using a DK2 and GTX 650, so maybe not the ideal spec, but the "Oculus Home" VR scene runs perfectly. It seems odd that the same example would work perfectly for me on the old runtime and badly on the new one. Does this mean the new 1.3 runtime requires a higher spec graphics card than the 0.8.0.0 version?
Would it be possible for someone at oculus to update
'https://developer.oculus.com/downloads/game-engines/1.0.0/Oculus_Sample_Framework_for_Unity_5_Rift_Executable/'
to target the latest oculus runtime? As least then I can confirm I am building the project correctly.
'https://developer.oculus.com/downloads/game-engines/1.0.0/Oculus_Sample_Framework_for_Unity_5_Rift_Executable/'
to target the latest oculus runtime? As least then I can confirm I am building the project correctly.
- Hi ChrisX,
Yes, at the moment the executable is built for the 0.8 SDK. We will be replacing it very soon with a build for the 1.3 runtime.
As you say, your machine is below recommended spec, but I'm also surprised that performance is that bad. I suggest trying again with the prebuilt executable once we update the download in the next few days.
11 Replies
Replies have been turned off for this discussion
- AndyBorrellProtegeHi ChrisX,
Yes, at the moment the executable is built for the 0.8 SDK. We will be replacing it very soon with a build for the 1.3 runtime.
As you say, your machine is below recommended spec, but I'm also surprised that performance is that bad. I suggest trying again with the prebuilt executable once we update the download in the next few days. - ChrisXExplorerOk, great. I'll keep an eye out for it. Thanks.
- ChrisXExplorerAh ha, thanks. I see the executable has been updated to 1.3.0.
I can confirm that the judder is just as bad with my GTX 650 in this executable version, i.e. the same as when I built it from sources.
So my conclusion seems to be that the 1.3.0 build requires a much better spec of graphics card than the 0.8.0 build which worked perfectly on my GTX 650 card. Interestingly it seems to be the AA settings that drag it down on this hardware with 1.3 runtime, even with the simplest of scenes.
Everything seems fine on a similar spec PC with a GTX 980, so it made me wonder if internally the 1.3 runtime is handling AA less efficiently than the older runtime and putting more demands on the GPU?). - owenwpExpert ProtegeI assume you changed Unity editor versions at the same time? That seems a more likely cause.
- ChrisXExplorerI'm not sure what you mean. I built the project with 5.3.4p1 for the 1.3 runtime, and it performs similarly badly (on my gtx 650) to the new executable download, thus confirming the problem is not caused by the way I built it. The mystery for me is why the previous executable download for this project which was built for 0.8 runtime ran perfectly on my gtx 650.
- ChrisXExplorerAh... though you may still be right about unity editor version being significant, but I did not attempt to build the project except with 5.3.4p1 with the 1.3 plugin and utilities package. So, the problem I'm getting might also be related to changes in the oculus plugin an utilities packages.
- FmegrahiHonored Guesthi, i had my game works fine on unity 5.2.2f1, when i upgraded to unity 5.3.3p1 and utilities 1.3.2, i have always the [VRDevice] Initialization of device oculus failed. in my console, and when i run the game unity crashes, any solutions please ?
- FmegrahiHonored Guestwhen i run my game i have this error
Unity v5.3.3p3, Oculus Utilities v1.3.2, OVRPlugin v1.3.2, SDK v0.0.0.
UnityEngine.Debug:Log(Object)
OVRManager:Awake() (at Assets/OVR/Scripts/OVRManager.cs:490) - FmegrahiHonored Guestwell the last one was the debug, but the error is :
[VRDevice] Initialization of device oculus failed. - ChrisXExplorer@Fmegrahi Are you sure you installed the Oculus 1.3 Runtime? https://www.oculus.com/en-us/setup/
I think that "SDK v0.0.0" message may imply you are running with the older 0.8 or earlier runtime. Also worth noting, when I built this instructions said it required Unity edit 5.3.4p1, but you list an earlier version.
Just as an aside:
My question here really morphed into "Why is the example so much more juddery when built for 1.3 when running on my GTX 650?" While I have no right to complain about since hardware is below recommended GTX 970, but still a bit mysterious why it works fine with the Oculus runtime 0.8 targeted version of this example executable.
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 8 months ago
- 2 months ago
- 5 years ago