Skip to content

Commit

Permalink
Use the oversample factor for the reccommended target size
Browse files Browse the repository at this point in the history
It seems the original code was commented out due to a misunderstanding
of the difference between the overfill and oversample factors.
  • Loading branch information
CrossVR authored Mar 30, 2017
1 parent f0e16cf commit cd840e8
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions src/OSVRTrackedDevice.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -222,12 +222,11 @@ bool OSVRTrackedDevice::IsDisplayRealDisplay()

void OSVRTrackedDevice::GetRecommendedRenderTargetSize(uint32_t* width, uint32_t* height)
{
//const double overfill_factor = renderManagerConfig_.getRenderOverfillFactor();
const double overfill_factor = 1.0;
const double oversample_factor = renderManagerConfig_.getRenderOversampleFactor();
const auto bounds = getWindowBounds(display_, scanoutOrigin_);

*width = static_cast<uint32_t>(bounds.width * overfill_factor);
*height = static_cast<uint32_t>(bounds.height * overfill_factor);
*width = static_cast<uint32_t>(bounds.width * oversample_factor);
*height = static_cast<uint32_t>(bounds.height * oversample_factor);
OSVR_LOG(trace) << "GetRecommendedRenderTargetSize(): width = " << *width << ", height = " << *height << ".";
}

Expand Down

0 comments on commit cd840e8

Please sign in to comment.