Skip to content
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

megaplay.cpp - correctly set to 'export' region, as these aren't Japanese games, and shouldn't be running in Japanese. #11748

Merged
merged 1 commit into from Nov 17, 2023

Conversation

mamehaze
Copy link
Contributor

No description provided.

…ames, and shouldn't be running in Japanese.
@@ -969,7 +969,8 @@ void mplay_state::init_megaplay()
m_ic36_ram = std::make_unique<uint16_t[]>(0x10000 / 2);
m_ic37_ram = std::make_unique<uint8_t[]>(0x10000);

init_megadrij();
// use Export NTSC init, as MegaPlay was apparently only intended for export markets.
init_megadriv();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The init method name is confusing, it makes me think of PAL MD but under the hood it really initializes to NTSC -> init_genesis?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

while in theory I agree, that is out of scope for this set of changes.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It’d be clearer if they were called jdm_ntsc, export_ntsc, etc. but it should probably be in machine configuration and not an init function anyway.

Copy link
Member

@angelosa angelosa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll refactor later I guess.

@cuavas cuavas merged commit 1c9a2cc into mamedev:master Nov 17, 2023
5 checks passed
@mamehaze
Copy link
Contributor Author

mamehaze commented Nov 17, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants