Project

General

Profile

Emulator Issues #3491

Tatsunoko vs Capcom - grey flashing screen when Hurrican Polimar is selected

Added by himuradrew almost 10 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
GFX
% 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

What steps will reproduce the problem?
1. Using the DX11 plugin.

What is the expected output? What do you see instead?
- After selecting Polimar, the game should proceed as usual. Instead a flashing grey screen will be seen, but the game will continue as if nothing happens. Unfortunately, player will not be able to see what's going on.

Dolphin version with the problem? Other Dolphin version without the
problem?
- So far all revisions I've tried starting from 6364 up to 6385 have exhibited the same problem.

32-bit or 64-bit and any other build parameters?
- Using the 64-bit version

OS version and versions of tools/libraries used?
-Windows 7 Home Premium x64, Core i7-720QM, Mobility Radeon 5870HD (catalyst 10.6 drivers)

Please provide any additional information below.
- Regardless of settings used, the game will exhibit the problem as long as the DX11 plugin is used. When switching to the DX9 plugin, game will run fine.

History

#1 Updated by mariagoitea59 almost 10 years ago

Maybe its your video card because im using gt 8500 1gb in winxp pro and with that character is not show any problem it all.
My pc is:
Asus p5kpl am-se
ram 2gb kingston
geforce i already told you
intel core 2 quad q8400 2.66
maybe it lower than youre pc but it works great for me.
Pd:Im using 6148 svn and the only problem is the black shadows when you get it and block the hit by guard.

#2 Updated by NeoBrainX almost 10 years ago

Hi there,

It's possible that your issue is a regression (i.e. the stuff did work at some point but broke with a recent changeset). Regressions can be easy to fix if a developer knows which revision of Dolphin caused the regression. However, testing which revision broke anything can be a damn time-consuming task or even impossible if you can't reproduce it (while the mistake in the affected commit might be obvious). Thus, we (the Dolphin devs) heavily depend on our users telling us proper information. That is, it would be nice of you if you checked different Dolphin builds until you can tell us for sure which revision caused this issue (or if it has been broken all the time). You'll certainly get more developer feedback then (if you don't, we really have no idea) and the issue will more likely be fixed soon.

FWIW, you don't need to test all revisions back to when dx11 was introduced, but "6364 up to 6385" isn't really that helpful, sorry.

#3 Updated by himuradrew almost 10 years ago

Hi yeah, sorry about that. I only actually found out about Dolphin recently so I only started using it with build R6364.

Here are all the revisions I've tried:
r6364
r6367
r6372
r6378
r6379
r6380
r6381
r6385

I just currently downloaded r6399. Will try and see if the problem is still there.

Thanks again.

#4 Updated by Billiard26 over 7 years ago

  • Status changed from New to Questionable
  • Issue type set to Bug
  • Category set to gfx

Is the issue present in Dolphin 3.5?

#5 Updated by Billiard26 over 7 years ago

  • Status changed from Questionable to Fixed

Assuming fixed. If not, state otherwise.

Also available in: Atom PDF