bfttfInitialize: No BTTF fonts retrieved!

[xandersalarie]

Describe the bug trying to launch odyssey downgrader but got an instant error message: "an error has occurred while initializing resources. bfttfInitialize: No BTTF fonts retrieved! For more information, please check the logfile"

(it didn't create a logfile?)

To Reproduce Steps to reproduce the behavior:

1. Go to 'both applet mode and/or title override'
2. Click on 'odyssey downgrader'
3. See error

Please fill the following information:

• Horizon OS (Switch FW) version: [e.g. 10.0.0] 18.1.0
• CFW: [e.g. Atmosphère, SX OS, etc.] atmosphere
• CFW version: [e.g. 0.11.1, 2.9.4, etc.] AMS 1.7.1|S
• Atmosphère launch method (if applicable): [e.g. Hekate, fusee-primary] i use hekate to boot into atmosphere
• nxdumptool version: [e.g. 2.0.0] 1.1.15
• Homebrew launch method: [e.g. title override, applet] both
• Source storage used with the application (if applicable): [e.g. gamecard, SD/eMMC] n/a but want to use SD
• SD card specs: [e.g. Samsung EVO 256 GB, FAT32 partition] Samsung EVO 512GB FAT32

Screenshots Add screenshots to help explain your problem.

Logfile If available, please upload your logfile located at sdmc:/nxdumptool/nxdumptool.log.

Additional context tried to boot up the .nro but got insta hit with an error

[karateman10998]

Odyssey Downgrade.log

[karateman10998]

Any potential fix for this??

[xandersalarie]

Any potential fix for this??

i still haven't found a fix for this.... also there is no log created for me somehow

[karateman10998]

I can still reproduce the issue @xandersalarie can I help in any way?

[Joe-the-Moe]

Bumping this. Experiencing the same issue.

[SkyJumper409x]

From the sound of the log file provided by karateman10998, this might be caused by outdated keys. Not sure, though.

[Joe-the-Moe]

From the sound of the log file provided by karateman10998, this might be caused by outdated keys. Not sure, though.

@SkyJumper409x I just redownloaded my keys and got the same issue again, so that likely isn't causing the issue, for me at least.

[SkyJumper409x]

From the sound of the log file provided by karateman10998, this might be caused by outdated keys. Not sure, though.

@SkyJumper409x I just redownloaded my keys and got the same issue again, so that likely isn't causing the issue, for me at least.

What do you mean by "redownloaded"? Keys should be dumped using the Lockpick_RCM payload, which, afaik, has to be updated from time to time for the dumped keys to be up to date.