Open Fragtaster opened 1 year ago
MP2E
commented
1 year ago Startropics 1 and 2 work perfect here, they require NES 2.0 headers to function properly.
I recommend running the following python script to fix your rom headers, then it will likely work for you too
Fragtaster
commented
1 year ago Thank you for the response, I will test that solution (header patching) when I get a chance!
SegaSnatcher
commented
1 year ago Or just try to find a 2.0 romset. Then you don't have to worry about headers.
Toryalai1
commented
1 year ago This works. Close the issue
Hi,
I'm simply reporting a issue here today - since I don't have much time to address it myself further. I have been lightly testing this core for a while now, and run across two games that appear to have a issue (not sure if it's related to the mapper, or anti-DRM related): they are 'Star Tropics' and 'Star Tropics II -Zoda's Revenge'.
For clarification, this issue seems to effect both games regardless of which region ROM you choose (atleast in my own limited testing), and even occurs in ROMS that have had fan hacks applied! Specifically though, for brevity sake, I will be speaking of the bog standard USA (Rev A) ROMS today - where-in the issue is in regards to the starting 'name' screen on both titles.
Like the Legend of Zelda games; upon starting both Star Tropics I & II, you must choose a file-slot and name it to start the game. The issue is that using the current MISTER-NES core - after inputting the name, and confirming - the file name fails to save, and you are unable to proceed into the game (it essentially does not accept the file creation).
Star Tropics II - Zoda's Revenge has essentially the SAME issue (again, wondering if this is a anti-DRM issue) - but with the caveat, that the blank spots where you must insert a file name, are 'pre-filled' with a blue artifact that should not be there. Besides that anomaly; after trying to insert a name to a file, the same issue as before occurs, where the game simply refuses to remember the name you just assigned (locking you out of starting the game).
This issue was present a few updates back as well (when I discovered it) - so I do not believe this is a bug introduced with current core updates - but rather possibly a legacy issue specific to this title, that has yet to be addressed. I am aware that both of these games are notorious for their anti-piracy issues on some emulators in the distant past.
If anyone can get around to checking this out, I would appreciate this. I have tested many different ROM sets, validated files, and both compressed and uncompressed formats (as well as SD and external HDD) - this appears to simply be related to these titles, and how they interact with the core. I have kept my core updated both manually and recently with the update-all.
Thank you for your time guys! Much appreciation for your hard work.