You shouldn't have disabled rendering to texture. Rendering to texture does not slow down your game and basic frame buffer runs at about 30 FPS at the beginning of the game but then speeds back up again once you get to the File Select menu.
When having both activated, I get slowdown at least in these cases:
- Using a transformation mask
- Invisible tektikes turning
- Intro
- Lens of Truth
- Goron curl-up in snow (also happens with both disabled, though)
- probably some other things
which is the majority of the game. And I want speed more than quality, really. (apart from not seeing the advantages of having framebuffer and Render-To-Texture enabled)
Disable Big Textures is needed so you can see the gameplay in the Majora's Mask battle room. If this option is not on, you cannot see anything but a black screen in that part of the game.
I'm pretty sure this is related to motion blur, as this room works fine for me when Render-To-Texture is disabled/hidden (haven't tried with it on, though)
I told you to go with the options I suggested to you, not to go against my recommendations just because they seem pointless.
I just wanted to know what it's for, because an option such as this is likely to cause some side-effects.
Accurate/Fine Texture Mapping is not required to see the Map subscreen, and if it is on, the Map subscreen image will be glitchy as well as other graphics in the game.
I'm not talking about the Map Subscreen (which doesn't glitch here), I'm talking about the Map Select, a developer tool hidden in the game that can be activated with hex editing or gameshark codes. It can be really handy for testing glitches, emulator problems, and such.
Really, though, you shouldn't be using Rice's Video Plugin to emulate this game. Either you use Glide64 or you use Direct64. Just because using Rice's Video Plugin reduces plugin-changing in between running different games is no reason to use Rice's Video Plugin all of the time. In fact, I switch my plugins 20 times a day, as every day I am testing several games and trying to find out which emulators and plugins and configurations work best. It isn't that hard to change plugins in between games; should be quick to get over with.
I know that switching plugins should be done for some games, and can be useful at times, just this one has so minor bugs that I don't care about it.
If it's really that hard to put up with, use 1964 or Mupen64 to assign certain plugins to certain games. Both of those emulators should work just fine with the Zelda and Mario games.
I know these emulators and sometimes use them, I prefer the Project64 interface though.
If Glide64 does not work, that means your video card has a problem with it, judging by the errors you reported. You probably have some Microsoft-manufactured video card. You may need to reinstall your video card drivers from your video card brand's site. For example, I used to have NVidia GeForce (Microsoft Corporation). To get rid of that Microsoft part to get Glide64 working, I had to go to nvidia.com and reinstall their latest drivers.
I'm sure I downloaded the latest drivers when I got this computer. But while I'm thinking about it, there are probably newer drivers I can download. It just takes a while to disable the NVIDIA background processes...
And I'm pretty sure the Glide64 thing is not a global issue, as other games used to work fine, and here emulation stops when the title screen should pop up, which, as we all know, uses motion blur.
If you are still having trouble getting Glide64 to work, give it a rest, use Direct64 instead.
I haven't tried Direct64 yet, but I may give it a shot.