SimoneN64 / Kaizen

Experimental Nintendo 64 emulator
https://gadolinium.dev
BSD 3-Clause "New" or "Revised" License
126 stars 1 forks source link

[Feature request] Don't generate .EEPROM or .MEMPAK files unnecessarily #59

Closed DerekTurtleRoe closed 1 year ago

DerekTurtleRoe commented 1 year ago

Currently, the way this works is that a .EEPROM and .MEMPAK file are generated for each title you launch in Gadolinium. Not all games have EEPROM or MEMPAK support, so generating these files takes up space and clutters the file system. Being able to detect if the game needs those files beforehand would be awesome 😄

I have a database of which games support which save types if needed. 😄

DerekTurtleRoe commented 1 year ago

Also, I see code for FlashRAM and SRAM save support, which is good, but they should probably have their own file extension to reduce confusion and prevent things from getting overwritten.

An example would be if a game supports more than one save type, and both are considered .EEPROM or .MEMPAK saves, then when you save using another method, it gets overwritten. 😅

SimoneN64 commented 1 year ago

Also, I see code for FlashRAM and SRAM save support, which is good, but they should probably have their own file extension to reduce confusion and prevent things from getting overwritten.

An example would be if a game supports more than one save type, and both are considered .EEPROM or .MEMPAK saves, then when you save using another method, it gets overwritten. 😅

No I don't currently do anything with Flash or SRAM. I can just detect them I guess.

SimoneN64 commented 1 year ago

Addressed in 8c044b5