Seems more a levels issue to me. Edit: What FFMPEG settings did you do?
Used Bizhawk 2.3 btw.Please test any other VRC games that you are interested in to make sure there are no regressions.
Looks correct in 2.2.2:
Savestate to get to the minigame quickly (just press A):
https://www.dropbox.com/s/a3j2mk32m9cycym/Akumajou%20Special%20-%20Boku%20Dracula-kun.NesHawk.State?dl=0
Lagrange Point (NES)
Similar to Dracula-kun, the bottom of the battle screen shakes constantly.
Megami Tensei II - Digital Devil Story (NES)
In the battle screen, there's a graphic glitch below "AUTO".
SD Keiji - Blader (NES)
This is a strange one. During the intro, there are two characters exchanging dialogue. In neshawk, they look like this:
But in Mesen, they look completely different:
Since I don't have real hardware to test, I'm not sure which one is correct.
Necros no Yousai (PCE)
Game crashes during the intro, making it unplayable.
__________
None of the first 3 bugs exist in Mesen, and Necros no Yousai is playable in mednafen.Alright! Do you have any Virtual Machines to suggest?
Mugen Senshi Valis, for PCE, has been a game unplayable in BizHawk since the release of the PCE core. I just now fixed this game, but I thought I'd write a little bit about what went wrong and why it took so long to fix. As it turns out, this game was running some timed code. It's using a VBlank loop to do a few operations, and using the remainder of frame time to load data from the CD. The VBlank loop counts down, and after a certain number of VBlanks, the last VBlank interrupt turns off VBlanks. The game is expecting the other loading code to not be finished at this point, because at the end of the loading code, it turns VBlanks back on again! BizHawk was loading in data too fast. So the loading code was finished too early, and turned on VBlanks even though they were still on. Once the VBlank loop ended, it turned off VBlanks, but now had no way to turn them back on again! Oops! To fix the problem, I just increased the loading time from CD reads, which seemed likely to be the correct solution. This all probably seems pretty obvious just reading that last paragraph, but getting to that point took many hours of debugging, I'm glad it's finally done!
@Sonia: Doki Doki Panic works fine for me, what version / hash are you using?
As it can be seen, there are 3 save files at Level 1. If you load any of them, then you're stuck in an ocean and can't go anywhere, unless if you reset the game:
It's easily fixable by deleting those files, but is that really the intended behavior? I'm pretty sure the ROM isn't a bad dump as I used the No Intro one and tested it on several emulators. Different emulators gave me different results: Mesen, puNES, Nestopia and BizHawk 2.2.1 all generate the 3 save files, but BizHawk 1.13.1 for some reason doesn't.
The strangeness of this game has been discussed on a couple topics before:
http://forums.no-intro.org/viewtopic.php?f=2&t=1552
https://forums.nesdev.com/viewtopic.php?f=11&t=11045
Now the question is, which would be considered an emulator bug: generating those 3 saves or not generating them?Operating System Windows 10 Home Single Language 64-bit CPU Intel Core i7 7500U @ 2.70GHz 39 °C Kaby Lake-U/Y 14nm Technology RAM 16.0GB Dual-Channel Unknown @ 1064MHz (15-15-15-35) Motherboard Acer Captain_SK (U3E1) 40 °C Graphics Generic PnP Monitor (1920x1080@60Hz) Intel HD Graphics 620 (Acer Incorporated [ALI]) 4095MB NVIDIA GeForce 940MX (Acer Incorporated [ALI]) 37 °C ForceWare version: 376.54 SLI Disabled Storage 931GB Western Digital WDC WD10JPVX-22JC3T0 (SATA) 35 °C Optical Drives No optical disk drives detected Audio Realtek High Definition Audio
"laptop" and "gaming" are like polar opposites though... :p At least give it an SSD. (I see too many laptops every week that are a pain to work with because they have a HDD and not enough RAM to cache stuff.)
Sorry Sonia but it looks like you just got unlucky :( I'll try to find some general optimizations that will at least get you back up to 1x speed in games like Kirby. A NES emulator not being able to hit 1x, even under abnormal conditions, just seems silly, there must be something I can do to get some better performance.
Done.
I tested your build, and did not notice any slow down. Try disabling rewind and see if that helps. Also check CPU and memory usage and make sure they aren't off the charts, although I did that on my end and nothing seems amiss.
Also what OS are you using?
I'm not sure what other variables might be at play here. Can you try a Dev Build from right before I made all the changes and see if it works fine there?
I can't reproduce this so I'm not really sure. If you can zip up the folder you are using exactly as it is and get me a link to it, then maybe I will be able to see what the problem is if it also occurs on my end.
As you can see, palette #23 is incorrect. That's because BizHawk uses the FCEUX.pal from version 2.1.0. As of version 2.2.0, they fixed it, which looks like this:
Could you please update it to the correct one? Because every time a new BizHawk version comes out, I have to do it myself. I stuffed the correct file in the linked .rar, which I named "FCEUX (2.2.0).pal". It's in the same folder as the other NES palettes.@Sonia: I tested build 0.0.0.1830 and the performance matches my local build , which is about 5% slower then 2.2. For comparison SMB runs at ~135 FPS on 2.2 and ~130 on dev build. So, I'm not entirely sure why your performance has suffered that much. Does it affect any other cores or only NESHawk? Did you compile it on your own or did you use the appveyor download?
