Project

General

Profile

Actions

Emulator Issues #4427

closed

r 7477 unstable with Spartan total warrior

Added by SeeebM over 13 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

Loadings are VERY longs in Spartan total Warrior (GC) and there are
appcrashes with a "BEX" message in release 7477.

Works fine with r6175.

On Win 7 32-bit

Game ID : GWAE8P (ISO dumped from disc).

Actions #1

Updated by Sonicadvance1 over 13 years ago

What revision broke it?

Actions #2

Updated by SeeebM over 13 years ago

In fact I don't know. I tried to play the game with the latest release
but I had bugs. So i Tried some older releases and with release 6175 there is
no appcrash and loadings times are "normals".

Actions #3

Updated by SeeebM over 13 years ago

EDIT : The newest the release is the longest the loadings are and game crashes
with all the 7xxx releases I tried (appcrash or BEX message after some minutes)
but I don't know why.

Actions #4

Updated by DimitriPilot3 over 13 years ago

"Loadings are VERY longs in Spartan total Warrior (GC)"

Hmm... By curiosity, can you confirm that r7318 is the cause of your problem? (I thought my problem started with r7328, but further testing proved me otherwise...)
To put it simply:
In Pokémon Colosseum (PAL version), for example, r7318 seems to take about 2x as much time as r7317, to go from the first black frame of the last intro video to the actual 3D title screen. I'm quite sure this isn't okay to me...
By the way, this issue doesn't occur when "Speed up disc transfer rate" is enabled, and I am using Mamario's Win32 builds, if that matters.

Either something is wrong with the fix in r7318, or the transfer rate constants should be revised, or everything is okay and this is the correct speed (although I don't think so)...

Actions #5

Updated by SeeebM over 13 years ago

"By curiosity, can you confirm that r7318 is the cause of your problem?"

Yes I confirm. Loadings times to start the first mission (new game):

r5991 : 1 s (release used in the wiki to test the game)
r6175 : 2 s (the release I use)
r7317 : 5 s
r7318 : 38 s
r7477 : 38 s

Actions #6

Updated by Anonymous over 13 years ago

Did the crashes begin to happen at the same revision?

Actions #7

Updated by SeeebM over 13 years ago

No. Although loadings become very long with r7318, the r7317 crashes after 5 minutes playing.

The game often crashes after checkpoints (r7317).
For example, in the mission "The Badlands", the game crashes every time after the first
checkpoint.

Actions #8

Updated by SeeebM over 13 years ago

The same thing happens with r7318.

Actions #9

Updated by SeeebM over 13 years ago

I have just found the file exceptioninfo.txt :

Unhandled Exception
Code: 0xC0000005
Call stack info:
ntdll!0x77882D37 : RtlFreeHeap

Unhandled Exception
Code: 0xC0000005
Call stack info:
ntdll!0x77882D94 : RtlFreeHeap

Unhandled Exception
Code: 0xC0000005
Call stack info:
ntdll!0x773B2D37 : RtlFreeHeap

Actions #10

Updated by DimitriPilot3 over 13 years ago

Do the "random" crashes still occur if the "Speed up disc transfer rate" option is ticked in the game properties? Do they still occur using one of the recent revisions? (most likely the answer is yes, but just in case...)

Since you say it is crash-free using (a build of) r6175, and that it crashes with "all of the 7xxx builds you tried" (try being more descriptive here, what's the earliest revision/build you tried that crashed? does r6995 crash as well?), that would mean the "culprit" is between r6176 and insert-buggy-revision-number-here. Try narrowing it down to as few revisions as possible, with "trial and error" (start with r6500, r6700, etc).

(With some luck, issue 4427, issue 4568 and the issue that caused a few RtlFreeHeap crashes for me, may be the same issue...)

Actions #11

Updated by SeeebM over 13 years ago

It's magical ! With r7589 everything works fine. Loadings are very fasts and I can play the entire mission "The badlands" (I didn't play a long time).
I don't understand...
Problem with loadings is resolved. For the stability, I have to make a longest test.
Good work anyway :)

And yes the "Speed up disc transfer rate" was ticked every time. And r6995 doesn't look to crash (Ialways test with tes same mission).

Actions #12

Updated by SeeebM over 13 years ago

Oups ! I took a look ar issue 4549 and I think I made a mistake.
In fact I though a "blue square" meant option ticked but it mean option unticked.
And effectivly, with "Speed up disc transfer" truly ticked, loadings are normals.
It's my fault, but the GUI is ambiguous...

Actions #13

Updated by kostamarino over 13 years ago

  • Status changed from New to Fixed

The game ini changes should have this fixed.

Actions

Also available in: Atom PDF