Alyosha, I downloaded the latest BizHawk developer build to test the new Z80 stuff, then went ahead and also tested NEShawk's new performance. I chose 3 basic games for it, then compared with BizHawk 2.2's performance. This is what I got: SMB: 63 fps (Dev Build) | 105 fps (2.2) Rockman 2: 60 fps | 97 fps Kirby's Adventure: 58 fps | 93 fps (CPU: Intel Core i5 3330 @ 3.00 GHz) Is this huge performance hit because now NEShawk runs in single PPU ticks?
@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?
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.Could you please update it to the correct one?
Completely unrelated, but just in case you didn't see this thread already: http://forums.nesdev.com/viewtopic.php?f=3&t=16507 It's a FDS test rom that validates the IRQ's behavior - Bizhawk currently fails a number of the tests (which causes Kaettekita Mario Bros to crash). Should be pretty simple to fix though.
Although Kattekita Mario Bros wasn't crashing for me previously, where was it crashing for you? Maybe I have a different version? Also thanks for the valuable R&D on this Sour!
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?
The problematic build
I also had him check with process explorer and it was the main thread eating up all the CPU.
Previous Build:
Problematic Build
If you want, I can check with him to see if that old build still causes issues on his machine and if does, I can have him run the build that's causing Sonia trouble to see if it occurs. Might help track the issue down?If you want, I can check with him to see if that old build still causes issues on his machine and if does, I can have him run the build that's causing Sonia trouble to see if it occurs. Might help track the issue down?
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?
Can you give me a link? I only see the latest build in that appveyor page.
My results: https://imgur.com/a/7vpxE 64-bit Windows 7 Ultimate, Service Pack 1
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.
