Jump to content
  • 0

Pause menu problems


Lishy
 Share

Question

Hey guys. As many of you know, pause menu in OoT debug is INCREDIBLY messy, as it takes an incredibly long time to load. Is there any way to fix this? Any patches as of yet?

 

Additionally, PJ64 1.7 crashes when it gets the so called "graphic error" notification you sometimes get when pausing while using Jabo's graphics plugin. How does I fix this? It is annoying to constantly savestate in fear of it crashing. Hell, sometimes I even get Blue Screens...

Link to comment
Share on other sites

Recommended Posts

  • 0

I have NEVER experienced a pause crash with Rice 6.1.3 DX9 build. Glide64 crashes sometimes, but only if I use high res textures. Keep in mind that it does have a very long pause regardless of the video plugin (at least for me). To my knowledge, there was a GS code that "fixed" the long delay but it never worked for me. Just for the record I am a PJ64 1.6 user.

Link to comment
Share on other sites

  • 0

Using PJ64 1.7 and going to graphic settings ingame caused a "system_service_exception" Blue Screen of Death :D

 

I'll try 1964 then. Do you mean the emulator or video plugin? Because I'm really attached to PJ64. Dunno why I never use to have these problems in the past, or if I just got lucky, but I'd love if I knew of a fix..

 

edit: In 1964 debug rom is a blank screen. These are my ROM settings:

 

Posted Image

Link to comment
Share on other sites

  • 0

This is not specific to 1964, but it is all i could dig up at work:

 

CPU core style: Re compiler

Self-mod code method: Check Memory Advance

Default Memory size: 8MB This one is important.

Advanced block lining: On

 

-Then go to the ROM settings tab and do your settings like this:

CPU core style: Re compiler (if this doesn't work the first time switch it to "Protect Memory")

Self-modifying code method: Check Memory Advance

Memory Size: 8MB

Advanced block linking: Default

Default save type: Use first used save type

Counter Factor: 2

 

-Then remove all checks at the bottom of the tab except for "Register Caching" That's the only one you should have checked.

Apply these settings

Link to comment
Share on other sites

  • 0

Not to be rude, but some of these are verbatim from what I posted so it appears you didn't even try. That being said... if I had to guess here is what you didn't change/changed incorrectly:

Expansion Pack should be 8MB (This one is important)

Self Modifying code: Check mem advance

Core: Not sure if this can be changed to just Recompiler, but check

Link to comment
Share on other sites

  • 0

The problem you are describing is caused by is actually by the programmers being "clever".

 

What takes awful long to load is the background image for the inventory screen. It gives some pluggins/emulators problems. Even on a real N64 it loads slow sometimes!

 

MM's Inventory loads fast! Why? It lacks that stupid background image.

 

This problem was solved once, but the fix was hoarded, and since lost. But if it was fixed once, it can be fixed again. Any of you mighty ASM wizards what to take a stab at it? I'm willing to help.

Link to comment
Share on other sites

  • 0

I quoted myself from glitchkill:

  Quote

Your BEST choice for an emulator would be Nemu64.

 

If you want pre-configured Nemu64... CLICK ME

If you want another guide on setting up for the Debug ROM... CLICK ME

 

And if you insist on using 1964, I guess I'll give you the correct settings since I can't seem to find them anywhere. I set the emulator up myself after awhile of tweaking and messing around so these may not be the best settings but, hey, they work.

 

First, make sure you have these plugins:

Posted Image

 

Go to Video Settings:

Posted Image

 

Set it up like this:

Posted Image

 

Next, go to ROM Properties:

Posted Image

 

Set it up like this:

Posted Image

 

And (hopefully) success:

Posted Image

Link to comment
Share on other sites

  • 0

Thank you Jason!

 

However there is still the issue of the dirt roads in hyrule field disappearing. Any way to fix this?

 

edit: This is weird. Why does it work with graphics plugin of jabo 1.6, but not 1.5.2? In 1.5.2 it is just a blank screen! I used the exact settings as your rom settings image.

 

And even in 1.6, the spear moblins freeze the game!

 

I really wish I knew the secret to getting this to work..

Link to comment
Share on other sites

  • 0

Try the jabo 1.6 fix, created cooliscool.

 

1. open the ROM in a hex editor

2. In the header there should be the ROM name, something like "LEGEND OF ZELDA".

3. In typo over mode, typing over the original text and not adding bytes to the ROM, rename it to anything else. The classic fix was used "LEGEND OF DEBUG"

This fix is so crucial, I have it applied to default ROM.

Link to comment
Share on other sites

  • 0

Nemu64 is a black screen (but it still "plays")

 

I'm using the 2003 version.

 

I wish I had a way to simply just play it without all these errors. Sure these are your configurations? :D

 

edit: Additionally, pj64 configured with 1964 still doesn't have dirt roads, and level select is garbled!

 

Me and Naxy tried to do all sorts of crap but nothing is seeming to work so far! He told me to post logs because something is REALLY messed up and we need xdaniel or spinout's help.

 

 

  Reveal hidden contents

 

Link to comment
Share on other sites

  • 0

So the Debug ROM won't run correctly for you or crash no matter what? Okay, from the start... First, your Mobile Intel video chipset might be problematic in general. Second, get the recently released PJ64 v1.6.1 plugins and try those with PJ64 v1.6, making sure the ROM settings are correct - those here work right for me. Third, if it still doesn't work right, try Nemu64 with said PJ64 v1.6.1 video plugin and make sure the Expansion Pak is enabled. Fourth, I have no idea.

Link to comment
Share on other sites

  • 0

If v1.6.1 also does it, it's probably your video chipset's fault. Especially integrated/mobile chipsets by Intel are infamous for glitches like that - they have gotten better, but are still way behind ex. a Mobility Radeon HD. Your best bet is probably messing around with some other, older plugins (ex. glN64, Rice Video 6.x), although it's still not guaranteed that one of them will work right.

Link to comment
Share on other sites

  • 0

I believe you. This is a shitty laptop :D

 

However, I went to Intel's site and scanned for driver updates, and it did not detect any needed updates. This is odd since before I reformatted my laptop I had to update it manually, but now i don't know what to install to update it. Anyone happen to know what to do with this crappy "Mobile Intel® 4 series express chipset family"?

Link to comment
Share on other sites

  • 0

Just tried using your Nemu download.

 

Error loading library 'Direct64 v0.5.03.25.dll'

 

Execution blahblahblah not use plugin.

 

Err... Halp? I can still load up my rom and stuff but so far it aint even show New Game name letters. And still no roads on hyrule field!

 

On the bottom right of the emu is also some flickering thing. (Pause is certainly faster though, but it aint fix these other glitches.)

 

Using the exact settings you included, unless the direct64 error loading did something?

 

 

edit: Says it's using Rice's Video Plugin 6.1.1 beta 10? Is that correct? O_o

Link to comment
Share on other sites

  • 0

Remove the direct64 dll if you don't want that error. I threw about 15 GFX plugins into that emulator package. I really don't care about the paths in hyrule field, though you can configure the GFX plugin as it suits you and I'm sure you can get it working. The flickering thing is due to Rice video being designed and tested on PJ64 and 1964 but Nemu 64 still has the same standard (Zimlar's spec iirc) for gfx plugins.

 

Nemu's sound emulation is also better than all emulators, LaC spent tons of time making it work as near as he could get it to work as an N64.

Link to comment
Share on other sites

 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.