We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Windows 10
DOSBox-X v0.83.23
I've been testing the "amastrad" machine mode lately and came across glitches in some games. Here are some screenshots
https://i.imgur.com/PlMfI2C.png
https://i.ibb.co/1J5gXWL/Top3.png
In the first screenshot the borders around the title card show the staring screen. I'm told the borders should be black.
In the second screenshot, the OCEAN logo from the previous config screen is visible. There's also a glitch around the lower part of the crosshair.
The patch for the exclusive Amstrad PC1512 graphic mode is old, but I thought it was definitive. It seems to nee more testing.
Just load the games using the "machine=amstrad" option.
machine=amstrad
None
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Code of Conduct & Contributing Guidelines
Have you checked that no other similar bug report(s) already exists?
What operating system(s) this bug have occurred on?
Windows 10
What version(s) of DOSBox-X have this bug?
DOSBox-X v0.83.23
Describe the bug
I've been testing the "amastrad" machine mode lately and came across glitches in some games. Here are some screenshots
https://i.imgur.com/PlMfI2C.png
https://i.ibb.co/1J5gXWL/Top3.png
In the first screenshot the borders around the title card show the staring screen. I'm told the borders should be black.
In the second screenshot, the OCEAN logo from the previous config screen is visible. There's also a glitch around the lower part of the crosshair.
Expected behavior
The patch for the exclusive Amstrad PC1512 graphic mode is old, but I thought it was definitive. It seems to nee more testing.
Steps to reproduce the behaviour
Just load the games using the "machine=amstrad" option.
Used configuration
machine=amstrad
Emulator log
Additional context
None
The text was updated successfully, but these errors were encountered: