Emulator

Have you tried disabling dual core, like the first error message says?

JosJuice wrote:

Have you tried disabling dual core, like the first error message says?

Yes but after the game Crash

JosJuice wrote:

Have you tried disabling dual core, like the first error message says?

Oh I forgot that this problem does not occur on an older version like 5.0-540

then please bisect and find out when it stopped working. that way we can fix it.

JMC4789 wrote:

then please bisect and find out when it stopped working. that way we can fix it.

Any news?

Have you fixed the bug?

So you're saying HybridXFB broke it?

I tested it on latest master on non-Android and it's working fine. It could be an issue with the AArch64 JIT, so, try using the cached interpreter to boot it.

JMC4789 wrote:

So you're saying HybridXFB broke it?

I tested it on latest master on non-Android and it's working fine. It could be an issue with the AArch64 JIT, so, try using the cached interpreter to boot it.

Same not working

What version of the game do you have? PAL?

JMC4789 wrote:

What version of the game do you have? PAL?

Yes

JMC4789 wrote:

It's probably a legitimate regression with Hybrid XFB then.

then?

Considering that it's a PAL version of a game that no one on the team has... either use an older version or try to investigate it yourself until someone is interested enough to check it out themselves. Because HybridXFB had so many issues with PAL games early on, it seems likely that this game uses a strange video mode. I have the NTSC version and everything is fine there.

I'll try to trick the game into running in PAL mode with a bootloader and see what happens personally and report it forward. I can't promise anything will change soon, though.

Okay, after some testing.

A shitty work-around that works in my modified NTSC version is setting the emulated CPU Clock to 6% on boot with single core. Once the game is running it seems to be fine to set the CPU clock to whatever you want.

I'll continue to investigate though.

JMC4789 wrote:

So I did a lot more testing and finally figured things out.

This game has actually never worked in Dolphin's XFB paths - it relied on a lack of emulation. No XFB, which was replaced by Immediately Present XFB copies, emulated so little that whatever is tripping up Dolphin now wasn't an issue. Therefore this isn't exactly a regression (and the bisect isn't as useful) but it at least gives us a starting point to investigation.

The base issue report for this issue kind of sucks (you didn't follow the issue template, which resulted in a lot of wasted time...) so I may replace this issue once I have the actual game instead of relying on a hacked ISO.

Thank you