![]() ![]() So, if you have 100%, it means that you are using your processor completely. I find it more interesting an emulator that respects the cycles of instructions and thought everyone was using a Windows or Linux task manager to analyze CPU usage. (but this is the case of all the consoles, I don't know who would emulate the hardware perfectly). ![]() When I do something exotic with the material, I test on a real SNES That's just one of many we rely on the hardware, no emulator is perfect on this point. For example: "my stuff runs on bsnes v1.07 64-bit correctly, but with bsnes-plus 073.3a 64-bit requires you use bsnes-accuracy.exe". I also can't stress enough including a README or manual/documentation outlining emulators (and their versions/builds, including CPU architecture used) which may not work correctly. It's kind of a back-and-forth relationship though: usually today you start with developing things using emulators (because they make the development process easier), you then later test on hardware + get things working there properly, *then* go back to make sure emulator compatibility is as good as you can get it. Ensure your stuff works on hardware - preferably on actual cartridge (read: not SD2SNES, EverDrive, etc.) - and if it does then that's good, from there start to try and work out what quirks need to be added to be compatible with emulators. It matters!īut to answer the question in the summary line: there is no "best emulator". standard this applies to older versions). GPU matters too.įurthermore, with bsnes, you didn't disclose what version, nor did you disclose what profile (accuracy vs. If for CPU you're talking about actual CPU usage on the system running the emulator, then you've chosen to omit system specs as well. helloworld: 99.8% (varies wildly sometimes 900%!) That being said if your aiming for compatibility with the highest number of emulators make sure it works in snes9x 1.43 I think as that's what ports tend to be based on off. If you ask me Higan is probably the best. Snes9x is probably fine for what your doing but hardly what I would consider as the best emulator. If you want to emulate the snes keyboard you need to use no$sns. You can't play sattellaview roms you need the fork of bsnes that luigiblood works on. This also ignores any attempt to do exotic things, you can't control memory maps for custom roms in snes9x without editing the source, some romhacks only work in snes9x after being developed and working in other emulators first. Higan also has more accurate vblank timing from my experience. Higan was the only emulator to replicate that behavior correctly. One example from my experience is that you can't read joypad inputs right after a vblank but bsnes debugger and snes9x where working fine despite inputs being ignored on hardware. What about higan, as you said snes9x is easy and probably what most of your user base will end up using, but I'll still defend not using it over more accurate emulators for development especially interfacing with hardware because it's easy to make mistakes that will work on snes9x but then not work later on hardware. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |