Felloyo / nintendon-t

Automatically exported from code.google.com/p/nintendon-t
0 stars 0 forks source link

White screen on loading battle map - Fire Emblem Path of Radiance [PAL] #85

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

Start and play Fire Emblem up until you'd expect a battle map to be loaded 
(usually directly after the Chapter screens). The game fails to load the battle 
map and gets stuck on a white screen. Happens intermittently, sometimes the 
screen will pass without issue.

What is the expected output? What do you see instead?

Expected output is the battle map/scenario being loaded and playing. White 
screen hang is the actual outcome 70% of the time.

What revision of Nintendont are you using? On what system Wii/Wii U?

I have noted this issue in Nintendont 2.157, 2.155, 2.152 and 2.120. Crash/Hang 
happens with equal chance across all versions. 

System is a Wii - system menu 4.3E (Europe). 

Please provide any additional information below.

The iso is being launched from a USB. I have tried several iso versions (both 
from my own disc and from various internet sources). 

Memory Card emulation is on, with a block size of 251. No multi-card. 

Nintendont is being launched directly from the Homebrew Channel.

Here is what I believe to be the relevant extract from the log file. The full 
file is attached.

[------------- Nintendont IOS55 v22.31
Built   : Sep 10 2014 19:36:48
Version : 2.157
Game path: /games/[GFEP01] FIRE EMBLEM GC EU/game.iso
EXIInit Start
Trying to open GFEP.raw
DIP:DOLsize:2819204 DOL read:9728
Patch:[Patch31A0]
DIP:DOLsize:2819204 DOL read:2545472
DIP:DOLsize:2819204 DOL read:2545536
DIP:DOLsize:2819204 DOL read:2545632
DIP:DOLsize:2819204 DOL read:2545824
DIP:DOLsize:2819204 DOL read:2545856
DIP:DOLsize:2819204 DOL read:2662880
DIP:DOLsize:2819204 DOL read:2803360
DIP:DOLsize:2819204 DOL read:2804224
DIP:DOLsize:2819204 DOL read:2819232
Patch: Offset:0x00003100 EOffset:0x002B3584 Length:002B0484
Patch: Game ID = 47464550
AI:[0021089C] 3C80CD00: lis r4, 0xCD00
AI:[002108B8] 3C80CD00: lis r4, 0xCD00
AI:[00210C80] 3C60CD00: lis r3, 0xCD00
AI:[0021C5F0] 3C80CD00: lis r4, 0xCD00
AI:[0021C630] 3C60CD00: lis r3, 0xCD00
AI:[0021C660] 3C60CD00: lis r3, 0xCD00
AI:[0021C690] 3FE0CD00: lis r31, 0xCD00
AI:[0021C750] 3C60CD00: lis r3, 0xCD00
AI:[0021C784] 3FE0CD00: lis r31, 0xCD00
AI:[0021C838] 3C60CD00: lis r3, 0xCD00
AI:[0021C848] 3C80CD00: lis r4, 0xCD00
AI:[0021C864] 3C60CD00: lis r3, 0xCD00
AI:[0021C874] 3C80CD00: lis r4, 0xCD00
AI:[0021C890] 3C60CD00: lis r3, 0xCD00
AI:[0021C94C] 3CC0CD00: lis r6, 0xCD00
AI:[0021CA1C] 3FE0CD00: lis r31, 0xCD00
AI:[0021CBB4] 3FE0CD00: lis r31, 0xCD00
SI:[00243984] 3C60D302: lis r3, 0xD302
SI:[00243AB4] 3CC0D302: lis r6, 0xD302
SI:[00243C48] 3C60D302: lis r3, 0xD302
SI:[00243C80] 3CA0D302: lis r5, 0xD302
SI:[00243D98] 3C60D302: lis r3, 0xD302
SI:[00243FE8] 3C80D302: lis r4, 0xD302
SI:[00244264] 3C60D302: lis r3, 0xD302
SI:[00244318] 3CC0D302: lis r6, 0xD302
SI:[002443F8] 3C80D302: lis r4, 0xD302
SI:[002444AC] 3CC0D302: lis r6, 0xD302
SI:[002444F4] 3C80D302: lis r4, 0xD302
SI:[00244558] 3C60D302: lis r3, 0xD302
SI:[00244568] 3C60D302: lis r3, 0xD302
SI:[002445A8] 3C80D302: lis r4, 0xD302
SI:[0024464C] 3C80D302: lis r4, 0xD302
SI:[002446C0] 3C80D302: lis r4, 0xD302
SI:[00244714] 3C80D302: lis r4, 0xD302
SI:[00244764] 3C60D302: lis r3, 0xD302
SI:[002447FC] 3C60D302: lis r3, 0xD302
Patch:Found [SetInterruptMask]: 0x002109DC
Patch:[__OSDispatchInterrupt] 0x00210B90
Patch:Found [__DVDIntrruptHandler]: 0x00214338 (0x00214338)
Patch:[__DVDInterruptHandler] 0x00214394
Patch:[DVDLowReadDiskID] 0x00214B90
Patch:[DVDLowStopMotor] 0x00214C50
Patch:[cbForStateBusy] 0x00217394
Patch:[cbForStateBusy] 0x002175F0
Patch:[cbForStateBusy] 0x002175F4
Patch:[cbForStateBusy] 0x00217600
Patch:[cbForStateBusy] 0x00217604
Patch:[cbForStateBusy] 0x0021765C
Patch:[cbForStateBusy] 0x00217660
Patch:[VIConfigure] 0x00219A20
Patch:[DSPPattern] 0x002ACB80 v12
Patch:[DSPROM] DSPv9
PatchCount:00000FFF
Patch:Found [C_MTXLightPerspective]: 0x0020B3C8
Patch:Found [C_MTXPerspective]: 0x0020B5C4
Patch:Found [__OSResetSWInterruptHandler]: 0x00211980
Patch:__OSResetSWInterruptHandler FakeRSWLoad
Patch:__OSResetSWInterruptHandler FakeRSWLoad
Patch:__OSResetSWInterruptHandler FakeRSWStore
Patch:Found [OSGetResetButtonState A]: 0x00211A74
Patch:OSGetResetButtonState FakeRSWLoad
Patch:Found [DVDLowRead A]: 0x0021469C
[002146E8] 3C80C000: lis r4, 0xC000
[002146F4] 38842F00: addi r4, r4, 0x2F00
[002146F8] 3C60A700: lis rX, 0xA700
Patch:Found [DVDLowAudioStream A]: 0x00214DDC
Patch:Found [DVDLowRequestAudioStatus]: 0x00214E74
Patch:Found [DVDLowAudioBufferConfig]: 0x00214F00
Patch:Found [DVDInquiryAsync A]: 0x00217BA8
Patch:Found [DVDGetDriveStatus]: 0x00217D08
Patch:Found [PADRead B]: 0x0021B71C
Patch:Found [PADControlMotor A]: 0x0021BA1C
Patch:Found [AIInitDMA]: 0x0021C4BC
Patch:Saving Audio Locations
Patch:Found [ARStartDMA]: 0x0021CDF0
Patch:[ARStartDMA] Length 0
Patch:[ARStartDMA] 0x0021CDF0
Patch:Found [__ARChecksize B]: 0x0021D0C4
Patch:[__ARChecksize B] 0x0021D434
Patch:Found [ARQPostRequest]: 0x0021EAF8
Patch:Skipped [ARQPostRequest]
Patch:Found [__DSPHandler]: 0x0021EE6C
Patch:Added Audio Mixer
Patch:Found [__CARDReadStatus]: 0x0021FB04
Patch:Found [__CARDClearStatus]: 0x0021FCE4
Patch:Found [__CARDStat C]: 0x002201E4
Patch:Found [PADIsBarrel]: 0x00220990
Patch:Found [PI_FIFO_WP D]: 0x00227DFC
Patch:Patched [PI_FIFO_WP D] 0x00227E3C
Patch:Found [PI_FIFO_WP C]: 0x00227F14
Patch:Patched [PI_FIFO_WP C] 0x00227F28
Patch:Found [GXInitTlutObj B]: 0x00228914
Patch:Found [GXInitTlutObj B]: 0x0022BA00
Patch:[GXInitTlutObj] 0x0022BA00
Patch:Found [PI_FIFO_WP E]: 0x0022D700
Patch:Patched [PI_FIFO_WP E] 0x0022D734
Patch:Found [__fwrite A]: 0x00239A54
Patch:Skipped [patch_fwrite_Log]
Patch:Found [EXIImm]: 0x0024196C
Patch:Found [EXIDMA]: 0x00241C68
Patch:Found [EXISync]: 0x00241D54
Patch:Found [__EXIProbe]: 0x00242064
Patch:Found [EXISelect]: 0x002424D4
Patch:Found [EXIDeselect]: 0x00242600
Patch:Found [EXIntrruptHandler B]: 0x00242710
Patch:Applied **IntrruptHandler patch 0x242710 (PatchOffset=0x4) 
Patch:Found [TCIntrruptHandler B]: 0x002427D8
Patch:Applied **IntrruptHandler patch 0x2427D8 (PatchOffset=0x4) 
Patch:Found [EXILock]: 0x00242C94
Patch:Found [EXIUnlock]: 0x00242D88
Patch:Found [CompleteTransfer A]: 0x00243980
Patch:[CompleteTransfer] 0x00243980
Patch:Found [SIInterruptHandler A]: 0x00243C7C
Patch:Applied **IntrruptHandler patch 0x243C7C (PatchOffset=0x8) 
Patch:[SIInterruptHandler] 0x00243C7C
Patch:Found [SIEnablePollingInterrupt A]: 0x00243FC0
Patch:[SIEnablePollingInterrupt A] 0x00243FC0
Patch:[SIEnablePollingInterrupt A] 0x00243FC0
Patch:Found [SIInit A]: 0x00244218
Patch:[SIInit] 0x00244218
Patch:Found [_SITransfer A]: 0x002442CC
Patch:[_SITransfer] 0x002442CC
Patch:[_SITransfer] 0x002442CC
Patch:Found [SITransfer]: 0x00244910
Patch:Skipped [SITransfer]
Patch:Found [SIGetType A]: 0x00244D14
Patch: [DVDSeekAbsAsyncPrio] not found
Patch: [GXInitTlutObj A] not found
Patch: [J3DUClipper::clip()] not found
Patch: [J3DUClipper::clip()] not found
Patch: [GCAMSendCMD] not found
Patch: [GCAMRead] not found
Patch: [GCAMExecute] not found
Patch: [GCAMWrite] not found
Patch: [GCAMIdentify] not found
Patch: [GCAMSendCommand] not found
Patch: [__GXSetVAT] not found
Patch: [PADControlAllMotors A] not found
Patch: [PADControlAllMotors B] not found
Patch: [PI_FIFO_WP A A] not found
Patch: [PI_FIFO_WP A B] not found
Patch: [PI_FIFO_WP B] not found
Patch: [PI_FIFO_WP F] not found
Patch: [__CARDStat A] not found
Patch: [__CARDStat B] not found
Patch: [RADTimerRead] not found
Got Shutdown button call
EXI: Saving memory card...Done!
Nintendont IOS55 v22.31 ------------------]

Original issue reported on code.google.com by sOccu...@gmail.com on 12 Sep 2014 at 3:57

Attachments:

GoogleCodeExporter commented 9 years ago
Also tested with the NTSC version of Fire Emblem, same issue. 

Forgot to mention I'm using a USB Verbatim Hard Drive with a sector size of 
512. 

ISO files are compressed with GameCubeISOCompress software.

Original comment by sOccu...@gmail.com on 12 Sep 2014 at 5:25

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Changing emulated memcard size to 59 blocks will get you past the first chapter 
loading screen hang (first chapter, not prologue hang), but will again hang on 
chapter 2 even with the reduced memcard size.

Original comment by sOccu...@gmail.com on 13 Sep 2014 at 12:23

GoogleCodeExporter commented 9 years ago
Confirmed on 2.162.  Also happens when playing from SD.

Original comment by marcusbl...@gmail.com on 22 Sep 2014 at 7:37

GoogleCodeExporter commented 9 years ago
Getting the same problem here... when started to play for the first time, I was 
able to go even into chapter 2, but the memcard emulation was turned off. Since 
I turned it on, the same problem happens, even after the memcard emulation was 
once disabled again.

Wii 4.3U, Nintendont Version 2.162, wiimote with classic controler, loading 
direct from homebrew channel.

Original comment by faralh...@gmail.com on 28 Sep 2014 at 4:20

GoogleCodeExporter commented 9 years ago
Happens to me when i try to promote boyd

Original comment by Osadd...@gmail.com on 19 Feb 2015 at 11:57

GoogleCodeExporter commented 9 years ago
In my case, just after the chapter 2 title screen, the screen turns totally 
white. I'm using a compressed iso and a real memory card.

Original comment by daniel.p...@gmail.com on 5 Mar 2015 at 8:45

GoogleCodeExporter commented 9 years ago
I also forgot to say that I'm using the NTSC versiona (not PAL).

Original comment by daniel.p...@gmail.com on 5 Mar 2015 at 9:01

GoogleCodeExporter commented 9 years ago
Still happens for me as well.  Memory card vs virtual, NTSC vs PAL, compressed 
vs uncompressed makes not a bit of difference.  It's really too bad that a 
certain rabid fanboy edits this problem out of the gbatemp compatibility table 
every time the game is changed to "Issues" where it belongs.  fix94.1 probably 
thinks the game works perfectly as a result.  I gave up long ago hoping it 
would ever be fixed and play this game using DIOS MIOS Lite.

Original comment by marcusbl...@gmail.com on 5 Mar 2015 at 9:07

GoogleCodeExporter commented 9 years ago
Currently the list blames it on forcing a non-native video mode.  This is, of 
course, nonsense, just like past suggestions it's related to compressed vs 
uncompressed images.  It has nothing to do with region, controller type, 
resolution, memory card type, source device, or anything else implicating the 
user.  The game is simply not fully compatible with nintendont, and to my 
knowledge it is the only remaining top shelf game that remains so.

Original comment by marcusbl...@gmail.com on 5 Mar 2015 at 9:11

GoogleCodeExporter commented 9 years ago
Do you think it will be eventually fixed? I personally don't want to go through 
all the effort of installing DIOS MIOS (especially because of the restriction 
of using original CDs).

Original comment by daniel.p...@gmail.com on 5 Mar 2015 at 9:29

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
What revision of Nintendont are you guys using? While I used to have this 
issue, r2.197 appeared to have addressed it and I haven't updated since. As I 
only use Nintendont for Fire Emblem and Tales of Symphonia, I'm not sure if 
reverting to an old version is viable for you.

Original comment by sOccu...@gmail.com on 7 Mar 2015 at 10:38

GoogleCodeExporter commented 9 years ago
I'm embarrassed to say you're right, it seems it's been fixed.  I heard so many 
times "there is no problem" when I knew there was that I was skeptical that it 
would ever be fixed.  I tested on new builds frequently last year for many 
months and no improvement.  I subscribe to the build RSS but didn't see 
anything suggesting the game was fixed, but it certainly looks like something 
was done that improved Fire Emblem's stability even if that was only a 
secondary effect.

I'll report back if I experience any more hangs, but for now it appears stable, 
granted I could just be getting lucky.  I doubt it.

Original comment by marcusbl...@gmail.com on 13 Mar 2015 at 12:33

GoogleCodeExporter commented 9 years ago
How could it be that a newer revision has issues an older version fixed?

Original comment by daniel.p...@gmail.com on 13 Mar 2015 at 11:21

GoogleCodeExporter commented 9 years ago
What build are you using?  It worked okay in my limited testing yesterday with 
r322.  Builds I tried current up to sometime in the fall of last year were 
unstable with Fire Emblem.

Original comment by marcusbl...@gmail.com on 13 Mar 2015 at 11:35

GoogleCodeExporter commented 9 years ago
@Daniel, occasionally changes present in one version are removed in a newer 
version because of issues it causes, either unforeseen/untested in the old 
version. Or code introduced in a newer version causes conflicts that result in 
circumstances. 

That said, if you're still having issues even on a newer revision then I'd 
suggest testing using an emulated memcard vs the real one. It could be there is 
some conflict between hardware and software memory?

Original comment by sOccu...@gmail.com on 14 Mar 2015 at 12:42

GoogleCodeExporter commented 9 years ago
Thanks for your replies, and sorry for answering so late. I have been using 
Nintendont for about a few weeks. I first installed version 2.252. I have been 
using a real memory card (1019 blocks), the games from a HDD and a Gamecube 
controller. I have been updating Nintendont since then with the Internet update 
option, so I have the latest version installed.

When I wrote my first comment, the white screen appeared after the chapter 
title screen. I tried various configurations of the Configurable USB Loader 
(changing patches, force screen, etc) and returning them to their previous 
configuration, without saving (meaning no changes at all). After loading the 
game, I could finally get past the chapter title screen. 

After finishing that chapter, the white screen reappeared again after the next 
chapter title screen. I tried again the same method used before (playing with 
the configurations, but returning then to their previous configuration when 
booting the game). After that, no chapter had the same problem of the white 
screen again. But now I have another issue: the game crashes without warning 
during gameplay (so I have to restart a chapter all over again). It generally 
occurs when resuming a previously suspended game. It also occurs when doing 
something not involving the gameplay (watching a cutscene, the items or enemy 
info screen). It doesn't occur in the same spot. Sometimes, not even Nintendont 
loads (freezes in the "B: Cancel Autoboot" screen).

Thanks for any help given.

Original comment by daniel.p...@gmail.com on 14 Mar 2015 at 3:31

GoogleCodeExporter commented 9 years ago
Try loading from different media like the front SD slot (format FAT32, 32kB 
sectors).  Also bypass CFG and use the loader direct (forwarder channel is 
convenient) till you work things out.  Just use default settings.  The highly 
varied instability does not sound like a problem caused by Nintendont.

Original comment by marcusbl...@gmail.com on 14 Mar 2015 at 3:44

GoogleCodeExporter commented 9 years ago
I have also loaded the games from Nintendont forwarder channel itself and 
sometime occurs the same problem with the B: Cancel Autoboot screen.

Maybe it is, as you say, the use of a HHD (known for their sometimes unstable 
cable), but when I have played Wii games they never freeze, so I don't really 
think it could be the HDD. 

If I try with a SD card, I'll need to move the Homebrew configuration to a new 
SD card (the one I'm using doen't have enough space for Gamecube games). If I 
do this, is it as simple as copy-pasting the data to a new SD card or do I have 
to configurate something again?

Original comment by daniel.p...@gmail.com on 14 Mar 2015 at 8:53

GoogleCodeExporter commented 9 years ago
It's that simple.  Just be sure to format it the way I mentioned before.  Also 
know some homebrew may not like the higher capacity card, but this won't matter 
for most people.

Original comment by marcusbl...@gmail.com on 14 Mar 2015 at 9:52

GoogleCodeExporter commented 9 years ago
Hmm, I use a HDD for my Wii and GC games (although it's always possible your 
HDD is causing fragmentation issues when transferring games from your computer 
to the drive). Have you tried using an emulated 251 block memcard instead of 
your large real one? 

I use USB Loader GX so I'm not accustomed to CFG Loader, but it sounds like 
that's not the issue. 

Other than that, it does sound like what you're experiencing is a unique 
situation. Perhaps if you grab some debug logs and post them (like I have 
above), someone with a bit more technical knowledge might see a cause. 

Original comment by sOccu...@gmail.com on 15 Mar 2015 at 12:39

GoogleCodeExporter commented 9 years ago
Could you teach me how to get that data to post it, please? 

Original comment by daniel.p...@gmail.com on 15 Mar 2015 at 1:18

GoogleCodeExporter commented 9 years ago
Just try it on different media.  It sounds performance-related and the above 
mention of fragmentation is a good hunch.  Rule that out completely with a 
cleanly formatted SD card.

Original comment by marcusbl...@gmail.com on 15 Mar 2015 at 7:06