So, until now, I was setting the capture FPS by changing the FPS of the actual application. For example, setting the FPS to 1 FPS would not only take just one "snapshot" per second, but also set OVRdrop's target FPS to 1 frame per second, which caused it to seem laggy and unresponsive.
I have now implemented a proper solution. The target FPS of OVRdrop will now cap at a minimum of 60 FPS, however it will go higher with the higher FPS settings.
The actual "screenshot" however, will be taken with the FPS you set - i.e. 1 FPS = 1 screenshot per second, but OVRdrop itself will continue to update at 60 FPS, so OVRdrop (and the VR overlays) no longer seems slow or unresponsive.
I'll do some testing later before I push v1.0.4p4, and I might lower the minimum of OVRdrop itself to 30 FPS if it still seems responsive at that level.
The actual capture rate has not changed, but OVRdrop itself will now cap out at a minimum of 60 FPS so it no longer seems unresponsive or slow with slower capture rates. As a side effect however - unless I fix this before pushing v1.0.4p4 - the FPS: ### counter will now bottom out around 60 FPS instead of displaying the actual capture rate FPS. At higher FPS settings (60/120/Unlimited) you won't see a difference.
So, until now, I was setting the capture FPS by changing the FPS of the actual application. For example, setting the FPS to 1 FPS would not only take just one "snapshot" per second, but also set OVRdrop's target FPS to 1 frame per second, which caused it to seem laggy and unresponsive.
I have now implemented a proper solution. The target FPS of OVRdrop will now cap at a minimum of 60 FPS, however it will go higher with the higher FPS settings.
The actual "screenshot" however, will be taken with the FPS you set - i.e. 1 FPS = 1 screenshot per second, but OVRdrop itself will continue to update at 60 FPS, so OVRdrop (and the VR overlays) no longer seems slow or unresponsive.
I'll do some testing later before I push
v1.0.4p4
, and I might lower the minimum of OVRdrop itself to 30 FPS if it still seems responsive at that level.The actual capture rate has not changed, but OVRdrop itself will now cap out at a minimum of 60 FPS so it no longer seems unresponsive or slow with slower capture rates. As a side effect however - unless I fix this before pushing
v1.0.4p4
- theFPS: ###
counter will now bottom out around 60 FPS instead of displaying the actual capture rate FPS. At higher FPS settings (60
/120
/Unlimited
) you won't see a difference.