Posts for PrinceWatercress

Experienced Forum User
Joined: 5/4/2018
Posts: 18
YoshiRulz wrote:
This might be because EmuHawk sees that you've pushed the Win key but doesn't see that you've released it, so it only looks for hotkeys with Win in them. I believe the Win key was removed from the modifier keys list after 2.8; could you try a dev build?
Just tried the latest one (bdcd3721). Hotkeys work perfectly, as does Alt + Enter for full screen, while recording with Windows 10 game bar. It's just 2.8 itself that's not letting me do it.
Experienced Forum User
Joined: 5/4/2018
Posts: 18
GJTASer2018 wrote:
Have you opened an issue about this on the BizHawk GitHub yet? You might get a faster response than posting here...
I could, but I don't have a GitHub login.
Experienced Forum User
Joined: 5/4/2018
Posts: 18
Unlike previous versions of Bizhawk that I've used, whenever I record with Windows Game Bar (Windows Key + G, for those wondering), I cannot use the hotkeys or get out of full screen mode unless I exit Bizhawk altogether. Hotkeys and keyboard shortcuts work fine, but once I start recording with Windows Game Bar, they just stop working and stay un-functional unless I exit Bizhawk 2.8 and re-enter it altogether, forcing me to use earlier versions. Really hoping this gets fixed.
Post subject: Re: The Terminator (SMS) won't show backgrounds
Experienced Forum User
Joined: 5/4/2018
Posts: 18
Alyosha wrote:
PrinceWatercress wrote:
So I've tried to play The Terminator on the newest version of Bizhawk (2.6.1), and the game won't show backgrounds at all. Apparently this has been a thing for what seems like numerous version of Bizhawk; even 2.5.2 seems to do this. All you really get are your sprite as well as those of the enemies. Backgrounds are just completely black as if they don't even exist. https://twitter.com/PrinceWatercres/status/1364264787194957828 EDIT: Changed the link so you could actually see the screenshot.
I'm pretty sure the game gear version of this same game was fixed a while back by adding SRAM to it. I can't test it right now myself, but if you go into gamedb->gamedb_sega_sms and replace this line:
F224907676A09C7F0404C95C316F1503		The Terminator (E)	SMS			Europe
with this:
F224907676A09C7F0404C95C316F1503		The Terminator (E)	SMS		SRAM=8192	Europe
(or equivalently for the brazil version if you are using that one.) I'm guessing it will probably work. Let me know if so and I can commit it to master.
I just tried this and it works. It gave me the SMB1 ? Block and the "Warning: Unknown ROM" status in the lower-left corner of the window, but it did the trick. Thanks!
Post subject: The Terminator (SMS) won't show backgrounds
Experienced Forum User
Joined: 5/4/2018
Posts: 18
So I've tried to play The Terminator on the newest version of Bizhawk (2.6.1), and the game won't show backgrounds at all. Apparently this has been a thing for what seems like numerous version of Bizhawk; even 2.5.2 seems to do this. All you really get are your sprite as well as those of the enemies. Backgrounds are just completely black as if they don't even exist. https://twitter.com/PrinceWatercres/status/1364264787194957828 EDIT: Changed the link so you could actually see the screenshot.
Experienced Forum User
Joined: 5/4/2018
Posts: 18
endrift wrote:
Fixed upstream, fix will be in 0.7.3 when that comes out.
Thank you!
Experienced Forum User
Joined: 5/4/2018
Posts: 18
feos wrote:
Please try on standalone mGBA (not bizhawk core).
Just did that after seeing your message. I got the exact same results. EDIT: Used mGBA 0.7.2; the bug/glitch is still there.
Post subject: Glitch for Secret Agent Barbie: Royal Jewels Mission (GBA)
Experienced Forum User
Joined: 5/4/2018
Posts: 18
Found this glitch on Bizhawk 2.3.2, though it may be on earlier versions. Would like to see if anyone else can get this to happen. EDIT: I did this with the American (U) version. Not sure it will work on the European (E) version, though it wouldn't surprise me if it did. 1. Play on the mGBA core. (This is important.) 2. Start a new game. 3. Play the first level and get all six Secret File discs to get an unlockable. 4. When asked if you want to enter the Secret Vault to see what you unlocked, select "Yes." 5. Screen will fade to white and stay there; sound will stutter on the frame that the game locked up on. You'll have to reset, load state or power off/on to get out of that. If you select "No," the game continues as normal. If you play on the VBA-Next core, this doesn't happen.
Experienced Forum User
Joined: 5/4/2018
Posts: 18
EZGames69 wrote:
It's probably worth mentioning that if you dump GBHawk movies, enabling alt sync will make the audio output in the dump to be fixed.
Ah, yes...the issue from the recent Mega Man II GB TAS. I remember catching the comment on the re-upload.
Experienced Forum User
Joined: 5/4/2018
Posts: 18
Alyosha wrote:
I'm quite bad at hearing audio issues, but generally speaking GBhawk audio will sound slightly worse then Gambatte (i.e. version 2.2.2) since GBHawk always ends frames on VBL boundaries, which is good for me since it makes logging and debugging stuff easy, but slightly worse for users since the main thing this impacts is audio fidelity.
Well, that's interesting. Also, I checked again to see what core I was using when the sound pitch issues occurred in Bizhawk 2.3. It was Gambatte, not GBHawk. Subject line has been changed accordingly.
Post subject: Is it me, or is the music on Gambatte a bit off-pitch?
Experienced Forum User
Joined: 5/4/2018
Posts: 18
Just started playing Link's Awakening DX on Bizhawk 2.3. For some reason, whenever a song plays, it is off-pitch for the first few seconds. I thought it was just me, but when I played it on Bizhawk 2.2.2, it was absolutely fine and I didn't have an issue. Anyone else notice this, or am I the only one? EDIT: For those wondering how off-pitch it sounds, the pitch is a tad lower for the first few seconds. That's pretty much it. EDIT 2: It's Gambatte, not GBHawk. Didn't look at the core I was using before making this post. Changing subject line accordingly.
Experienced Forum User
Joined: 5/4/2018
Posts: 18
Alyosha wrote:
http://z80.info/interrup.htm This page says that SP = AF = 0xFFFF at reset. Implementing this does indeed make the game work. So I guess I can remove that hack afterall, problem solved!
Great! Thanks!
Experienced Forum User
Joined: 5/4/2018
Posts: 18
Alyosha wrote:
Ok, I was wrong about that. The game does set the 'ROM write enable' flag, but the root cause of the problem is that it doesn't set the stack pointer before starting to execute code. A 'CALL' instruction then overwrites the ROM bank. This happens since I initialize the stack pointer to zero, then it gets decremented to 0xFFFF (ROM bank register.) I tried looking for documentation about where the stack pointer gets intiialized to, but I don't see it actually specified anywehere. 0x0 and 0xFFFF both crash the game, so it can't be those. It's possible that's it's just some unspecified value. If this were the case, this game would function by pure chance on real hardware. The game does need to be able to return to the proper address after the call, so the stack pointer does have to be in writable memory. This is very strange. My guess is that during development, they didn't realize the mistake they made since they left the ROM write anbel flag set, meaning the stack pointer could start anywhere and still be in writable memory on their dev boards, thus masking the problem. Or it really is initialized to something internally and I just can't find what. The documentation does specify that the only register actually set is PC (to zero) so who knows what actually happens. Anyway, I added a game specific hack to make the game run by putting the stack pointer in RAM initially. I don't particularly like it, but it does work now.
So it's the game doing this, and not the emulator? Well, this is interesting... Edit: Forgot it was the game the whole time. Whoops.
Experienced Forum User
Joined: 5/4/2018
Posts: 18
Alyosha wrote:
So this game is turning on the ‘ROM write enable’ flag and then doing some antics with rom writes. Will take more time then I thought to sort out.
Yikes! No wonder it wasn't working. Good luck with getting that fixed. Once again, thank you.
Experienced Forum User
Joined: 5/4/2018
Posts: 18
Alyosha wrote:
PrinceWatercress wrote:
Alyosha wrote:
I'll look into it.
Thanks. Will you need the SHA1 and MD5 from the dump status report for the specific ROM I used, by any chance?
Shouldn't be necessary, I just haven't gotten around to it yet, maybe in a few days.
Alright. Let me know if you do. Thank you.
Experienced Forum User
Joined: 5/4/2018
Posts: 18
Alyosha wrote:
I'll look into it.
Thanks. Will you need the SHA1 and MD5 from the dump status report for the specific ROM I used, by any chance?
Post subject: Aerial Assault (W) for Game Gear will not load
Experienced Forum User
Joined: 5/4/2018
Posts: 18
For some reason, the other two Game Gear games that I have on my computer work just fine. It's just that Aerial Assault (W) won't load. Don't know if anybody else has this problem. As soon as I load it, I get nothing. No sound, no Sega screen at the beginning...nothing. Nothing happens. And I'm getting the checkmark in the lower-left corner, so I know it's a good dump. Anybody else able to recreate this? EDIT: Oddly enough, Aerial Assault (J) (Rev 1) works perfectly okay.
Post subject: Possible bug/glitch on G-LOC: Air Battle (Genesis/MD)?
Experienced Forum User
Joined: 5/4/2018
Posts: 18
It seems that every time I fire a missile in the game, the game wants to temporarily speed up (and sometimes do it for even an even longer, indeterminable amount of time). I've tested this on both Bizhawk 2.0 and 2.2.2 and getting the same results. Not sure if it's my ROM or the emulator, but I thought I would bring it up here. What's funny is that Bizhawk says that the ROM is a verified good dump, but loading it in the newest version of Kega Fusion give me a "WARNING: Checksum error" message, so that probably has something to do with it. Anybody able to recreate this bug/glitch? EDIT: For some reason, when I closed the emulator, it seems to have fixed the issue. Weird...