|
Post by samphex on Jan 27, 2008 4:50:02 GMT 1
Can you guys combine MAME and LJP or is that not possible?
|
|
|
Post by Tinnus on Jan 27, 2008 11:58:34 GMT 1
I don't think that makes much sense since there's so much difference between the two. The objectives are different, both of them are already big projects, and are still being developed.
(I suppose you've checked out PalmMAME by Vilmos)
|
|
|
Post by vilmos on Jan 27, 2008 16:15:49 GMT 1
Well since PalmMAME also has MESS (which is computer and console emulators) it is really the other way around, PalmMAME could add LJP.
Although I agree there isn't much point. PalmMAME and PalmMESS are HUGE. Combining them for no real reason would be someone's project for 6 months and I can't see anyone willing to take that on.
|
|
|
Post by samphex on Jan 27, 2008 16:41:08 GMT 1
Ha, I see your point, although I think it would be much easier to install one program to play both, I see it will just create a burden on someone for no point other than aving time in installing programs. ha.
|
|
|
Post by tgwaste on Jan 28, 2008 5:22:49 GMT 1
afaik mame is for atari right? wont ljx have atari emulators like ljp did? although I think ljp's atari had some issues?
|
|
|
Post by Tinnus on Jan 28, 2008 15:09:12 GMT 1
MAME's a Multi Arcada Machine Emulator. I tjust emulates a ton of different arcade machines
|
|
|
Post by vilmos on Jan 28, 2008 15:11:43 GMT 1
PalmMAME emulates about 1200 arcade machines, and far more than just Atari machines.
MESS can amulate a ton of consoles and computer systems which is more what LJP does.
|
|
|
Post by _Em on Jan 28, 2008 18:10:14 GMT 1
...and there you have it from the developers themselves Something to note: MESS is designed from a documentation standpoint, not a performance standpoint. This means you can go into the source code and figure out how all the pieces of hardware fit together quite easily, but getting decent performance out of any of the compiled emulators is not high priority. LJP tends to try for performance; LJX should be somewhere in the middle (using portable code but sacrificing code readability for performance).
|
|