Hotrian
commented
7 years ago The reason full desktop capture performs poorly is because this is currently using the GDI API. The GDI API is ancient and very slow at larger resolutions. Technically though, the screen capture script already supports full Desktop Capture using the GDI API, though again, at larger resolutions the capture rate will be very low. You would have to rewrite some stuff to make it use the full desktop instead of targeting an application, but the underlying code is already there.
Additionally, would adding an option to have the overlay be curved help with performance
No, I don't believe so as the bottleneck is the GDI API and nothing to do with my application or SteamVR in specific. The GDI API is not GPU accelerated and thus is quite slow. The new API is very fast (150FPS+ with my 2560x1440 monitor, capturing the full desktop), but unfortunately Unity only supports .Net 2.0, with some .Net 3.5 thrown in, and I cannot access the new API from Unity's .Net version.
There are some other APIs I can use, but they are either too slow or do not play nice with Unity as far as my testing has shown. Once Unity finishes support for .Net 4.6 it will be very easy to add the new API support.
Edit: API name redacted ;]
bgr
tjhowse
Hi, my only use case for this app is having my full desktop in VR, and that's the only option that's missing 😄 I have a kludgy workaround right now that works good enough, and I saw that you mentioned you've tried full desktop capture but it worked bad. I figured it might actually work better than my workaround, so, if you still have that, can you please push that to a separate branch?
My workaround is to open OBS and enlarge its Filters window to maximum size, and have OpenVRDesktopDisplayPortal capture that window. I run that at 1.5x supersampling and it works good enough for me (i7, GTX 1070).
Additionally, would adding an option to have the overlay be curved help with performance in this case (since it'd go through that fast code path mentioned in OpenVR docs)?