You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It appears that when clones of a game exist, instead of those clones sharing the same resource files (i.e. screenshots and cover art), duplicate copies of those resources get downloaded from sources like IGDB or MobyGames. If there are a lot of clones, this would effectively consume a lot of unnecessary storage. Currently, my resources directory consumes 7.9 GB of space for my 24 platforms.
Describe the solution you'd like
Instead of downloading the same resource files for each individual clone, the same parent game/rom resource files should be used for each individual clone. Since RomM already has a mechanism for grouping "clones" (or in terms of RomM, "duplicates"), it seems as if that same mechanism may be leveraged to point to the parent game's resource files as well. This would help save on storage space, potentially cutting down the amount of space used by about 20 to 40%. Also, this would help avoid unnecessary download requests made to IGDB and/or MobyGames.
Describe alternatives you've considered
I haven't thought of any alternatives; however, I've thought about two approaches for how this could be handled. The first approach could be data-driven such that the resource references in a database table (if that's where the references are stored) for each clone could just point to the same resource directory that the parent game points to.
The second approach could be to just create symlinks on the filesystem for each clone to point to the parent game's resource directory.
Additional context
Here are screenshots showing 2 of 3 duplicated resources for the same game to demonstrate what I described above.
The text was updated successfully, but these errors were encountered:
RomM groups siblings (optionally) In order to make easier navigate and find different versions of the same game or just to make the gallery cleaner, but some users just uses different covers for different regions or versions.
Apart from that, this can cause additional issues: what if you delete the "main" version (the one that has the cover stored) but not the others? That will let all of the others without cover and you should scan them again.
And probably there will be more issues that I can't think about right now
@zurdi15 If you delete the main version, I would imagine that something would take the place of the previous main version. The resource files could be moved to the new main version to help minimize the impact.
If each version of the same game downloaded completely different files from IGDB/MobyGames, then having those files stored in their own directories makes complete sense. However, so far, I've noticed most/all of my clones are the same files.
Is your feature request related to a problem? Please describe.
It appears that when clones of a game exist, instead of those clones sharing the same resource files (i.e. screenshots and cover art), duplicate copies of those resources get downloaded from sources like IGDB or MobyGames. If there are a lot of clones, this would effectively consume a lot of unnecessary storage. Currently, my
resources
directory consumes 7.9 GB of space for my 24 platforms.Describe the solution you'd like
Instead of downloading the same resource files for each individual clone, the same parent game/rom resource files should be used for each individual clone. Since RomM already has a mechanism for grouping "clones" (or in terms of RomM, "duplicates"), it seems as if that same mechanism may be leveraged to point to the parent game's resource files as well. This would help save on storage space, potentially cutting down the amount of space used by about 20 to 40%. Also, this would help avoid unnecessary download requests made to IGDB and/or MobyGames.
Describe alternatives you've considered
I haven't thought of any alternatives; however, I've thought about two approaches for how this could be handled. The first approach could be data-driven such that the resource references in a database table (if that's where the references are stored) for each clone could just point to the same resource directory that the parent game points to.
The second approach could be to just create symlinks on the filesystem for each clone to point to the parent game's resource directory.
Additional context
Here are screenshots showing 2 of 3 duplicated resources for the same game to demonstrate what I described above.
The text was updated successfully, but these errors were encountered: