Open GoogleCodeExporter opened 8 years ago
GoogleCodeExporter
commented
8 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
8 years ago [deleted comment]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
8 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
8 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
8 years ago Happens to me when i try to promote boydOriginal comment by Osadd...@gmail.com on 19 Feb 2015 at 11:57
GoogleCodeExporter
commented
8 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
8 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
8 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
8 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
8 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
8 years ago [deleted comment]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
8 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
8 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
8 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
8 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
8 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
8 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
8 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
8 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
8 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
8 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
8 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
Original issue reported on code.google.com by
sOccu...@gmail.comon 12 Sep 2014 at 3:57Attachments: