search

libretro / RetroArch

Cross-platform, sophisticated frontend for the libretro API. Licensed GPLv3.
http://www.libretro.com
GNU General Public License v3.0
10.32k stars 1.84k forks source link

Ozone assets exists but RetroArch claims it's missing #9231

Open RisingHopperZeroOne opened 5 years ago

RisingHopperZeroOne commented 5 years ago

Description

While Ozone theme's assets are present in the nightly 7z archive, when in RA on the Switch, you'll recieve the warning that assets are missing.

When testing further for some reason, the Ozone theme uses assets from the Monochrome XMB theme.

Expected behavior

When using the Ozone theme, there shouldn't be a warning as all assets are present.

Actual behavior

When using the Ozone theme, you will recieve a warning that assets are missing even though they are all present.

Steps to reproduce the bug

  1. Copy RetroArch files to Switch
  2. Select it from the homebrew menu
  3. As Ozone is the default theme, you will recieve a warning assets are missing

Bisect Results

As far as I know every nightly build after the 1.7.7 stable build has this problem, the latest tested was the 29th on the Switch.

Version/Commit

You can find this information under Information/System Information

Environment information

rsn8887 commented 5 years ago

I have never seen this warning on my Switch. Where does it appear? Are you sure you are not using exFAT (causes corruption)? Are you sure you don't have the archive flag set on any of your folders inside /Retroarch dir?

RisingHopperZeroOne commented 5 years ago

I am not using exFAT and have not set an archive flag on any of the folders.

I did explain the problem as I have tested this by removing and adding files.

When testing further for some reason, the Ozone theme uses assets from the Monochrome XMB theme.

rsn8887 commented 5 years ago

So to be clear: When you copied all the bundled files (all assets etc.) to your Switch like you are supposed to when you install Retroarch (or download assets using the online updater), there was no error message and everything worked.

Only when you then deleted some of the assets, then you got an error message.

If my description above is correct, in my opinion I don't think this is an issue. Just don't delete assets, always copy all of them. I don't think assets are designed to be used in a "mix and match" way.

RisingHopperZeroOne commented 5 years ago

This wasn't an issue with the 1.7.7 stable build as the assets are loaded from the correct folder, Ozone didn't need to have Monochrome XMB present to have all it's assets loaded.

When checking the asset folder itself shows that Ozone had ALL the nessesary asset files present in the Ozone folder, it's just ignored by RetroArch for some reason.

Logically if all the files for Ozone are present in the Ozone asset folder, why does RetroArch ignore it and load from Monochrome XMB?

andiandi13 commented 3 years ago

No updates in 2021 ?

I got the same issue on 1.9.1 Windows x64.

ozone/png/icons has is the same as xmb/monochrome/png, so why ?