Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
hyperion337's avatar
hyperion337
Explorer
10 years ago

Since 0.6 Oculus SDK we've been having issues. Ideas?

So I did a bad thing.

I'm the developer for Convrge and I created an update where I implemented a ton of new code, which on its own is fine... until it doesn't work and you can't pin down what is going wrong.

With the latest update we've run into issues where the voice codec we're using takes an extremely long time (22ms based on the Unity profiler) and Twitch streams are affecting the CPU to the extent of lowering the FPS below 75. Also some parts of the world are causing judder on my GTX 670 which definitely shouldn't and haven't previously. I'm using an i7 at 2.7Ghz.

I'm about to spend a day working on the following potential causes, if anybody has any other ideas as to why our latest build could be screwing it up (based on the below changes I made), I'm all ears and will buy you a virtual beer.

Changes:
Oculus 0.6 SDK & 0.1 Utilities
Unity VR integration
New personal browser which uses CoherentUI Web Browser plugin to a larger extent than previously.

Here is a screenshot of the profiler with the voice codec taking an extremely long time to encode (have never had an issue with this previously, from memory it is usually around 3-5ms max):

http://i.imgur.com/Ignv8B0.png

I'll post back here tomorrow night if I manage to work out what was happening.

2 Replies

Replies have been turned off for this discussion
  • I've tried integrating another voice wrapper (using the Opus codec) and was able to reduce the impact of voice to the usual 5ms but I had to drop the bitrate to really low levels and it still doesn't perform as well as it did before this update. It seems like there is an underlying thing that is causing a loss of CPU as we've never noticed any CPU issues over the last 6 months (until now).
  • I rolled back to Unity 5.0 and Oculus Unity Int 0.5.0.1 and things are working smoothly again. Not sure what was happening but its resolved now.