Go Back   Project64 Forums > Public Version > Project 64 - v1.6

 
 
Thread Tools Display Modes
  #1  
Old 14th November 2015, 08:04 PM
Tv.Johnny Tv.Johnny is offline
Junior Member
 
Join Date: Nov 2015
Posts: 5
Default Zelda OOT Crash at windmill after song of storm

Does anyone think they can save my game save file and then save it to after the cutscene is done? i really want to continue from my save point but the rom crashes..
Attached Files
File Type: zip zelda oot crash.zip (1.59 MB, 2 views)

Last edited by Tv.Johnny; 14th November 2015 at 08:05 PM. Reason: Forgot my save file
  #2  
Old 15th November 2015, 02:38 AM
Marcelo_20xx's Avatar
Marcelo_20xx Marcelo_20xx is offline
Senior Member
 
Join Date: Oct 2013
Posts: 165
Default

No need to do that, under the Recompiler options uncheck any selfmod code and just check "protect memory", also you must switch to 2.2 or latest PJ64 either from the Github or from EmuCR as the 1.6 suffers from two fatal flaws:

There is only 2 options to play this game in Project64 1.6 (I don't count playing the game on interpreter mode as an option, if you have enough CPU raw power be my guest) and both has cons:
a) Use "Check memory advance" cons:you will get random crashes here and there and specific crashes (one is the problem you are describing, a hang after playing the Song of Storms and draining the well at night, I bet this doesnt happen if you play the song at daytime)...
b) Use "protect memory" cons: The game will not crash under most circumstances but you will suffer from an annoying vertical stutter every 5 seconds or so which is very unpleasant to the eye and brain...

Finally PJ64 2.X and above has some regressions in their core which renders OoT unplayable as you will get known crashes, search in one of my other post for the detailed info...

The solution? Sadly play the game on the hard to find Mupen64Plus 1.5 for windows (last version where you can use the PJ64 compatible plugins, because the emu dev chose to depart from the zilmar spec crippling his emu badly)...

As the time of writing this post I am testing with this emu playing a complete run, that is play the entire game in one session, so if I find a crash I will edit this post, hopefully I already tested with my saves the troublesome spots where there are known crashes...

Last edited by Marcelo_20xx; 15th November 2015 at 02:40 AM.
  #3  
Old 15th November 2015, 07:44 PM
Tv.Johnny Tv.Johnny is offline
Junior Member
 
Join Date: Nov 2015
Posts: 5
Default still get crashes

i tried p64 2.2 and couldnt find muphen 1.5. could you restore my game save? i think it would be easier.
  #4  
Old 15th November 2015, 08:51 PM
Marcelo_20xx's Avatar
Marcelo_20xx Marcelo_20xx is offline
Senior Member
 
Join Date: Oct 2013
Posts: 165
Default

But you will get random crashes, that's the point, also did you tried my suggestion? play the song at daytime?...
  #5  
Old 15th November 2015, 09:50 PM
Frank74's Avatar
Frank74 Frank74 is offline
Alpha Tester
Project Supporter
Senior Member
 
Join Date: Aug 2013
Location: UK
Posts: 828
Default

Found mupen64plus 1.5 for windows.
http://cid-ec92aae47a89073b.skydrive...aspx/Emulation
Browse to mupen64plus folder.
  #6  
Old 15th November 2015, 11:06 PM
RPGMaster's Avatar
RPGMaster RPGMaster is offline
Alpha Tester
Project Supporter
Super Moderator
 
Join Date: Dec 2013
Posts: 2,010
Default

Quote:
Originally Posted by Marcelo_20xx View Post
Finally PJ64 2.X and above has some regressions in their core which renders OoT unplayable as you will get known crashes, search in one of my other post for the detailed info...
Send me a savestate please ! So that I can debug it, and possibly fix it.

Quote:
Originally Posted by Marcelo_20xx View Post
The solution? Sadly play the game on the hard to find Mupen64Plus 1.5 for windows (last version where you can use the PJ64 compatible plugins, because the emu dev chose to depart from the zilmar spec crippling his emu badly)...
I don't think Mupen64Plus 1.5 is a good solution. It doesn't even have a frame limiter, or VI/s display. Why not use 1964 instead?
  #7  
Old 16th November 2015, 05:04 AM
Marcelo_20xx's Avatar
Marcelo_20xx Marcelo_20xx is offline
Senior Member
 
Join Date: Oct 2013
Posts: 165
Default

Sorry RPGMaster it turns out that I had disabled Advanced Block Linking, I read somewhere that sometimes this option is needed (the weirdest part of all is that the Kokiri Shop crash (happens on 1.2 roms only) still exist while using interpreter, why ABL fix this on Recompiler mode? I dont know), now that two crashes I reported are fixed, so what is the downside of using ABL on latest PJ64? is still there the minifreeze like in PJ64 1.6 for using it? because that's why I disable it in the first place...

Last edited by Marcelo_20xx; 16th November 2015 at 05:07 AM.
  #8  
Old 16th November 2015, 10:37 PM
RPGMaster's Avatar
RPGMaster RPGMaster is offline
Alpha Tester
Project Supporter
Super Moderator
 
Join Date: Dec 2013
Posts: 2,010
Default

Quote:
Originally Posted by Marcelo_20xx View Post
Sorry RPGMaster it turns out that I had disabled Advanced Block Linking, I read somewhere that sometimes this option is needed (the weirdest part of all is that the Kokiri Shop crash (happens on 1.2 roms only) still exist while using interpreter, why ABL fix this on Recompiler mode? I dont know), now that two crashes I reported are fixed, so what is the downside of using ABL on latest PJ64? is still there the minifreeze like in PJ64 1.6 for using it? because that's why I disable it in the first place...
That is very interesting! Usually, ABL is more bug prone, hence why some games are bugged with it enabled, like Vigilante 8. I'll have to check out that Kokiri Shop crash.

Unfortunately, ABL still can cause stuttering. Basically there's a trade off. ABL makes the executable code more efficient, at the cost of taking longer to recompile the code.
  #9  
Old 16th November 2015, 11:01 PM
Marcelo_20xx's Avatar
Marcelo_20xx Marcelo_20xx is offline
Senior Member
 
Join Date: Oct 2013
Posts: 165
Default

Yep, there is that mini-stuttering you mentioned, not an option for me as my eyes gets distracted from it...

I remember that was the reason I disable it and the emulator as you said, ran smoothly, no random pauses or mini freezes, I tested this on a Zelda complete play through (mind you 6 to 7 hours) without a single hitch on its performance. The 1.1 (U) version was the closest to get to the end without issues and with ABL disabled. I was preparing to celebrate when out of nowhere the game hanged at the last battle with Ganon, the cinematic when he resurrects and transform into a Giant Monster Pig, sorry for the spoilers but by this time I think this is no secret anymore...

ABL fix this but at a cost, Mupen64Plus 1.5 seems to be the best option for me, at least for this only game, I tested it all the way to the cutscene where child Link pulls the Master Sword and the emu went smoothly, no stuttering of any kind and the audio without problems too (thanks to Shunyuan's audio as the default audio plugin that came with the distro does suffer from a lot of stuttering because it wasn't that polished like it is now)...

Last edited by Marcelo_20xx; 16th November 2015 at 11:04 PM.
  #10  
Old 18th November 2015, 10:40 PM
Tv.Johnny Tv.Johnny is offline
Junior Member
 
Join Date: Nov 2015
Posts: 5
Default Zelda oot crash

Can anyone fix my game save file and then return it back to me on here lol... The game save state is on my first post up as an attachment. I saved it right when the screen went black and the song repeatedly plays and all you here is the water draining sound... I really wanna continue here I left off. I don't know shit about emus or how to fix anything which is why I left it up to someone here to save me hehe. Thanks
 

Tags
zelda ocarina of time

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT. The time now is 07:38 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.