Project

General

Profile

Actions

Emulator Issues #5678

closed

Battalion Wars - GFX FIFO 0x03

Added by decfabrice over 11 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

Game Name : Battalion Wars USA (G8WE01)

The game crashes extremely frequently and is almost unplayable. It suddenly freezes with or without an error (some times GFX Fifo, some type desync, with various opcodes like GFX FIFO 0x03).

The game worked flawlessly (but slowly) with r7607 (tested quite extensively on this revision). Not tested extensively enough on newer revisions to tell if there is a bug or not (since it appears randomly).

After the crashes I have FPS = 0 and VPS = 60 (but the values do not seem updated anymore).

4) What steps will reproduce the problem?
Play for a few minuts. Seems to appear with a higher probability in mission 2 after the bridge, when the bombers arrive.

  1. What version of dolphin are you using
    r 3.0-796-dirty x64 on Windows 7 Home x64, corei7 Q720M 4x1.6 GHz, Nvidia GT320M (laptop).
    Note that as each of the cores of the processor is not extremely fast, it should be a good way to reveal sync issues.

6) Please provide any additional information below.
Tested with various configurations (Directx 9, 11, OpenGL, JIT/JITIL, DSP HLE, LLE, Nosound) and with various hacks enabled or disabled. The bugs appear more frequently with MMU activated (but deactivating it doesn't suppress them completely).
My configuration of the emulator is pretty standard (nothing changed)

  1. Attachments
    Here is a statesave just before a moment where the bug is likely to occur (>90% chance to get it on my laptop)
    https://skydrive.live.com/redir?resid=7526A995241065CC!800
Actions #1

Updated by hatarumoroboshi over 11 years ago

Have you tried to disable the dual core enable option?

Actions #2

Updated by Sonicadvance1 over 11 years ago

Have you tried without using savestates since those are really buggy?

Actions #3

Updated by decfabrice over 11 years ago

I have tried without dual core. Still the same.
I have tried without savestates, too (not so extensively obviously because I need to wait longer for the bug to appear). Still bugs.

Actions #4

Updated by decfabrice over 11 years ago

Little precision : when the bug (or bugS) occur(s), there is not necessarily something special on screen (I mean, no heavy particle effects, no lag, no nothing) or no special sound effects (voices or stuff). It is just during gameplay. Happens in window and fullscreen mode.

Actions #5

Updated by skidau over 11 years ago

Would you please identify the revision where this issue started? Start from 3.0-483 to the latest.

Actions #6

Updated by marcosvitali over 11 years ago

Interesting, I never see this game.

Actions #7

Updated by decfabrice over 11 years ago

OK, I will try to look for the revision, even though I suspect it was a bug hidden in the previous revisions that became visible because some other part of the emulator became faster, so there is a race condition or something like that.

If you tell me in which source file the code causing the error could be located, I might have a look at it. I am a developper, but I never worked on an emulator.

I cannot guarantee that I will test the revisions fast because I have a LOT of work to do, so see you in a few weeks.

By the way, when the game crashes, most of the time, I do not get an error code (just freezes with sound looping). But when there is one, then I get a ton of them in a row.

Actions #8

Updated by skidau over 11 years ago

Have a look in Fifo.cpp and CommandProcessor.cpp, but we can't be sure which area is causing this issue as you said that single core mode does not help.

Actions #9

Updated by marcosvitali over 11 years ago

Only post one revision where this game is working, is enought for me. Batalian Wars 2 porgramming sucks, so maybe the first sucks too.
In the pastt the gfx problems are produced because of fifo reset or CPREad cpRW pointers writed for the games.

Thanks.

Actions #10

Updated by decfabrice over 11 years ago

No problem. I finally found the time to test the revisions. Here are the results for the 3.0- versions:
374 OK
590 OK
673 OK (sometimes freezes for about 1 sec but recovers)
680 bugged
683 bugged
But maybe I didn't play long enough on 673 version since the thing is random.

I wish it will be of some help for you guys.

Actions #11

Updated by Autoran1 over 11 years ago

, please, can you give me some sort of save not a savestate which is closes to the issue point

Actions #12

Updated by marcosvitali over 11 years ago

Thanks, I will ask for a friend who has this game for test :) I need some days.

Actions #13

Updated by marcosvitali over 11 years ago

Like said, if you have a savestate, please attach this.

Actions #14

Updated by Autoran1 over 11 years ago

Yes i think i've found one freeze spot in the first mission, but i have no GFX FIFO messages

Actions #15

Updated by decfabrice over 11 years ago

Sometimes, there is no error message.
I will try to give you a save (may take some time because I don't have my gaming machine with me), but you can also take my savestate from the first post, return to the main menu and save, this will create you a clean (memory card) save.
By the way, just complete the first mission (5 minutes) and you will be able to start the (buggy) second mission from a fresh save.

Actions #16

Updated by decfabrice over 11 years ago

Here's your save

Actions #18

Updated by skidau about 11 years ago

decfabrice, would you please retry this with the latest 3.5-393 revision? I was unable to reproduce this one.

Actions #19

Updated by decfabrice about 11 years ago

I just managed to finish mission 2 on the first try, so I guess the issue is solved (version 3.5 - 367). There are now sound problems, but this is another issue. Thanks guys for the good work on the emu.

Actions #20

Updated by skidau about 11 years ago

  • Status changed from New to Fixed
Actions

Also available in: Atom PDF