search

flyinghead / flycast

Flycast is a multiplatform Sega Dreamcast, Naomi, Naomi 2 and Atomiswave emulator
GNU General Public License v2.0
1.29k stars 161 forks source link

Fighting Vipers 2 (J) gets Fighting Force 2 box art in game list #1467

Closed smbhax closed 3 months ago

smbhax commented 3 months ago

Platform / OS / Hardware: Windows 11

Github hash: f346bcd

Hardware:

Intel Core i7-10750H CPU @ 2.69GHz (12 CPUs) 16 GB RAM NVIDIA GeForce GTX 1660 Ti S271HL NVIDIA High Definition Audio

Description of the Issue

When I put the rip of the game Fighting Vipers 2 (J) in my Content Location and run Flycast, the box art used for Fighting Vipers 2 (J) is the box art for Fighting Force 2.

Debugging Steps Tested

1) Put the ROM of Fighting Vipers 2 (J) in your Flycast Content Location directory 2) Run Flycast and open the game list, set to download and show thumbnails == The thumbnail that downloads and appears for Fighting Vipers 2 (J) is the thumbnail for Fighting Force 2, not the thumbnail for Fighting Vipers 2 (J).

Ie it is using https://thegamesdb.net/game.php?id=8128#cover instead of https://thegamesdb.net/game.php?id=123622#cover-1

Logs Gathered

flycast.log

Screenshots

Untitled-1 copy

flyinghead commented 3 months ago

This should now be fixed.

Flycast uses TheGamesDB to retrieve boxart and metadata. You can open an account and add missing or fix incorrect information. In this case, the disk UID for this game was missing (HDR-0133). image

smbhax commented 3 months ago

Thanks! I couldn't find a way in Flycast itself to force the thumbnail to refresh, but I was able to confirm it downloads correctly now by deleting the boxart folder (I suppose probably just deleting the .json inside it would have done the trick, although I dunno if the incorrectly assigned thumbnail jpg file would have got cleared out that way ^ _^).

I've registered at thegamesdb.net and should be able to deal with any other game I come across with this problem. : ) Took me a little googling but I worked out that for DC games the code it wants for "UID" is the first two parts of the printing on the inside of the data side of the GD-ROM; it's also printed in the region code box on the case back, and at the base of the spine cover (and the obi strip).

flyinghead commented 3 months ago

Sometimes the GD-ROM code listed on the case or referenced by redump.org is incorrect. To get the actual disk ID, start the game and it will be printed in the log:

00:06:777 emulator.cpp:54 N[BOOT]: Game ID is [MK-51064]

Enable Log to File on Windows, or start Flycast from the command line on linux or macOS to see the log.

smbhax commented 3 months ago

Ah! Yes, I see it there, thanks for the tip! : )