Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Azahar is not capable to use movable.sed from inital launch old 3ds. #681

Closed
1 task done
AmyRoxwell opened this issue Mar 16, 2025 · 0 comments · Fixed by #697
Closed
1 task done

[BUG] Azahar is not capable to use movable.sed from inital launch old 3ds. #681

AmyRoxwell opened this issue Mar 16, 2025 · 0 comments · Fixed by #697
Assignees
Labels
bug Something isn't working

Comments

@AmyRoxwell
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Affected Build(s)

2120-rc1

Description of Issue

Currently, Azahar is only capable of loading 320 byte movables, making launch consoles movable.sed completely incompatible and throw an "Invalid" error while trying to load it.

Only way to "Fix it" is by adding two rows of additional gibberish into the file itself, letting the file finally be able to be "Loaded"

Expected Behavior

Being able to load the movable.sed of an launch old 3ds on the settings section `Real Console Unique Data"

Reproduction Steps

  1. Acquire a launch model old 3ds.
  2. Dump the movable.sed using godmode
  3. Check using a hex editor that it only has up-to row 00000110
    Image
  4. Try to load this file on the Movable.sed section.
    Image

Log File

azahar_log.txt

System Configuration

CPU: Ryzen 5600
GPU/Driver: RX6600/Mesa 25.0.1-arch1.2
RAM: 16gbs ddr4 3200mhz
OS: EndeavourOS (Arch linux based distro)

@AmyRoxwell AmyRoxwell added the bug Something isn't working label Mar 16, 2025
@PabloMK7 PabloMK7 self-assigned this Mar 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants