Emulator Issues #3198
closed
Castlevania Rebirth not working with "copy to RAM" selected.
0%
Description
What steps will reproduce the problem?
1.Select copy to RAM in any gfx plugin.
2.Load Castlevania Rebirth and reach to the point where you select "start game", black screen after that.
What is the expected output? What do you see instead?
Same as with "copy to texture" selected, games starts normally.
Dolphin version with the problem? Other Dolphin version without the
problem?
6181 and 6197, last working version is 6110
32-bit or 64-bit and any other build parameters?
32-bit
OS version and versions of tools/libraries used?
WinXP SP3
Please provide any additional information below.
If bug can't be confirmed locally videos will be provided.
Updated by otomospirits about 14 years ago
My mistake, is not even working in 6110. As a reference, other games like Crystal Defenders and the newer Blaster Master Overdrive are working with copy to RAM selected.
Updated by
Updated by miltos07 over 13 years ago
I can confirm that copy to RAM causes the blank screen issue in r7434.
DX9 and OpenGL renderers work fine with copy to texture, DX11 causes graphics glitches even before starting the game and sometimes totally scrambled output. It seems that this issue needs reopening. I hope this info helps. You can see attached screenshot.
Updated by Billiard26 almost 12 years ago
- Issue type set to Bug
- Category set to gfx
Updated by tommyhl2.SS almost 12 years ago
- Status changed from New to Accepted
I can confirm this as well. EFB to Ram after the "start game" button is pushed, the screen is black and goes to 0fps. EFB to Texture works normally.
Updated by JMC4789 over 10 years ago
I can confirm this is still happening in 4.0-1533
Updated by JMC4789 over 10 years ago
- Category deleted (
gfx)
This is a GPU synchronization issue much like F-Zero GX and many other games.
Using single core + EFB2Ram works fine.
Not sure this should be accepted or merged into something else?
Updated by JMC4789 over 10 years ago
- Status changed from Accepted to Duplicate
Going to make a judgment call and merge this with the "dualcore is unstable" master issue. Anyone else with issue rights can override me if you disagree.