-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSX 1 and 2 Emulation #1288
Comments
Maybe eventually. But probably not for another 6-12 months at the very least. |
No worries. Good Luck. |
I've been wondering about that for a while as well. MSX would certainly do a great addition as a core. When the time comes, maybe port either openMSX or blueMSX over? Since they're both open source projects with high compatibility. |
We have all the components to get a MSX core up and running . It’s just a matter of stitching all the infrastructure stuff together. This would be a good way for someone to learn how BizHawk works while developing something new at the same time , but so far no one has been quite interested enough to do it . |
Its on my list of things todo if/when I finish CPCHawk. By then (as you say) we already have the components in other cores to reuse (for MSX 1 and 2 anyway, the TurboR (and on the 2+ optionally) has an additional YM2413 sound chip that we would need to emulate from scratch I think). |
edit 2023-03-10: Moved this table here from the external page I had it in before. I updated all the data at the same time.
† licensed like CC BY-NC-SA Dis/honourable mentions: BRMSX, NLMSX, NO$MSX, RedMSX, RuMSX duplicate of #319 |
There is now a functional MSX 1 core in BizHawk. It only run cartridge games for now. It can be upgraded to disk games and MSX 2 with some work, Probably a stretch to add 2+ or Super R. in the long run not sure whether its better to work on the in house core or port something over, probably depends on interest level. |
I want to request a MSX emulation because is good.
It will be possible?
All the No-Intro Sets less the newest Nintendo generation because it's too big for now deserves a good place.
Thank you.
The text was updated successfully, but these errors were encountered: