MSX.emu released for mobile devices

Page 1/2
| 2

By Rakashazi

Rookie (18)

Rakashazi's picture

16-08-2011, 05:16

I've officially released MSX.emu for iOS (on Cydia) and Android (on the Market). The WebOS port is coming soon and I'll post the source once it properly compiles for all three platforms. Remember to download the machine profiles from my site (or use your own from BlueMSX) before running. Feel free to leave any feedback, questions, bug reports, etc. here :)

Login or register to post comments

By Manuel

Ascended (18162)

Manuel's picture

16-08-2011, 20:09

Congratulations, it looks really good Smile

By Vampier

Prophet (2385)

Vampier's picture

16-08-2011, 20:16

No ROMs are included with this app and must be supplied by the user. Transfer games anywhere to your SD card and browse to them from within the app (default SD card directory is /mnt/sdcard). Enable the Direct Texture option if supported by your device to increase performance.

Why not include cbios so that at least you can boot game roms.

http://cbios.sourceforge.net/ I'm sure you'll be content with the license

By jasonvieira

Rookie (23)

jasonvieira's picture

16-08-2011, 21:06

Rakashazi Big smile U can't imagine how happy I am for using this app. It works perfectly and everytime I'm able to use MSX in several different platforms, I feel it keeps the system from dyinhg. I bought, I tried, I approve. Smile

By Rakashazi

Rookie (18)

Rakashazi's picture

17-08-2011, 05:56

Thanks for the comments. I would like to eventually bundle C-BIOS so ROM carts work without additional setup, just need to work out some platform-specific packaging issues so the app can install the needed files on its own.

By Rakashazi

Rookie (18)

Rakashazi's picture

22-09-2011, 04:53

The next version (1.4.4) will bundle C-BIOS and prompt you to install if the app starts up without an MSX.emu directory present. You can then manually add other BlueMSX machines as usual. I also fixed a potential crash when loading an incomplete save state (i.e. one that's missing dependent machine files or rom/disk media). It should now cleanly close the existing game instead of leaving it in an undefined state.

By Rakashazi

Rookie (18)

Rakashazi's picture

28-10-2011, 13:36

Sorry for the delay with the WebOS port. I've just submitted it for approval in the App Catalog so it should be up in the near future. There were some mysterious IO errors I had to work around (bugs in WebOS apparently), but it's running properly now Smile

I'm going to focus on MSX-specific features for the next few updates and am open to user requests. Currently, I'm starting to hook up the hard drive controller code to allow inserting disk drive images.

Also, I hope to get a Linux version released at some point to use as an alternative to the command line SDL one.

By luppie

Paladin (863)

luppie's picture

16-11-2011, 00:25

Sorry for crossposting, but this topic looks like a better place for my questions LOL!

Running MSX.emu now on my Galaxy Tab 10.1 en it looks great. Only thing I cant get working is the keyboard dock.
I used the key config form MSX.emu to bind all keyboard keys to the MSX.emu keys, but it looks only the shift & return are mapped, all other keys dont work (the mapping in the config screen does work, so the keys are mapped)

upload.luppie.net/uploaded/IMAG0404.jpg
upload.luppie.net/uploaded/SC20111115-144606.jpg

Anyone an idea what is going wrong with key mapping ?

Also I'm missing an option to start the emu without a gamerom inside, so that I just can boot a msx and start in Basic. (Right now i'm doing it by loading a MSX2.rom, but I suppose that's not the way to do it)

By luppie

Paladin (863)

luppie's picture

16-11-2011, 01:30

Found the solution, in this case it's a Samsung issue.
If I use the Samsung keyboard config I have the problem mentioned above.
If I use the Android keyboard config, the keyboard works with MSX.emu.

Finaly I can play with my Tab as it was a real MSX Big smile

By Rakashazi

Rookie (18)

Rakashazi's picture

20-11-2011, 05:17

Found the solution, in this case it's a Samsung issue.
If I use the Samsung keyboard config I have the problem mentioned above.
If I use the Android keyboard config, the keyboard works with MSX.emu.

I've heard of this problem from some other users and it's caused by the keys sending a combined push & release message to the app so there's no way to track if a key is really held down or not. I don't have a Bluetooth/Docked keyboard myself but most users said they fixed the issue by switching their IME in the Android settings like you did. The slide-out keyboard on my Droid/Milestone isn't affected and reports the key messages correctly, so only specific devices need this fix.

By cax

Prophet (3736)

cax's picture

20-11-2011, 08:47

I've found the auto-detection code works quite well on the games I've tested. I'm sure there are a few that might have issues but so far I haven't received any reports of serious compatibility problems. I'll also be adding a slimmed down ROM DB implementation in a future update.

Indeed, there is a number of improperly detected non-Konami megaroms.
Great to hear you are going to add the ROM DB implementation to fix this issue.

Page 1/2
| 2