RAM Editor broken in SX OS 2.9.2

lahma0

lahma0

VIP Member
Oct 15, 2018
16
8
After updating to SX OS 2.9.2, attempting to jump to a specific MAIN+0x??????? offset memory location fails with the message "ERROR: Invalid Address Specified". I am 100% certain that this memory location does indeed exist because codes that use this address work just fine. For the sake of being thorough, I will provide an example below of a cheat code that works fine using such an offset yet fails when trying to jump to the same offset in the RAM Editor.

Game: Fire Emblem Three Houses
Title ID: 010055d009f78000
Build ID: 19ba39bd3ee8131d

Working Code:
[9000 Money]
580A0000 01A846F0
780A0000 00023B54
640A0000 00000000 00002328

Not Working:
  • Start playing Fire Emblem Three Houses
  • Return to Home menu
  • Open SX OS Album Menu
  • Navigate to "Cheat" tab
  • Open "RAM Editor"
  • Hit "+" to go to "Jump To Address"
  • Enter offset from code above:
    • MAIN+0x01A846F0
  • Does not work and gives the error message "ERROR: Invalid Address Specified"
 
lahma0

lahma0

VIP Member
Oct 15, 2018
16
8
It would be great to get a confirmation from a team member that this bug has been recognized/acknowledged so that it can be fixed in a future release. My only purpose for posting this here was to bring it to the attention of the developers in case they were not already aware of its existence.
 
C

c0013r

Noob Account
Nov 15, 2019
1
1
Russia
+1 for a bug. Updated SX OS to 2.9.2 / switch to 9.0.1. Tried to find some known addresses in Divinity 2 but had no luck.
 
  • Like
Reactions: lahma0
lahma0

lahma0

VIP Member
Oct 15, 2018
16
8
If you haven't update your firmware to 9.0+ yet, it seems the easiest solution right now is to probably go back to SX OS 2.8. Or, perhaps you might consider taking a more permanent solution like I am, and switch over to using an Atmosphere based CFW. There have just been too many issues with SX OS of late, some of which are permanent and irreversible outside of hardware modifications (mostly talking about game cart fuse burning without any warning).

I am not a fanboy of any brand or CFW but looking at the situation objectively, there are many things being accomplished on the other side of the fence right now that are important to me that Xecuter doesn't seem to have any motivation in fixing/implementing. One of my biggest complaints right now is that with the SX OS cheat format. There are some VERY basic things that their code format is simply incapable of doing.

With the SX OS cheat format, you cannot:
- Write the value of a register to a memory address
- Write one register to another
- Write the value of one register to a memory address stored in another register
- Store the value of a memory address contained in a register to another register

Atmosphere's cheat format while being backwards compatible with the SX OS format, allows you to do all of these things and much, much more (see code type 0x9, 0xA, etc). I'm just getting tired of waiting around for stuff like this, so I'm weighing the cost (mostly, my time) of switching over to another CFW. Again, I think you just have to look at your own situation and decide what works best for you.

Note: Again, I want to reiterate, I am not "dissing" on SX OS or trying to trigger anyone... If you disagree with me, that is perfectly fine and I am not going to criticize anyone who does. There are legitimate reasons that people use SX OS over other options (hell, I have since the beginning and still am using it). Just wanted to ensure people know where I'm coming from...
 
  • Like
Reactions: ndjembe and zohayer
You must log in or register to reply here.