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
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
Acquire a launch model old 3ds.
Dump the movable.sed using godmode
Check using a hex editor that it only has up-to row 00000110
Is there an existing issue for this?
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
movable.sed
using godmode00000110
Movable.sed
section.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)
The text was updated successfully, but these errors were encountered: