Well you read my mind there, a module system would not increase bin size.PH3NOM wrote:As far as rom recognition, I don't see any problems.Neoblast wrote:Great, but wouldn't it be better ( and obviously more diff and take more time ) to use the emulator core ( and not load the emu bin ) to load the rom directly from dcmc?
Two cons of this are the rom recognision, either using a different file extension for each rom type would work or maybe the header, but I get the feeling it would be a mess when loading bins.
True, the build of DCMC you tested determines how to process a file based on its extension.
It would be easy to change this to actually open the file first, read its header, then decide how to process it.
Simply, there has been no need to do so, until now...
Adding the EMU CORE into DCMC is a good idea.
But, as Quzar mentioned, this would inflate the binary size, that is something I dont want to do.
DCMC ( including romdisk ) is currently ~2.5Mb
If I had enough time, which I dont, I would implement a module system, similar to how Dreamshell functions.
Considering my time constraints, it is a realistic goal to simply go about this the way I originally mentioned.
DCMC is shaping out to be one of the essentials, hope you manage to find enough time to complete it man.
And not only snes4all, there are still a few emus on the work ( emuforge ones, gens4all on its current build looks great and there's some steps that are being done that would increase the speed a lot ).
Once again, if you need some external help in testing let me know
Also the audio discussion of this thread should be split, my comprehension of all the audio system has increased a lot.