GSDX-TextureCache: Remove hacks which caused scaling issues

* Ignore Frame memory offsets for calculating dimensions value of display rectangle.
* Remove hack which limited scaling size based on the scissor value.

Note: With the following commit, SilentHill 2 now properly outputs the desired resolution by the users on custom resolution. Previously if we set 1024 x 1024 , it'll output a lower height value which was caused by the hack removed on this commit.
This commit is contained in:
Akash 2016-06-25 21:55:50 +05:30
parent dce67351f9
commit ce20544a4f
1 changed files with 2 additions and 15 deletions

View File

@ -472,21 +472,8 @@ GSTextureCache::Target* GSTextureCache::LookupTarget(const GIFRegTEX0& TEX0, int
} }
else // Custom resolution hack else // Custom resolution hack
{ {
GSVector4i fr = m_renderer->GetFrameRect(); int ww = m_renderer->GetDisplayRect().width();
int hh = m_renderer->GetDisplayRect().height();
int ww = (int)(fr.left + m_renderer->GetDisplayRect().width());
int hh = (int)(fr.top + m_renderer->GetDisplayRect().height());
// Gregory: I'm sure this sillyness is related to the usage of a 32bits
// buffer as a 16 bits format. In this case the height of the buffer is
// multiplyed by 2 (Hence a scissor bigger than the RT)
// This vp2 fix doesn't work most of the time
if(hh < 512 && m_renderer->m_context->SCISSOR.SCAY1 == 511) // vp2
{
hh = 512;
}
if(ww && hh) if(ww && hh)
{ {