-
Notifications
You must be signed in to change notification settings - Fork 368
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
(Konami Mystic Warriors Hardware) transition effects missing #1754
Comments
The konami pre-gx hw emulation is not pcb-perfect at all, we can make little hacks here 'n there to improve certain things, but, to fix every single issue with this hw is really an excersize in futility. At this point, the best bet is to buy a pcb if you want perfection. On the other hand, pcb's need a lot of care & repair to keep going, so maybe the imperfect emulation isn't so bad after all? :) best regards,
|
This is partially a duplicate of #1714 |
Curious how hamster fixed the bugs in terms of Aca, thanks for looking into it either way :) |
Well, in best case scenarios, i suppose commercial emulators have a dedicated team working on this and/or full hardware documentation and/or full access to pcbs for retroengineering. |
im curious why some transition effects dont work, but some do for example the end of the intro for Mystic Warriors FinalBurn.Neo.v1.0.0.03.Mystic.Warriors.ver.EAA.2024-04-18.19-48-26.mp4 |
Hi, |
I see, i mean that’s why bug testers are here haha, not trying to be rude btw |
Games that ran on the same hardware as mystic warriors for example gaiapolis, violent storm, etc seems to be missing transitions effects either between scenes, or starting a stage, as far as i know this doesn’t happen on original hardware, also seems that violent storm’s graphics might seem too bright(?) in terms of graphics. https://youtu.be/0hEZvGd4whM?feature=shared
as you see on real hardware, the colors look less bright than on emulation. Then again it’s hard to tell if it’s something to do with the capture method or what. Sorry for the long post btw.
The text was updated successfully, but these errors were encountered: