Lens of Truth in Ocarina of Time?

2stick

@quicksilver Changed that, and now I'm getting what looks to be a texture loading screen before the ROM launches (even if I choose the non high res Glide plugin). It never actually loads the ROM, as whatever is going on hangs around 715mb. So it does look like changing that compatibility check does allow Glide to launch. I'll have to do some digging to see why this texture stuff is happening though.

Thanks a lot for all the help and advice.

quicksilver

@2stick that message about noise textures loading is normal when using mupen64-glide

quicksilver

@2stick There must be some other compatibility settings that enable OOT to run correctly. Disabling the the compatibility check must be causing an issue with those other settings.

I just checked and it looks like a recent change put OOT on the glide blacklist. If you want to remove it without disabling the compatibility check you can do so here:

/opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh

Looks like its on line 217. Try removing zelda from that line and try to run using glide again.

2stick

@quicksilver For whatever reason, mine is hanging. Before I went to bed last night I tried to load the ROM with Glide again, and it hung up around 700MB. It's still actually working, as every few minutes it'll show a fraction of a MB of progress. But I guess the CPU is so bogged down by whatever it's trying to do, because I can't even SSH into the Pi.

I left it loading the textures and let it run overnight. This morning when I checked it, it was back in Emulationstation so I thought it worked. However I tried to load the ROM again and the texture load hung up at 720MB.

alt text

If I can't figure it out tonight after work I'll just create a new post since we're not really talking about the Lens of Truth anymore lol.

quicksilver

@2stick Yea thats not normal. Are you overclocked? Try removing mupen64 and then reinstalling from binary.

2stick

@quicksilver I am overclocked. Don't know my settings off hand, but it's nothing crazy and it was 100% stable over a few different tests back when I originally did it a year or so ago.

I'll try removing/reinstalling mupen64 later today.

quicksilver

@2stick Over time emulators can become more demanding which may expose an unstable overclock. Its possible your stability testing wasnt as thorough as you thought (how did you test for stability?). Or it could be something completely unrelated but its worth investigating. Before you change your settings can you post the contents of your config.txt?

2stick

@quicksilver I tested it with Stress and cpuburn.

https://core-electronics.com.au/tutorials/stress-testing-your-raspberry-pi.html

A part of me thinks that I only actually have the GPU overclocked, but I may be thinking of a different board. When I get home I'll check my config and post it here to be sure.

quicksilver

@2stick yea CPU burn really only tests your cooling and power supply. The stress program I have found to be inadequate at determining stability. I can pass it at 1400ghz but my pi really isn't stable past 1350mhz. This is because it is only stressing your CPU. You really want to test using something that will thrash your CPU, GPU, and ram all at the same time. I have another thread with a good conversation going about overclocking and proper stability testing.

Again, I have no clue if this is the cause of your current issue. But it's worth investigating because bad overclocks can do all sorts of wierd things.

Jonathansharp

@2stick Did you happen to have the instructions for converting the save file? We're having the same issue with the Lens of Truth.