Thursday, August 25, 2016

Dev update #21 - Legacy GPU support




Update on Gear VR (1 September):
We managed to fix known bugs but we still need to shuffle some code and run some tests after. We will try to finish all the release prep work before Monday so we can submit the app to Sideload VR early next week. Sorry for being late!

---

This is a small update, not the one with Gear VR support. Minor bug fixes and a new software encoder for some older GPUs. Desktop app version is 1.1.2 and it's available in beta channel.

Software encoding

Many people kept asking us to introduce support for video cards other than modern GeForces and Radeons. We added Intel HD Graphics support (starting with Intel Core 4000+ processors) but it wasn't enough.

Today we bring full software encoding capability for all systems running Windows 8.1+. This will allow you to run VRidge on any system that can launch your games in VR. There will be of course limitations and game / SteamVR / Oculus hardware requirements still apply but no extra hardware will be required by VRidge.

This mode is last resort option and is automatically pre-selected only if no modern video card is detected on the system. This puts high load on your CPU (depending on video resolution but good CPUs can encode 1080-1440p in real time). It may also add some latency depending on your CPU performance. It's the worst decoder out of all the options but it's the best one where none of the other options work. 

New software encoding option

Bugfixing

  • Sometimes SteamVR wasn't launching VRidge server properly. An extra option was added to desktop app settings. If you check it, it will run some extra checks during launch process to make sure VRidge server starts properly.
  • AMD "Not enough storage" or "Signature verification error" error will now ask if users wants to open troubleshooting page for this error.
  • Old NVIDIAs (pre-Kepler chipset) will no longer default to NVENC encoder. It will now offer new software encoder.
  • Changed MF's default encoding profile to 100. It shouldn't cause any problems but if it does, go to Riftcat\Config, open vridgeQuality.cfg with notepad and change UseLegacyProfile to true. Setting it to legacy profile may affect Android device compatibility.
  • Minor text fixes.

GearVR news

We contacted SideloadVR to make sure we have some platform to launch on. If they don't agree to host VRidge we'll have to create our own repackaging service to bundle user signatures. This shouldn't be too hard but may delay release for few days if SideloadVR crew refuses to host VRidge.
There is one major bug to fix and we're good to go. Expect more news and, if everything goes well, an apk file next week.

No comments:

Post a Comment