AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Bsnes emulator fast forward2/28/2024 ![]() * wanting GL fencing / flushing per-frame * wanting to upscale mode 7 to 3840x2160 widescreen * wanting to run really demanding software filters like snes_ntsc (shaders are at least mostly free) * overclocking all the CPUs by 1000% to reduce slowdown * implementing run-ahead to multiply the system requirements by the run-ahead amount (+3 frames = 300% more demanding) * using rock-bottom hardware like $5 Raspberry Pi Zeroes People keep finding new, innovative ways to make SNES emulation more demanding: ![]() Snes9X -> 800fps (1200fps with frameskip fast forward) Mesen-S -> 240fps īsnes -> 390fps (500fps with frameskip fast forward) The question is, is it possible to make what we do faster without losing accuracy? I have a third SNES emulator (really >_>), and with range-tested IRQs and priority queues, and an opcode-based CPU core, I can match Snes9X's performance (for non-SA1/SFX games at least), but it absolutely does not pass my test_nmi/irq ROMs. If Mesen-S didn't come about, I would have tried to do the same for the accuracy mode of bsnes.Īs it stands, I'd like to invest as much resources as possible into speeding up the faster side of bsnes, but it's proving to be a really difficult struggle here. I was planning to speed up the accuracy portion inside bsnes, but I think that effort might be a bit redundant now ^-^īut yea, I'm hoping to be able to squeeze more performance out of it all eventually I revived bsnes to try and fill the large gap between higan and Snes9X, because I'd pretty much given up on another serious SNES emulator attempt. I am not in any way saying one is more important than the other (if anything, a gaming emulator is way more useful), it's just the kind of emulator I wanted to make is all. With higan, I want to preserve the machine more than play games. I don't want higan to be the fastest accurate emulator, I want it to be the reference implementation people use to validate the hardware. But on the whole, my original estimate seems to be mostly holding up. I think you have more headroom in Mesen-S to get more than 200%, but then there's also a few corner cases you're skipping because they're quite frankly ridiculously costly. I've always said you could get about twice the speed of higan without losing any accuracy if you optimized it to its limits. This is why I've been bugging other emudevs for quite a while now (to no avail :P) to make an accurate SNES emulator. since I end up with fairly slow code even if I do that :p) Most of the time I tend to favor speed over perfectly isolating the code for each piece of hardware (esp. since everything in a console tends to be interconnected, heh. In general though, while I do try to keep my code as clean as I can, I've found that often times abstractions that make the code cleaner unfortunately end up also making it slower, esp.
0 Comments
Read More
Leave a Reply. |