Posts for Trent_Browning

Experienced Forum User
Joined: 8/18/2015
Posts: 8
Sure, I'm up for it. I'll be in the IRC under TB.
Experienced Forum User
Joined: 8/18/2015
Posts: 8
Alright, so I've tested almost everything supported in the official release of BizHawk. Everything seems to work fine. The few I didn't get to test was the Sega Saturn, the TI-83 and the Atari Lynx. The different N64 plugins all work fine, no problems found there. Process Monitor reported this, when using a vanilla install; After some work, finally managed to delete the files you asked to get rid of. I then ran the prerequisite installer, which went through without a problem. I then get this error. I've tried to restart the computer to see if that fixed it, no luck. This broke both the working and vanilla BizHawk.
Experienced Forum User
Joined: 8/18/2015
Posts: 8
Okay, so here's what has happened so far. Got a fresh install of BizHawk to make things easier. Copied the mupen64plus-audio-bkm.dll file to the base folder. Copied the mupen64plus-input-bkm.dll file to the base folder. Finally the mupen64plus-rsp-hle.dll file to the base folder. Which results in the game loading. It seems to be those three plugins not loading properly for some reason.
Experienced Forum User
Joined: 8/18/2015
Posts: 8
zeromus wrote:
Try pasting all the dlls from the dll directory into the same directory as emuhawk.exe. You may have heard a lot of people suggesting this, but it isn't as effective as they think. Nonetheless, it may work in this case. You're not supposed to have to do that obviously. If that fixes it, maybe we can find out why it fixes it. It's odd though, the video plugin is loaded first. If it couldnt find the plugin dlls, then youd think it would fail on the video plugin first, so I'm not confident. The audio plugin seems to be very lightweight, why would it be the one that fails? It's practically nothing at all. Also try running bizhawk from a directory on your desktop
Alright, some progress! Seems pasting the dll's to the base directory seems to fixed the problem. Quite weird considering that I tried a few other games to see if it was just an issue reading from the dll folder, but they all worked fine. Just the N64 part of BizHawk wasn't cooperating If you want to try to figure out why this is happening, I'll keep an eye on this thread.
Experienced Forum User
Joined: 8/18/2015
Posts: 8
zeromus wrote:
What "plugins" are located in the dll folder? Did you manually put anything there?
Just the basic plugins that came with Bizhawk. Vanilla install.
zeromus wrote:
All your fooling around in the path configuration isn't going to solve anything. But it was helpful in answering another question I have, which directory is your bizhawk based in. There seems to be nothing unusual about that.
Yep, just decided to follow the advice of another user. Plus it's easy to reset if I choose to do so.
zeromus wrote:
Since the other thread was about the same error message, maybe you could try some of my debugging from the other thread:
These are the errors I'm getting, hopefully it helps.
zeromus wrote:
did you run the prerequisite installer?
Yep, I've installed the prerequisite installer already as well.
Experienced Forum User
Joined: 8/18/2015
Posts: 8
Alright, I've tried to manually set the paths as seen in this screenshot. But I'm still having the same problem. As well as changing the paths specifically in the N64 tab. Still no change, I can record these instead of taking a screenshot if it helps you guys?
Experienced Forum User
Joined: 8/18/2015
Posts: 8
Sure, forgot to post it in the original post so here; http://tasvideos.org/forum/viewtopic.php?t=16254
Post subject: N64 load error
Experienced Forum User
Joined: 8/18/2015
Posts: 8
Hey, seem to be having a problem running Bizhawk 1.11.1 on Windows 8.1 (x64). Whenever I try to load an N64 game, it gives me this error. I can confirm that the plugins are located in the dll folder inside of the Bizhawk folder. Despite renaming/redownloading there has been no changes. I have also found another user had a similar problem but never listed how to fix it. If I could get some assistance that would be amazing.