Project

General

Profile

Actions

Emulator Issues #6284

closed

PAL Muramasa black screen with progressive scan

Added by tomman about 12 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Do not attach files to this issue. Upload them to another site and
link here. Use imgur.com for images.

Have you searched the issue tracker for a similar issue?
Somewhat related? Issue 6114... which was also filled by me.

Game Name?
Muramasa: The Demon Blade (Wii), PAL

Game ID?
RSFP99

What went wrong?
Yet another Dolphin update that somehow manages to cause problems with the one and only Wii game that (mostly) justifies the presence of Dolphin in my computer. On master-3.5-1081 it was working. Finished the game for the first time, forgot about it, then decided to take it back. As usual, decided to update my Dolphin first (master-3.5-1307 as of now). Now the display "vibrates" when I run my PAL Muramasa (not the same flickering as experienced on Issue 6114). Other games don't seem to exhibit this issue (PAL GC Puyo Pop, NTSC WiiWare Sonic 4). However, if I disable XFB emulation, display is stable (and I don't notice any graphic glitch so far)

What did you expect to happen?
Game should run with stable video (as in "not in a earthquake"), just like it did in -1081

What steps will reproduce the problem?

  1. Get PAL Muramasa
  2. Run game
  3. Watch the earthquake on your display.

What version of Dolphin were you using (please test the latest version
from http://dolphin-emu.org/download first, 3.5 or 3.5-367 are not valid
tests!)?
3.5-1307, freshly built from git-master

64 or 32 bit Dolphin?
64-bit

What version of Dolphin used to work?
Game was working fine on 3.5-1081

What Operating System were you using and what are your hardware
specifications?
Debian Wheezy/testing AMD64
Intel Core i5-2450M (Sandy Bridge) laptop
Intel HD Graphics 3000 / nVidia GeForce 610M (through bumblebee/Primus)

64 or 32 bit Operating system?
AMD64

Any other relevant information or links to logs:
I haven't changed my system settings since the last-reported bug, aside of the usual Debian updates. I'm playing the game on the nVidia card (as Wheezy's Mesa version is kinda buggy, so no HD3000 love).

Actions #1

Updated by skidau about 12 years ago

This is expected behaviour because the game is drawing on an interlaced screen. If you machine can handle it, try enabling progressive scan in the advanced graphics settings. Be prepared for a significant drop in performance, though. My advice would be to turn off XFB as I don't think it fixes anything for this particular game.

Actions #2

Updated by tomman about 12 years ago

Aha! I also had the same thought (the shaking looks like a bad video deinterlacer).

Tried enabling progressive scan... just to be greeted with a black screen and a unbootable game.

Ah well, the game seems to be look just fine without XFB enabled, so I'll continue with it.

Is there a way to turn off XFB for a single game and not globally? - the game-specific settings provide no option for that.

Actions #3

Updated by skidau about 12 years ago

No, there isn't a way to turn off XFB for a single game.

I'll keep this issue open for a bit to investigate the progressive scan issue.

Actions #4

Updated by skidau about 12 years ago

The combination of XFB + Progressive scan also causes Xenoblade PAL to crash.

Actions #5

Updated by Billiard26 about 12 years ago

  • Issue type set to Bug
Actions #6

Updated by OPajot about 12 years ago

I also have this problem with some of my GameCube PAL games :

  • Dead to Rights GDRP68
  • Eternal Darkness GEDP01
  • Hitman 2 GHMF4F
    and disabling XFB was enough for them.

Unfortunately, Summoner: a Goddess Reborn (GS2P78) need the XFB. It's even enforced by the game settings.

By the way tom, you can disable XFB for a game with:
[Video_Settings]
UseXFB=False

Actions #7

Updated by phire almost 11 years ago

Does this still occur on the latest dev builds of dolphin? This bug should have been fixed October last year.

Actions #8

Updated by JMC4789 over 10 years ago

  • Status changed from New to Fixed

No response, assuming fixed. If someone is still having this issue, please post it here and the issue will be opened back up.

Actions

Also available in: Atom PDF