Homebrew RELEASE Release - Super Mario 64 v8

  • Thread starter Thread starter iriez
  • Start date Start date
  • Views Views 108,304
  • Replies Replies 214
  • Likes Likes 22
I'm just saying that your setup my be peculiar. Maybe something is causing issues there, though I do not know enough about this to tell for sure.

I just tinkered around with a few files from josete2k, had to re-download AMS for 19.0, and eventually it just worked on its own after getting the first star. I'm not really sure what made it stop crashing.
Might try updating to 19? Might also fix my n64 NSO instalation that crashes on startup :yayswitch:
Post automatically merged:

I'm just saying that your setup my be peculiar. Maybe something is causing issues there, though I do not know enough about this to tell for sure.

I just tinkered around with a few files from josete2k, had to re-download AMS for 19.0, and eventually it just worked on its own after getting the first star. I'm not really sure what made it stop crashing.
Updated the firmware and still same result... Is there anything I need to download for firmware 19?
 
Last edited by Rsomethin,
From the system and also check if theres anything in the root of the sdcard
Nope. You have to delete savedata from dBi.
Post automatically merged:

I just tinkered around with a few files from josete2k, had to re-download AMS for 19.0, and eventually it just worked on its own after getting the first star. I'm not really sure what made it stop crashing.


As the fs patch works, I don't add the compatibility patch to my AMS compilation...
 
Nope. You have to delete savedata from dBi.
Post automatically merged:




As the fs patch works, I don't add the compatibility patch to my AMS compilation...
Still same result =( With the patch and deleted save from dbi
 
Ok So I've deleted everything, savegame included, I have uninstalled the game and reinstalled it again, but the mod configuration I made a long time ago still applies. This means that the game is saving some files in the SD card to "remember" this configuration. Does anyone know where this files are saved? Because I'm completely unable to find them. I suspect the problem is there.

Thanks a lot.
 
Ok So I've deleted everything, savegame included, I have uninstalled the game and reinstalled it again, but the mod configuration I made a long time ago still applies. This means that the game is saving some files in the SD card to "remember" this configuration. Does anyone know where this files are saved? Because I'm completely unable to find them. I suspect the problem is there.

Thanks a lot.
Try with clean orphan files form dbi AFTER unistalling the game and deleting the savedata (from dbi too).


Or you can test with this custom AMS.
 

Attachments

  • Like
Reactions: alcab
Nope. You have to delete savedata from dBi.
Post automatically merged:




As the fs patch works, I don't add the compatibility patch to my AMS compilation...
I genuinely don't remember how I got it to work. I tried the exef_patch, I tried your files, I had to re-install AMS 1.8.0 because yours wouldn't boot with CFW 19.0., and after all that it magically worked after getting 1 star.
 
Try with clean orphan files form dbi AFTER unistalling the game and deleting the savedata (from dbi too).


Or you can test with this custom AMS.
Thanks for your help. I tried by deleting the game and its saves again and then cleaning the orphan files by using DBI. It didn't work. But yet again, after reinstalling the game, the previous mod configuration was loaded when starting the game for the first time.
I am pretty sure that a configuration file, maybe when using a previous version, was stored somewhere. And now this old config file is messing things up.
I have found a sm64.log file at the root directory of my sd card that confirms this. It is created everytime I start the game and specifies which mods are loaded. But this is just a log file.

Tomorrow I will try your custom version of AMS. But I suspect the problem is deep hidden in the emunand, and that this issue can only be solved by using a new one.

Thanks in any case for all your help.
 
Thanks for your help. I tried by deleting the game and its saves again and then cleaning the orphan files by using DBI. It didn't work. But yet again, after reinstalling the game, the previous mod configuration was loaded when starting the game for the first time.
I am pretty sure that a configuration file, maybe when using a previous version, was stored somewhere. And now this old config file is messing things up.
I have found a sm64.log file at the root directory of my sd card that confirms this. It is created everytime I start the game and specifies which mods are loaded. But this is just a log file.

Tomorrow I will try your custom version of AMS. But I suspect the problem is deep hidden in the emunand, and that this issue can only be solved by using a new one.

Thanks in any case for all your help.
If that is the case (the current modifications causing a crash), could we in theory give you a save file that isn't using the default modification settings? When I deleted my save file to test if the game would crash, the game reverted to the ugly "modern" model rather than keep my settings.
 
  • Like
Reactions: alcab
I don't think this would work, because I suspect the settings are not associated to the game "standard" save file, but to a different file that is stored somewhere else. That is the only explanation I can give to the fact that, even when deleting the save file, the whole game or even cleaning the orphaned files by using DBI, when reinstalling the game it boots with the old mod settings being applied.

And I think that what is causing the crash when accessing the mod menu is this -possibly outdated or corrupted- file that is storing the mod settings.

But I could be completely wrong....
 
Last edited by alcab,
I genuinely don't remember how I got it to work. I tried the exef_patch, I tried your files, I had to re-install AMS 1.8.0 because yours wouldn't boot with CFW 19.0., and after all that it magically worked after getting 1 star.
Tried also downgrading to AMS 1.8.0 and still same result =(
Post automatically merged:

Tried also downgrading to AMS 1.8.0 and still same result =(
After deleting everything with dbi, and anything I could find on the sd card, installing, adding mario-mod and patches it finally worked! I dont know what I did diferent :rofl2:
 
Last edited by Rsomethin,
Try with clean orphan files form dbi AFTER unistalling the game and deleting the savedata (from dbi too).


Or you can test with this custom AMS.
Ok, so I finally tested the game using the custom AMS. It still crashes when trying to access the mod menu.

But thanks a lot for your help!!
 
Ok, so I finally tested the game using the custom AMS. It still crashes when trying to access the mod menu.

But thanks a lot for your help!!
OK... Thanks for reporting.

The custom AMS has the patch coded so maybe you have corrupted files.
 
  • Like
Reactions: alcab
WOW.
I finally found the solution, and it was easier than expected. A very long time ago I installed another SM64 port in my SD card and placed it in the ./switch/sm64 folder. It seems this was causing the crashing problem when accessing the mod menu of the SM64 v8 unofficial port. After reading SM64 v7 unofficial port readme file, I realized that some texture packs could be placed in the .\switch\sm64 folder for that version. Because I installed another port in that folder, it seems this was messing things up with SM64 v8.

So I just renamed this folder and now I can access the mod menu without crashes.

I have been having this issue for a very long time, and by having all these nice conversations with you, I have been able to finally understand what was going on. So thank you all for your help!!!

And sorry for bothering you with this stupid issue!!!
 
Last edited by alcab,
So for the Linux Build (2022 Build), it has Cheats included. I am curious if anyone can create a Coin Magnet Code (Mario attracts Coins to come to him at a certain Distance) for the Switch Build. @nolberto82 , is it possible? Same for other Builds, and the original N64 Release?
Off Topic, but nolberto82, need to see about a Rapid Fire Code for StarFox64 (N64 and 3DS) for Version A (Base N64 has it, but Rev A does not)
 
Any way to get Edizon to work with this game again? It used to work prior to fw19. No matter what, the cheat list shows up on Edizon empty and there's no ID associated with it? I only ask cause the built in Moon Jump is just a high jump
 
Which basically means game over!
For that we need the source code, and unfortunately we don’t have it.
So my trick no longer works under Atmosphere 1.10.0 or Horizon OS 21.0.0!
 
  • Like
Reactions: alcab

Site & Scene News

Popular threads in this forum