Mega Man X Collection - Mega Man X 3 has a graphic bug with vertical scrolling

[GoogleCodeExporter]

Mega Man X 3 has a graphic bug with vertical scrolling. Each time, it will 
display a weird frame at the bottom of the screen. It's visible in the first 
stage when you climb down the first ladder.

I have tried a lot of things like enabling HW hacks (sprite, WildArms offset) 
in GSdx 5330, different settings in Vus and EE/IOP emulating (clamping mode 
switch to Extra + Preserve Sign or Complet).
With ZeroGS 0.97, the game doesn't work properly.
I'm using PCSX2 0.9.9.5326 on Windows 7 32 bit. I also tried with PCSX2 0.9.8 
and 0.9.6 but it doesen't change anything except more graphic bugs.

I also noticed that I have to play Mega Man X collection in native mode in GSdx 
plugin in order to have less graphic bugs (there is some edges on the character 
and some interference in videos) but the result is quite blur.

Original issue reported on code.google.com by darkghos...@gmail.com on 11 Jul 2012 at 9:18

[GoogleCodeExporter]

What about running in software (F9)? I'm able to run this title fullspeed and 
avoid all the gfx issues with the software backend. And that would help with 
diagnosing as well.

Original comment by wespipe...@gmail.com on 11 Jul 2012 at 10:04

[GoogleCodeExporter]

I have the same issues with vertical scrolling in Mega Man X 3 in software 
mode. I tried the directx 9 and 10 versions.

Original comment by darkghos...@gmail.com on 11 Jul 2012 at 10:55

[GoogleCodeExporter]

Ok, I confirm this issue - and it is quite annoying. Wonder if it's always been 
like this? I couldn't find anything that fixes it either. :(

http://imageshack.us/photo/my-images/521/frame1l.jpg/
http://imageshack.us/photo/my-images/593/frame2t.jpg/

Original comment by wespipe...@gmail.com on 12 Jul 2012 at 4:28

[GoogleCodeExporter]

It was already like this on PCSX2 0.9.8 and 0.9.6. 

But it's a lot more annoying in some stages, here in your pictures the bottom 
is dark. But sometimes, it's green or orange with some parts from the previous 
area.

Original comment by darkghos...@gmail.com on 12 Jul 2012 at 12:21

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Here more examples :

http://imageshack.us/photo/my-images/220/mmx31.jpg/
http://imageshack.us/photo/my-images/820/mmx32.jpg/

In motion, it's a lot more annoying than it looks.

And here, a picture from the game in GSDx hardware mode in native resolution :

http://imageshack.us/photo/my-images/526/mmx33.jpg/

And there, in GSDx hardware mode with scaling 3x native (using another scaling 
like 2x native dosen't change anything)

http://imageshack.us/photo/my-images/534/mmx34.jpg/

As you can see, in native resolution the game is very blurry. And the use of 
scaling causes gfx issues around the characters.

http://imageshack.us/f/196/mmx36.jpg/

I also tried to disable all speed hacks but it dosen't help.

Original comment by darkghos...@gmail.com on 13 Jul 2012 at 12:17

[GoogleCodeExporter]

Is this even a bug? Games on consoles with hardware scrolling (such as the SNES 
in the case of MMX) often had bad graphics in the edges of the framebuffers.

Original comment by sudonim1 on 21 Jul 2012 at 4:08

[GoogleCodeExporter]

It doesn't happen on the SNES or PSX version. But I looked closer and I noticed 
that the bottom of the screen is cropped so this kind of bug is not visible.

I don't know why but on this PS2 version, we can see a bit more and then this 
bug appears. The other games of this collection don't have this problem.

I can't verify how it looks on console because my PS3 compatible with PS2 games 
doesn't work anymore (YLOD --').

Original comment by darkghos...@gmail.com on 21 Jul 2012 at 12:50

[GoogleCodeExporter]

This is obviously an emu bug. No way they would ship a game like this. This 
video shows no issues in verticle movement on MMX3. 
http://www.youtube.com/watch?v=imSz7x1ruFU 

Original comment by wespipe...@gmail.com on 21 Jul 2012 at 11:14

[GoogleCodeExporter]

On last test with r5492 this is fine now.

Original comment by refraction on 5 Apr 2013 at 9:49

• Changed state: Fixed

[GoogleCodeExporter]

I tested it with r5492 and r5620 but it doesen't change anything, the bugs are 
still there. You can see the issue at the begining of Mega Man X3 at the first 
ladder. 

Have you activated a hack or anything else?

Original comment by darkghos...@gmail.com on 21 Apr 2013 at 10:59

[GoogleCodeExporter]

This is still an issue. Can we please reopen?

Original comment by wespipe...@gmail.com on 25 Oct 2013 at 2:55

[GoogleCodeExporter]

Can you please verify that the buggy part of the picture is not clipped on a 
real console? You could compare the emu output with that Youtube video.
The bug is entirely normal for this kind of game (as sudo said), but they would
hide it in the offscreen area. Simply use the GS window zooming function then 
to do the same.

Original comment by ramapcsx2.code on 25 Oct 2013 at 5:51

• Changed state: Unknown

[GoogleCodeExporter]

I tested it with the lastest build available, r5755 . Actually, it's not really 
an emu bug but an issue with the ratio. On PCSX2, the game is a little bit 
stretched to 4:3 and the screen is slighlty shifted, we see a little bit too 
low. It's a Super NES game, the correct ratio is 8:7 I think and the correct 
ratio is kept on PS2.

Here 2 pictures, emu vs Megaman X Collection on a real PS2 console :

http://imageshack.us/a/img407/8098/31ij.png
http://imageshack.us/a/img855/773/bfy9.png

GS Window zooming function is not a solution because we can just zoom in but 
not shift the picture a little bit higer or correct the ratio.

Original comment by darkghos...@gmail.com on 31 Oct 2013 at 1:28

[GoogleCodeExporter]

Thanks for the effort but it looks like your capture is cropped at the bottom.
I think there's a few more pixels there if you tweak the DScaler output a bit.

Original comment by ramapcsx2.code on 1 Nov 2013 at 8:36

[GoogleCodeExporter]

You mean for the second one? It's from this youtube video : 
http://www.youtube.com/watch?v=6NdpCbu_dEs at 6:17.

Original comment by darkghos...@gmail.com on 1 Nov 2013 at 1:44

[GoogleCodeExporter]

I think I can faintly see it happening there.

Original comment by ramapcsx2.code on 3 Nov 2013 at 9:22

[GoogleCodeExporter]

I don't even get time to process in my mind what's wrong before it's gone, this 
is a really really petty bug report if that's the only problem..

Original comment by refraction on 3 Nov 2013 at 9:26

[GoogleCodeExporter]

I'll see if I can reproduce it here.

Original comment by ramapcsx2.code on 4 Nov 2013 at 1:01

[GoogleCodeExporter]

Ok, I tried the GC version and saw the same issue. SO, it's either a bug with 
BOTH emulators or it's just a port issue. Betting on the latter. :) Go ahead 
and close.

Original comment by wespipe...@gmail.com on 30 Nov 2013 at 7:36

[GoogleCodeExporter]

I would bet on it being a port problem, i will mark this as invalid.

Original comment by refraction on 30 Nov 2013 at 11:10

• Changed state: Invalid