-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
s18: bad graphics #686
Comments
Enemies are not visible in ddcrew. It might be related to the tile map. |
Some VDP priority issues are still exists
Here there are more inputs than sa, sb and fix from the tilemap chip: Just for record, the logic: |
Do you have an idea what are the Tilemap0-4 lines on the tilemap chip? |
I am not sure. The arcade GFX chipset seems to be a redesign of the System 16B chipset with slightly different IO. The original chipset seemed to identify which tilemap layer was active. The priority of that layer may have been available too. The file s16b/doc/s16b.txt has a good and short description of the layer priorities around line 1086. Because S16B video comes already mixed, S18 cannot do much when merging the VDP video. Particularly, you cannot have sprites hide each other depending on the y position. That's why the sprites used on the VDP look flat in Alien Storm, so as to make this limitation less noticeable. MAME identifies some scenes and priority values but they ignore the real connections on the board. I have been trying to make sense of the decoding signals in the PAL (315-5373) but I could only be sure of what I wrote in the colmix case statement. |
That probably need more time then, various priority values are used in every game (5 in D.D.Crew for example). Also 4 (Moonwalker) seems not perfect, as the to-be-rescued kids are look like ghosts sometimes. |
Shouldn't this VDP-S16 priority thing belong to a different issue? |
That's fine. Let's limit this one to fix the garbled graphics. Layer priority will be handled on a different one. |
I opened #701 |
Some VDP priority issues are still exists
Some VDP priority issues are still exists
FixedClitch Hitter seems ready to go. Thank you. ddcrewThis is the image that should appear right after booting up ddcrew. The tilemap bank is pointing to a different place, producing a completely different scene. wwallyjThe tile bank is wrong in several scenes, including the title |
ddcrew also a priority issue (the image you should see comes from the VDP). What's currently seen is the background with the policeman - it's good. Write 4,5: instead of just 4: for the case to the VDP priority mixing, you'll see. wwally - probably wwally should be wwallyj in the TOML file. But even with this change, there are still issues probably due to unhandled VDP priority level. Also wally needs trackball control. |
@jotego i have a version of laser ghost which is modded and uses joystick controls and im sure it bypasses the calibration screen. I also have a wally modded rom which uses joystick controls aswell. Theres also Clockwork Aquario. |
It looks like these ROM sets have not been documented. It would be good to report it to the MAME team so they set a name for the files and a CRC check sum for preservation. |
ddcrew seems fine in 8533440 after the priority edits done for mwalk. |
For me, it looks like desertbr also good. And wwally, too, but I have a problem adding trackball controls. The trackball input is using an upd4701. As there's jt4701, it seemed straightforward. Unfortunately dial_x and dial_y (which jt4701 accepts) don't correspond to mouse x and y, but only mouse x. Is it feasible to add the vertical mouse movement as dial_y emulation to jtframe_dial? |
Another issue that the game seems to need reversed dials, but
doesn't do anything, MRA has still:
|
But the later one is not really important, it's easy to reverse the dial signals. |
It looks like this issue is completed and the rest of the gfx problems are priority-layer related, and addresses in #701. Closing this one. |
These games have bad GFX. The tile bank seems wrong (a8cad67).
The text was updated successfully, but these errors were encountered: