cai567890 / pcsx2

Automatically exported from code.google.com/p/pcsx2
1 stars 0 forks source link

Collection of known regressions of r3274 (and following) #789

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
1) last works on 3113

2) now 3384 Win7

3) After Memory Cards checking its just a black screen - nothing happens anymore

4) What steps will reproduce the problem?
1. Launch the game
2. MC autocheking
3 eternal Blackscreen

Original issue reported on code.google.com by Zerotake...@gmail.com on 4 Jul 2010 at 6:51

GoogleCodeExporter commented 9 years ago
Comment 49 is sort of correct.
Interesting thing is the time goes a little bit faster when the gpu plugin is 
zz-ogl.

Original comment by chenxu...@gmail.com on 10 Oct 2010 at 6:03

GoogleCodeExporter commented 9 years ago
You can add many tekken titles to this long list.

Original comment by jodr...@gmail.com on 14 Nov 2010 at 6:01

GoogleCodeExporter commented 9 years ago
I think we're a bit past this now. Most (if not all) the issues caused by the 
builds around this time are now working again, we have moved on nearly 1000 
revisions, making this thread pointless.  If you have a new regression (tekken 
should now be working again btw) then make a new issue for it.

Original comment by refraction on 14 Nov 2010 at 12:28

GoogleCodeExporter commented 9 years ago
How can you say it is fixed while Onimusha Dawn of dream is still not working?

Original comment by chenxu...@gmail.com on 14 Nov 2010 at 2:07

GoogleCodeExporter commented 9 years ago
yah, I second that

Original comment by Zerotake...@gmail.com on 14 Nov 2010 at 2:15

GoogleCodeExporter commented 9 years ago
of onimusha still isnt working, make an issue for it, this one is too full of 
different games/issues to keep track of them.

Original comment by refraction on 14 Nov 2010 at 2:20

GoogleCodeExporter commented 9 years ago
The point is these problem share the same features so they should be considered 
together. Whence different aspects of the bug generated in r3274 can be shown.

Original comment by chenxu...@gmail.com on 14 Nov 2010 at 2:25

GoogleCodeExporter commented 9 years ago
The only thing these issues share in common is r3274.  r3274 is a major 
modification of like 3 major systems in PCSX2.  It had *several* independent 
bugs, most of which have been fixed.

Revision number is *one* of the many things we programmers use to help track 
bugs.  It is not the only thing.  Once a revision becomes significantly 
out-dated its usefulness to us is minimal, and when a revision is a huge one 
like r3274 its usefulness is already low to begin with.

Finally, this is emulation, which is quite unlike most other types of software 
dev.  It is likely not a 'bug' per-se in r3274 that breaks this one remaining 
game.  It is probably a bug or non-implementation elsewhere, that may have 
existed for years, that only becomes a problem when certain other conditions 
are met.  Frequently we fix things in PCSX2 and those fixes break many games.  
It's not always because the fix is bugged, but rather because the fix changes 
overall emulation behavior and that can cause other rare-scenario bugs which 
were being missed (by luck) to become problematic.

Original comment by Jake.Stine on 14 Nov 2010 at 2:34

GoogleCodeExporter commented 9 years ago
Thank you jake lol

Original comment by refraction on 14 Nov 2010 at 5:51