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

Glitches: Top Gear 3000 (EU & USA) Color glitch #74

Open
tmagri opened this issue Mar 13, 2018 · 19 comments
Open

Glitches: Top Gear 3000 (EU & USA) Color glitch #74

tmagri opened this issue Mar 13, 2018 · 19 comments

Comments

@tmagri
Copy link

tmagri commented Mar 13, 2018

Expected behaviour and actual behaviour

Within the race, instead of the colour for the outlier of font and border colour, being black, goes green. (For the first race this occurs when computer Player 2 arrives @ 3/4 on Lap 1 (21 to 22 seconds in roughly)).
image

After race completion (sometimes, not frequently), background colour instead of being black the colour goes blue.
image

Steps to reproduce the problem

Once the game is loaded:
1. CHAMPIONSHIP
2. 1 PLAYER SPLIT
3. RACE
4. Press A to exit TRACK DESCRIPTION (Issue 2, Blue, doesn't happen here)
5. Go down to EXIT
6. Race as per usual or stay idle. Either way, when computer Player 2 arrives @ 3/4 on Lap 1 (21 to 22 seconds in roughly), the black outlier of font, and border changes from black to green.
7. Once the race is complete, and continue pressing A until TRACK DESCRIPTION is shown, it may (or may not) have a blue background instead of black (continue more races until issue occurs).

ROM name and hash value

Unable to test ROM dump due to not having facilities to dump the cartridge.
I am unsure of the similarity between what roms that currently available like Top Gear 3000 (EUR).sfc* compared to Australia cartridge (although cartridge ID contains EUR)

Since Cartridge contains DSP-4 Enhancement, the Jailbreak cannot run the ROM.

From testing Top Gear 3000 (EUR).sfc* on Higan (RetroArch Accuracy), with using dsp4.rom, issues do not occur:

*MD5: 46‌2e‌15‌c0‌18‌c6‌53‌33‌5b‌a6‌34‌d3‌c1‌cd‌06‌c9
SHA1: 777D8732023A300A2C566F2D48BC354E0AA1DA7E

Untested on SD2SNES due to not having the device, this would be a good comparison to observe.

firmware version and SD card model

  • Jailbreak firmware version(s): all, including latest snt_firmware_verJB6.5, and the official 4.4
  • relevant Super Nt settings
    • Hardware: PAL (50Hz)
    • Resolution set at 1080p50Hz (the issue also occurs at 60Hz, outside of scope)
    • Any shader configuration (My preference: No Shader)
    • Any Screen size (My preference: 8x7)
    • Any Buffer mode (My preference: Zero Delay)
  • Cartridge ID: SNSP-A3TP-EUR
  • Phone Shots / Cartridge Scans
    image
    image
    image
    image
    image
@frederic-mahe frederic-mahe added the bug Something isn't working label Mar 13, 2018
@frederic-mahe
Copy link
Collaborator

@tmagri excellent bug report, thanks! If you can, could you please check whether or not the bug occurs on a genuine Super Nintendo?

@SmokeMonsterPacks SmokeMonsterPacks changed the title Glitches: Top Gear 3000 (PAL, Australia) - (Minor issue) Incorrect colour @ 1 player split screen & after race completion (Track Description screen, random) Glitches: Top Gear 3000 (EU) Incorrect colours Mar 13, 2018
@SmokeMonsterPacks
Copy link
Owner

SmokeMonsterPacks commented Mar 13, 2018

There was only one PAL region release, so your EU ROM is good for others testing via SD2SNES. Could someone please also test an NTSC copy so we can narrow down whether the bug is specific to PAL only?

I just tested TG3K on my Retro Duo Portable via SD2SNES and didn't see the glitch. RDP is not a perfect proxy of real hardware, but I would agree that this could be a SNT bug.

My ROM: Top Gear 3000 (Europe).sfc - 46‌2e‌15‌c0‌18‌c6‌53‌33‌5b‌a6‌34‌d3‌c1‌cd‌06‌c9 (matches issue)

@SmokeMonsterPacks
Copy link
Owner

SmokeMonsterPacks commented Mar 13, 2018

RaspberryAlpine on Discord just verified both glitches in the EU ROM via SD2SNES
Settings: 1080p60, PAL

RaspberryAlpine also found that both glitches also appear in the NTSC ROM via SD2SNES
Settings: 1080p60 NTSC

He also tested the NTSC ROM on a real SNESjr via SD2SNES and neither glitch happened, so this is a new confirmed SNT bug.

@SmokeMonsterPacks SmokeMonsterPacks changed the title Glitches: Top Gear 3000 (EU) Incorrect colours Glitches: Top Gear 3000 (EU & USA) Color glitch Mar 13, 2018
@tmagri
Copy link
Author

tmagri commented Mar 14, 2018

@frederic-mahe Hi, Just to check (although confirmed), the issues are not present on the SNES PAL console.
20180314_155715
20180314_160115
20180314_160449
20180314_160554
20180314_160625
20180314_161021

@SmokeMonsterPacks
Copy link
Owner

Kev has a fix for Top Gear 3000, but it won't be in the next official firmware update. He wants to release it in a future release to isolate if its fix causes any new issues.

@Chronokeys
Copy link

Hey, guess the fix hasn't been implemented yet, just wanted to confirm that this still happens on the latest JB with a real NTSC cart, both the blue background screen and the green border during races.

@teknomedic
Copy link

Similar bug happens using FXPak Pro with Space being blue when on planet/track selection screen. Also after several races the text reporting your winnings is garbled (Think in area 3 when it first appeared) . Perhaps this is a special chip problem.

@teknomedic
Copy link

teknomedic commented Sep 1, 2020

Update: For those that care. The green border glitch and the blue space background glitches are still happening on the FXPak Pro. Having re-tested on the Super NT (latest jailbreak) with no cart and using the latest firmware on last revision of the SD2SNES (regular) this no longer happens; however, using the SD2SNES Pro / FXPak Pro the split screen green border and blue screen glitches happen again. This is using a NTSC/USA ROM from No intro's 2020 updated packages. Also keep in mind that for all three tests all I've done is move my SD card between the 3 devices with no changes. If I can ever remember where I put my Original SNES I'll test the SD2SNES and FXPak Pro carts on that and update.

@tjanas
Copy link
Collaborator

tjanas commented May 29, 2021

@tmagri does this bug still exist with JB v7.0?

@teknomedic
Copy link

teknomedic commented May 29, 2021 via email

@tjanas
Copy link
Collaborator

tjanas commented May 4, 2023

@teknomedic @Chronokeys can you please re-test your cartridges with the latest official firmware? https://www.analogue.co/support/super-nt/firmware/5.1

@tjanas tjanas added needs verification Extra attention is needed and removed confirmed labels May 4, 2023
@tmagri
Copy link
Author

tmagri commented May 6, 2023

@tjanas : I had booted up and updated the firmware of the Super NT, with the Top Gear 3000 game.
Issue still persists.
image
image

@tjanas tjanas added confirmed and removed needs verification Extra attention is needed labels May 8, 2023
@tjanas tjanas pinned this issue May 8, 2023
@tjanas
Copy link
Collaborator

tjanas commented May 9, 2023

This is an outstanding issue with MiSTerFPGA too.

@tjanas
Copy link
Collaborator

tjanas commented May 9, 2023

Per kevtris regarding this game issue: "they do an insane amount of DMAs and it can get DMA-bound. when that happens it can then corrupt the palette"

@BarbieOnWeed
Copy link

Wasn't all known issues fixed in the new firmware?
It say so on the site.

@tjanas
Copy link
Collaborator

tjanas commented Jul 11, 2023

@BarbieOnWeed more issues are fixed in JB v7.2, especially those that are JB-specific.

@BarbieOnWeed
Copy link

BarbieOnWeed commented Jul 11, 2023

I have tested the game from SD on JB v7.2 and it seems fixed! :)

Edit: on SD2SNES both pal and ntsc copy still have the issue, but it works on the MSU1 version.

@tjanas
Copy link
Collaborator

tjanas commented Jul 12, 2023

I have also found that the green border issue is absent when running from SD card but present when running from an sd2snes, with JB v7.2.

@Chronokeys
Copy link

Issue still present when running the real ntsc cart, got the blue screen after the first race…bummer…

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants