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

casio/pv1000.cpp: Toggle BUSREQ like hardware does #12623

Merged
merged 1 commit into from
Aug 9, 2024

Conversation

lidnariq
Copy link
Contributor

This slows down games to realistic speeds.

Please let me know if there's a better way to do any of this.

{
int hpos = m_screen->hpos();
int vpos = m_screen->vpos();
hpos += 32; // adjust from screen coordinates to something that's easier to math
Copy link
Member

Choose a reason for hiding this comment

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

MAME historically starting at origin 0,0 is just for a generic stub convenience.
This kind of math is unnecessary if you acknowledge overscan origins in screen_update and set_raw setups.

Copy link
Contributor

Choose a reason for hiding this comment

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

To further clarify, if you do set_raw with the real hcount/vcount values you also have to change where you draw in screen_update to coincide with the specified visible area. I get why MAME does that, but it really does violate the principle of least surprise.

…ames to realistic speeds

try adjusting geometry to simplify busreq timing
@lidnariq
Copy link
Contributor Author

lidnariq commented Aug 7, 2024

Is this acceptable now?

@rb6502 rb6502 merged commit dbb097e into mamedev:master Aug 9, 2024
5 checks passed
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.

3 participants