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

Incorrect 8088 (4,77 MHz) emulation speed in games #705

Closed
usergithub64 opened this issue Apr 19, 2020 · 7 comments
Closed

Incorrect 8088 (4,77 MHz) emulation speed in games #705

usergithub64 opened this issue Apr 19, 2020 · 7 comments
Labels
Milestone

Comments

@usergithub64
Copy link
Contributor

usergithub64 commented Apr 19, 2020

20200420-044345-184
In games such as Arkanoid, Buck Rogers (Planet of Zoom), Eden Blues, Flightmare, and others, there is an incorrect processor emulation speed of 8088 (4,77 MHz). This is especially noticeable in the game Arkanoid by the speed of music playback in the initial splash screen of the game. To understand how this music should sound (if there is no real PC 8088 (4,77 MHz), in DOSBox ECE or in DOSBox-X you need to set cycles = 240 and run this game.
Here's how the music should sound. (both on a real machine 8088 XT 4.77 MHz and in DOSBox with cycles = 240)
https://youtu.be/_7mouV05qy0

I draw your attention to the fact that the Paratrooper (1982) game in 86Box at 8088 (4,77 MHz) now works correctly! You can hear PC Speaker sounds of flying helicopters and airplanes.

@fuel-pcbox
Copy link

DOSBox is heavily inaccurate compared to 86box when it comes to 8088 timings, so of course there are going to be differences. :P

@OBattler
Copy link
Member

There are some problems remaning with 808x timings, mostly related to DMA refresh cycles for which currently, a crude approximation is used. Eventually they are going to be made more accurate.

@OBattler
Copy link
Member

I'm going to look into this.

@OBattler
Copy link
Member

I confirm this and I suspect some 808x instruction (I believe that commit did change a few) is now misbehaving, causing this.

@OBattler
Copy link
Member

I just committed a fix for this, it was the DAA instruction that accidentally broke.

@ghost
Copy link

ghost commented Nov 4, 2020

What do you mean?
bause

@OBattler
Copy link
Member

Closing this as it's being tracked in #4044.

@OBattler OBattler closed this as not planned Won't fix, can't repro, duplicate, stale Jan 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants