02-14-2010, 11:53 PM
(This post was last modified: 04-01-2010, 09:43 PM by andutrache.)
I'm currently racking a bug and i need to know something so i can narrow it down to a revision.
Now for some detailed info:
The game is Galaxy Angel II Mugen Kairou no Kagi.
The error appears during a FMV and i get theese error messages on the WX version:
EE: Unrecognized op 766e6152
EE: Unrecognized MMI op 71767778
EE: Unrecognized COP0 op 4047525e
and the emu crashes with a Runtime Error.
Also in r1385-legacygui after those errors:
(EE) Tlb Miss, addr=0x6a5a [load]
(EE) PC: 0x21c7af10 Cycle: 0x4b17bed7
In pcsx2-WX the console is spammed with "libpad: sceSifSetDma faild" in 0.9.6 and r1385 it appeared only once or twice.
Tried the EE,IOP,both VU's in interpreter mode (on PCSX2-WX) and got only this error:
Unknown MMI opcode called
then Runtime Error.
So i'm asking at what revision was Pcsx2 0.9.6 released because this bug isn't present there. I suppose its older than r1385-legacygui which has the bug.
This bug persists even in r2586-WX.
P.S: Speedhacks were DISABLED.
L.E: ok i found out 0.9.6 was around r600 (thanks Gigaherz) now working on narrowing the bug
Now for some detailed info:
The game is Galaxy Angel II Mugen Kairou no Kagi.
The error appears during a FMV and i get theese error messages on the WX version:
EE: Unrecognized op 766e6152
EE: Unrecognized MMI op 71767778
EE: Unrecognized COP0 op 4047525e
and the emu crashes with a Runtime Error.
Also in r1385-legacygui after those errors:
(EE) Tlb Miss, addr=0x6a5a [load]
(EE) PC: 0x21c7af10 Cycle: 0x4b17bed7
In pcsx2-WX the console is spammed with "libpad: sceSifSetDma faild" in 0.9.6 and r1385 it appeared only once or twice.
Tried the EE,IOP,both VU's in interpreter mode (on PCSX2-WX) and got only this error:
Unknown MMI opcode called
then Runtime Error.
So i'm asking at what revision was Pcsx2 0.9.6 released because this bug isn't present there. I suppose its older than r1385-legacygui which has the bug.
This bug persists even in r2586-WX.
P.S: Speedhacks were DISABLED.
L.E: ok i found out 0.9.6 was around r600 (thanks Gigaherz) now working on narrowing the bug