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

s16b: ddux Dynamite Dux color changes #279

Closed
jotego opened this issue Jun 26, 2023 · 3 comments
Closed

s16b: ddux Dynamite Dux color changes #279

jotego opened this issue Jun 26, 2023 · 3 comments
Assignees
Labels
core bug Something isn't working
Milestone

Comments

@jotego
Copy link
Owner

jotego commented Jun 26, 2023

After finishing level 1, the duck color changes. Originally fixed in the old JTS16 repository (see issue here). This was related to the DTACK signal generation.

Someone mentioned it on Patreon after the Pocket beta release of JTS16B. Not clear whether he was using an old MiSTer version.

@florgana check whether this happens on the current version in SiDi. If the problem happens, the duck color changes when he is travelling through the warp at the end of level 1. The weird colors will stay on level 2.

This was originally fixed by modifying the generation of the DTACK signal for the M68000. Touching the DTACK generation is dodgy because it affects games in different ways. It isn't clear why games are so sensitive to it.

@jotego jotego added the question Further information is requested label Jun 26, 2023
@jotego jotego added this to the s16b milestone Jun 26, 2023
@florgana
Copy link
Contributor

In the JTFRAME commit 1bf46f5a the duck changes colors.

An attempt has been made to increment the value to the WD parameter in jtframe_68kdtak.v and it continues to happen.

The processor speed was changed to 12 MHz and it works, the wait2 and wait3 values were also changed to 0 and it works, in both cases (independent) the duck stops changing color.

@jotego jotego added core bug Something isn't working and removed question Further information is requested labels Jun 30, 2023
@jotego
Copy link
Owner Author

jotego commented Jul 1, 2023

  • Moving the 16kB of main CPU RAM to BRAM does not fix it
  • 16kB of RAM moved to BRAM and SDRAM operated at 96MHz does not fix it
  • at 10MHz, keeping wait2/wait3 at 0 does not fix it (contrary to the proposition above)

@jotego jotego self-assigned this Jul 6, 2023
@jotego
Copy link
Owner Author

jotego commented Jul 6, 2023

The DTACKN signal was generated one cpu_cen too late:

Bug
imagen

Fixed
imagen

This was related to the ugly line in Ryukyu occuring later compared to MAME in #299.

Fixed in 3a72437

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

2 participants