I don't know how to use a GUI-less emu.
Besides, I tested it on those emus because I believe they are less accurate than Bizhawk. So if they load there, and not on Bizhawk, then I can assume it's a Bizhawk bug.
No you can't. It might be a mednafen bug. there's mednafen frontends. I won't pay attention to psx emulation bug reports unless theyve been checked on mednafen.
Uh...
So, I found something wrong with both cores of GBA for BizHawk 1.11.3 and 1.11.4
Steps:
1. Start Monster House,GBA
2. Open this ram watch
Domain EWRAM
SystemID GBA
00F9D8 d 3 0 EWRAM
00F9DC d 3 0 EWRAM
02E3EC d u 0 EWRAM
02E534 d u 0 EWRAM
02E78C d u 0 EWRAM
02E790 d u 0 EWRAM
02FF04 d u 0 EWRAM
02F49C d u 0 EWRAM Basement 1
02F4C4 d u 0 EWRAM Basement 1
02F740 d u 0 EWRAM Basement 1
02FD88 d u 0 EWRAM Basement 1
02FDE8 d u 0 EWRAM Basement 1
02FF48 d u 0 EWRAM Basement 1
02E1E8 d u 0 EWRAM Floor 1
02E354 d u 0 EWRAM Floor 1
02E454 d u 0 EWRAM Floor 1
02E4BC d u 0 EWRAM Floor 1
02E4F8 d u 0 EWRAM Floor 1
02E560 d u 0 EWRAM Floor 1
02E5D8 d u 0 EWRAM Floor 1
02E630 d u 0 EWRAM Floor 1
02EC30 d u 0 EWRAM Floor 1
02EF20 d u 0 EWRAM Floor 1
02EF5C d u 0 EWRAM Floor 1
02F050 d u 0 EWRAM Floor 1
02F120 d u 0 EWRAM Floor 1
02BFB8 d u 0 EWRAM Floor 2
02E2C4 d u 0 EWRAM Floor 2
02E580 d u 0 EWRAM Floor 2
3. Find out which value corresponds to the correct one.
4. Right click and select "View in Hex Editor"
5. Slightly before it should display a value saying "B841B944" or something similar. Zero it out.
6. Move around a bit
Now depending on the core, the following will happen:
VBA next: Emulator crashes
MGBA: Game crashes, and savestates become "glitched"; loading other savestates won't fix the crash.
Here's a video of the "savestates error"
https://youtu.be/g04PqDbmDPU
Also, completely unrelated, but sometimes the change counter in the RAM watch advances even if I paused emulation.
An unhandled exception of type 'SlimDX.Direct3D9.Direct3DX9NotFoundException' occurred in SlimDX.dll
Additional information: Direct3DX 9 was not found. Please install the latest DirectX end-user redistributable package from Microsoft.
This is the error I got when running BizHawk past 1.11.0 on Windows 10. Some people say Win10 Bizhawk works.
When not running it through VS2015, you dont receive any errors or warnings.
Windows 10 bizhawk certainly does work. make sure D3DX9_43.dll got installed, or at least look at what D3DX9_*.dll you can find, and use dependency walker to make sure they can get loaded without errors
An unhandled exception of type 'SlimDX.Direct3D9.Direct3DX9NotFoundException' occurred in SlimDX.dll
Additional information: Direct3DX 9 was not found. Please install the latest DirectX end-user redistributable package from Microsoft.
This is the error I got when running BizHawk past 1.11.0 on Windows 10. Some people say Win10 Bizhawk works.
When not running it through VS2015, you dont receive any errors or warnings.
Did you follow the instructructions displayed? Or just assume that Windows 10 comes with DirectX and you shouldn't need to update it?
Afaik Microsoft has never included a full copy of DirectX with a copy of Windows, there's always a lot of optional stuff and backwards compatibility stuff that they leave out. DirectX is also periodically updated and I don't think I've ever seen the updates be offered via Windows Update except that one time when Vista was updated to support DirectX 11.
An unhandled exception of type 'SlimDX.Direct3D9.Direct3DX9NotFoundException' occurred in SlimDX.dll
Additional information: Direct3DX 9 was not found. Please install the latest DirectX end-user redistributable package from Microsoft.
This is the error I got when running BizHawk past 1.11.0 on Windows 10. Some people say Win10 Bizhawk works.
When not running it through VS2015, you dont receive any errors or warnings.
Did you follow the instructructions displayed? Or just assume that Windows 10 comes with DirectX and you shouldn't need to update it?
Afaik Microsoft has never included a full copy of DirectX with a copy of Windows, there's always a lot of optional stuff and backwards compatibility stuff that they leave out. DirectX is also periodically updated and I don't think I've ever seen the updates be offered via Windows Update except that one time when Vista was updated to support DirectX 11.
I did try Directx SDK with redistributed packages and all other options selected. I tried looking for directx9 and kept getting redirected to the upgrade to windows 10 page, didnt think to look for d3dx9_43.dll, I will check out Dependency Walker when I get home. Not a big issue for me though so don't mind me.
I'm getting some freezing/hanging when I play Perfect Dark on the latest Bizhawk version. It freezes at so many random points of time, I can't really know what the problem could be. I've tested all the video and audio plugins and the same problem occurs no matter which one I use. Could someone test out Perfect Dark for me just to make sure it's not a bad install or something?
Hi, new here.
Bug:
When I playback a Super Smash Bros. 64 movie I recorded, and open up the Virtual Pad for input viewing, sometimes it doesn't correctly play back the right inputs. For example, I'll do a diagonal up, diagonal down, for several frames, and it'll playback as if:
#1) My input wasn't as far on the x/y axis as I actually did in the recording
#2) Sometimes it just plays it back as a straight cardinal direction (e.g. east), when I actually did like southeast.
Also, as an n64 TASer, I'd like to request that the emulator somehow utilize live input viewing just like the TAS input plugin v0.8 on the mupen64-rr emulator. Not sure if this is possible, but it would be greatly appreciated.
Great emulator overall though. Much better than Mupen which always desynced upon playback for me.
Check the inputlog in your movie and see if the values are what youre expecting. I find it very unlikely that the virtual pad is mis-representing what's in the movie. It's more likely you don't understand what's making it through bizhawk's joystick input and into the movie. If you're able to verify that theres an actual discrepancy between whats in the movie and what the virtualpad displays, then thats very interesting.
virtualpad isn't going to support live input viewing any time soon, it just isn't built to do that. Some people have some kind of live input viewing with OBS, maybe theres some plugin that makes that easy.
bad installs dont make games freeze once they start running. bad roms or cheats might, or buggy gpus, if its bizhawk freezing and not just the game
I tested various other games including Smash 64, Super Mario 64, and Goldeneye, all work fine without freezing. Both revisions of Perfect Dark freeze at random points, sometimes right at the beginning screen, and sometimes in the middle of a multiplayer match. Weird thing is, Bizhawk doesn't crash, it just keeps running at a constant frame rate once it freezes. It's very unpredictable, and it happens with any video plugin, I tried disabling the sound but that didn't help either. I tried all three graphics options, OpenGL, DirectX, and GDI+, all act the same, so it might be something completely different going on.
thats not weird at all, it just sounds like an n64 emulation bug. check mupen64plus which we're based on if you get tired of waiting for someone else to find the exact same thing you did in bizhawk
Check the inputlog in your movie and see if the values are what youre expecting. I find it very unlikely that the virtual pad is mis-representing what's in the movie. It's more likely you don't understand what's making it through bizhawk's joystick input and into the movie. If you're able to verify that theres an actual discrepancy between whats in the movie and what the virtualpad displays, then thats very interesting.
virtualpad isn't going to support live input viewing any time soon, it just isn't built to do that. Some people have some kind of live input viewing with OBS, maybe theres some plugin that makes that easy.
Yes I checked the input log. The input log (text label over game) is correct, but on the virtual pad, the visual stick directions are wrong. For example, the text will say "89, -89", but the virtual pad only says "89, 0" and so doesn't show the stick in the right position.
Note: I recently discovered the only problem it has is the Y coordinate on the FIRST PLAYER's pad, which stays at 0, even though it's like -60 to 80 or w/e on the INPUT LOG. Player 2 is fine for some reason, lol.
I do remember one time though it completely skipped inputs on certain frames which was really weird. Try alternating diagonal topleft/right and bottom left/right inputs at each frame, then try to play back the movie with the virtual pad open.
Just figured out. If tortoisegit shows wrong icons for files, like exclamation marks that get stuck for clean files, go to tortoisegit settings, change Icon Overlays - Status cache option, save, and then restore it.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
mercenariez, do you know the difference between the fake analog buttons and the analog axes? "P1 A Up" for example is a button which sets the analog stick to the upmost extent. We record those separately. If those were in the inputlog and conflicting with simultaneous analog input, I don't know what will happen.
I'm not sure if this is intended, but using 2+ lua scripts that read different memory domains seems to have the latest script overwrite the "memory.usememorydomain" to the last one.
Example: I drag a script that uses "WRAM". Then I drag another script that uses "System Bus". Both scripts now use System bus instead of WRAM/System Bus separately.
the concept of multiple lua scripts in bizhawk is not fully baked. don't assume anything is intended, and try not to put the system under too much stress.
Use memory domain parameter for memory reading/writing functions... until what you need is working.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
client.bufferwidth() and client.bufferheight() return 0 if the emulator is minimized.
That was the reason my script keeps crashing for seemingly no reason: I was dividing by zero!
