Emulator

This issue doesn't exist in 3.5-1067-dirty. Use a newer build?

what is your graphics card because when i had that build, i never had that problem.

According to SS, this only happens at 1x IR. And yes, JMC4789 and SS tested it on latest.

When I run it at 1x IR in OGL or DX9, I don't get the issue on the latest build, so I dunno what to tell you. What kind of GPU are you guys running? I have a GTX 670 with Forceware 314.21..

I'm using a GTX 280; this seems to be one of those issues that doesn't make sense or even happen to everybody.

Reproduced. Requires that you set Internal Resolution to "Auto". Auto (Windows Size) produces hard lines with crisp edges. Auto (Multiple of 640x528) has fuzzy lines.

Alright, plotted out the various behaviors. It should be noted that Scaled EFB Copies has no effect on this glitch. At least none that I saw.

DX9
Manually setting IR - 1x works, everything else is broken
Auto (Window size) - Broken on all window sizes
Auto (Multiple of 640x528) - Broken on all window sizes

OpenGL
Manually setting IR - Works
Auto (windows size) - Broken on all window sizes
Auto (Multiple of 640x528) - Works at all window sizes except 1x

DX11
Everything works no matter what IR is used.

this is caused by the method this games uses to render the disolve screen.
it uses a large amount of horisontal lines. in dx11 the line width is scalled with the screen, in opengl this scalling is incorrect. in dx9 you cannot set the width of the lines. to fix this, on opengl the scalling method must be correted. and in dx9 line rendering must be emulated with triangles.

Nice! Thank you for the detailed explanation!

This issue is questionable because i dont have this issue and i have and amd radeon hd 6870 oc. i did have this issue when i had an old radeon graphics card, but not on this one. Could be your drivers or a setting in the Nvidia drivers.

This issue is questionable because i dont have this issue and i have and amd radeon hd 6870 oc. i did have this issue when i had an old radeon graphics card, but not on this one. Could be your drivers or a setting in the Nvidia drivers.

You were using D3D11. This is very well known and highly documented, with a well known cause.

So this issue fixed itself at some point, works with openGL now. Revision 2306.

for auto window size tht is. However, contrary to what MaJo said manually setting it to 2.5 causes this.