You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Somewhat noteworthy observations with the 4.0.0 and 4.0.1 Release, on a Focus 3 with current firmware:
max achievable fps seems to cap at 30fps
wvr_getrendertargetsize reports just 1720x1720 as 'recommended render target size' - this stays quite well below the typical 100% (not necessarily native) resolution.
CloudXR may have broken controller vibrations
For the render target api call issue: I believe this may be the reason for the recently introduce hardcoded values to this sample? Is there another way to get non-hardcoded, reasonable size render targets from WaveVR?
Best regards,
Jan
The text was updated successfully, but these errors were encountered:
Hi everyone,
thanks for maintaining the original sample!
Somewhat noteworthy observations with the 4.0.0 and 4.0.1 Release, on a Focus 3 with current firmware:
For the render target api call issue: I believe this may be the reason for the recently introduce hardcoded values to this sample? Is there another way to get non-hardcoded, reasonable size render targets from WaveVR?
Best regards,
Jan
The text was updated successfully, but these errors were encountered: