Home Page Forums MAME QMC2 Questions, suggestions or requests topic

One I would like (more behind the scenes). Is that the fevice configs being saved into a device.ini instead of the base qmc2.ini.

Would make live a lot easier when you "have to clean" the config files. or saving it into a /device sub-folder with each driver getting it's own device.ini (psx.ini or a2600.ini) which get's loaded when you select that driver, should speed up the first loading of qmc2 by a few nanoseconds

I like the idea.

It's not simple to change that completely, that is, the device-configurations are in qmc2.ini for good reasons and will stay there, but as I already said earlier I'm planning to add an import/export function for this, which would basically work the same way (the export could be automated whenever you change something, so you don't lose new entries).

Also, the initial loading time has nothing to do with the stored device-configurations but is due to the loading of slot-information. And nanoseconds do not count anyway .

That´s right, to load the slot-information consumed a lot of time.

Not "a lot of time", just about 600 milli-seconds here:


It's basically "mess -listslots" that's run here...

It´s subjective, dependent which hardware performance do you have.

And which OS... but it's something I can't change. I need the information, so when should I load it? I could, however, try to make that a "cached" operation as well, which may still be slow for some people with the "wrong" hardware (esp. disk I/O performance counts in the latter case).

Maybe a good idea will be to choose between 2 basic settings:
Fast for user which have a less performance (Hardware/OS) and Nice for user which have a good performance.
Dependent of the basic setting, QMC2 works with more caching or not as example.
Or some functions are disabled or enabled dependent of the basic setting too.

:p

But I found that disabling ROM state filter makes QMC2 load a lot faster