if you didnt read the message I wrote you should completely reformat the stick including a new MBR.no i don't use emulators on it, but i can confirm that usb loader gx works
if you didnt read the message I wrote you should completely reformat the stick including a new MBR.no i don't use emulators on it, but i can confirm that usb loader gx works
ok i will do thatif you didnt read the message I wrote you should completely reformat the stick including a new MBR.
I'm thinking of testing the retail disc with the official Mios to confirm the issue.Sonic Adv. 2 and Chao Garden is working fine for me using one real, official 59 blocks MC with Nintendont 349, 350 and 352.
I will test later the problem you described using two MCs to transfer Chaos between them.
yea for the triforce games I really need to think about generating some sort of empty file before starting the game to ensure it does not crash, creating a file mid-game is unstable for the nintendont kernel. also unrelated, just played most wanted for a while, was quite fun, I didnt play it in so long that all I could do is focus on me driving and not look at any HUD elements heh.
I confirm I'm having the same issue in Chao Garden, it's impossible to trade Chaos from real MC-A to real MC-B and vice versa.I'm thinking of testing the retail disc with the official Mios to confirm the issue.
Edit: I will have to mention that all 3 MCs I have are first party, one is (200?) blocks and the other two are 59 blocks, I'm not sure if third party MCs work better, I recall when Nintendont started having real MC support it worked better with third party ones, after a few updates and fixes it finally got a proper fix for first party MCs.
Funny, I was just about to report the exact opposite, I tested the game on real disc "official Mios" and all three MCs worked fine for me but the game had issues detecting the Chao from the other MC, it can only deletect the Chao only from the same MC that you load the game data from.I confirm I'm having the same issue in Chao Garden, it's impossible to trade Chaos from real MC-A to real MC-B and vice versa.
Appart from that issue, Chao Garden is working as expected, and Nintendont (v352) always read and write on both of my official MC without issues.
I also cloned data from MC-A to MC-B, lol. I'm gonna create new data and come back to report.As it turned out, I made a mistake with my save as I accidentally duplicated the same Chao garden data on all 3 MCs which is why it did that, I tried starting a new one and ti worked fine, I also tried re-installing my old back up for each one of the three cards and they worked fine.
incase you didnt know nintendont never touches the real MC, when mcemu is off nintendont just lets the mios code for memory cards run everything, nintendont never reads, writes or even touches memory cards if mcemu is off, that is all mios doing.Funny, I was just about to report the exact opposite, I tested the game on real disc "official Mios" and all three MCs worked fine for me but the game had issues detecting the Chao from the other MC, it can only deletect the Chao only from the same MC that you load the game data from.
As it turned out, I made a mistake with my save as I accidentally duplicated the same Chao garden data on all 3 MCs which is why it did that, I tried starting a new one and ti worked fine, I also tried re-installing my old back up for each one of the three cards and they worked fine.
With that being said, the MCs being not detected or getting corrupted still happens when used with Nintendont, not sure if it's because of it or maybe my MC tray are wearing off, they seem to work fine when using the official Mios, idk...
Have you tried it outside of Nintendont? It could be it's starting to go bad. You could also try running it without the BIOS just to try to rule out anything.Just tried gc bios with real memory card and there seems to be an issue with mounting the memory card. It shows up as an incompatiple object in slot A at the bios screen and when loading the game, it says that the memory card is damaged and can't be used. Simply removing and reincerting it fixes it though but it's realy strange.
Using official 1019 memory card.
Unfortunately, the 1019 block card has compatibility issues with the Wii for some reason. Anytime I used them with the Wii, my saves either got corrupted or I was forced to reformat the card. Switch to a 256 Block card and the issue went away. I know some games have issues with the 1019 card as they weren't designed with a card that size in mind. There is only one game that I know of that requires it as it uses over 300 blocks.Just tried gc bios with real memory card and there seems to be an issue with mounting the memory card. It shows up as an incompatiple object in slot A at the bios screen and when loading the game, it says that the memory card is damaged and can't be used. Simply removing and reincerting it fixes it though but it's realy strange.
Using official 1019 memory card.
yes.are the triforce bios stable for mario kart gp and f-zero?
I've always used the card with Dios Mios, retail games, Nintendont and it has never failed me. After removing the bios file from the SD card Nintendont boots directly into the game and the save file loads just fine so it seems like an issue with loading the Bios.Have you tried it outside of Nintendont? It could be it's starting to go bad. You could also try running it without the BIOS just to try to rule out anything.
I'm aware of the slight incompatibility issues with the 1019 block memory card but it's always worked perfectly on my end. Just to be sure, I tested loading a game with Bios enabled with both a 256 and a 59 block memory card and had the same issue so I'm certain that rules out the 1019 being the issue here. When the game starts, a message mentions the memory card being "damaged" but pulling it out and reinserting it while the game's running fixes it and the save data pops up just fine.Unfortunately, the 1019 block card has compatibility issues with the Wii for some reason. Anytime I used them with the Wii, my saves either got corrupted or I was forced to reformat the card. Switch to a 256 Block card and the issue went away. I know some games have issues with the 1019 card as they weren't designed with a card that size in mind. There is only one game that I know of that requires it as it uses over 300 blocks.
I had this issue way before Nintendont was even even thought of.
I tried the same cards on my GameCube and no issues.
Then it's probably my MC tray that's wearing off, it's weird because they work fine whenever I'm on the Wii menu, I been using these MCs since 2002 so that's about 13 years of serves.incase you didnt know nintendont never touches the real MC, when mcemu is off nintendont just lets the mios code for memory cards run everything, nintendont never reads, writes or even touches memory cards if mcemu is off, that is all mios doing.
What are the odds we both get the same issue, lol anyway I guess the issue is on my end then, sorry for the trouble.I also cloned data from MC-A to MC-B, lol. I'm gonna create new data and come back to report.
Anyways, I'm not having data corruption.
Edit: That's it, the problem was having the same Chao Data on both MCs, so no problem on Nintendont's side.
1. Some games don't work right when shrunk but most do. It is always recommended for first timers to use full 1:1 MD5 checked ISOs.Does shrinking isos cause any problems? And does it matter if games are iso or gcm?
The compatibility list isn't accurate anymore for shrunk ISOs.There isnt a list that shows which games work shrunk and not?
if you use DMtoolbos to shrunk them your good for all games besides 4 or 5.There isnt a list that shows which games work shrunk and not?
nvm seem like the wiki has it to an extent
what nintendont version are you using? just wondering becuase the issue you said was an issue before we had the card unlock code wich was like 100 revs ago or more.I've always used the card with Dios Mios, retail games, Nintendont and it has never failed me. After removing the bios file from the SD card Nintendont boots directly into the game and the save file loads just fine so it seems like an issue with loading the Bios.
I'm aware of the slight incompatibility issues with the 1019 block memory card but it's always worked perfectly on my end. Just to be sure, I tested loading a game with Bios enabled with both a 256 and a 59 block memory card and had the same issue so I'm certain that rules out the 1019 being the issue here. When the game starts, a message mentions the memory card being "damaged" but pulling it out and reinserting it while the game's running fixes it and the save data pops up just fine.
I've also managed to replicate the "damaged" memory card issue by loading a game using Nintendont through USB Loader GX, using the button combo to go back to the launcher and loading the game again or an other game. The memory card will then be unusable until reinserted or restarting the console. Tested with 59, 256 and 1019 as well.
It's puzzling.