ok, now I think it is fixed, I tried a few things and eventually regress back to the same source, so I actually did nothing other than rebuild it again.
The fixed version is still beta99i pr2. Only replaced gen2_19.2.zip.
Download performed a few seconds ago should work.
Not knowing the root cause of why it didn't work earlier is concerning but there isn't anything I can do at this time.
The fixed version is still beta99i pr2. Only replaced gen2_19.2.zip.
Download performed a few seconds ago should work.
Not knowing the root cause of why it didn't work earlier is concerning but there isn't anything I can do at this time.
@dsrules have you tried updating Breeze directly from the app?1.9.2 was downloaded directly from official github, only the gen2 test build you posted yesterday worked for me
Only the one posted around one hour ago would work. The gen2 fork included in earlier version is bad for unknown reason. The test build would also work and the difference is minor and can be totally ignored.@dsrules have you tried updating Breeze directly from the app?
double confirm it's fixedok, now I think it is fixed, I tried a few things and eventually regress back to the same source, so I actually did nothing other than rebuild it again.
The fixed version is still beta99i pr2. Only replaced gen2_19.2.zip.
Download performed a few seconds ago should work.
Not knowing the root cause of why it didn't work earlier is concerning but there isn't anything I can do at this time.
Last edited by TomSwitch,
members only
Another attempt at explaining the Search Manager. Feedback is welcome from both new users and long-time users—especially from those who may have struggled due to my lack of documentation.
Post automatically merged:
Another attempt at explaining the Search Manager. Feedback is welcome from both new users and long-time users—especially from those who may have struggled due to my lack of documentation.
Last edited by TomSwitch,
Fantastic! Now it's clear, to me at least. Thank you so much for your hard work and the well documented menu!members only
Post automatically merged:
Another attempt at explaining the Search Manager. Feedback is welcome from both new users and long-time users—especially from those who may have struggled due to my lack of documentation.
Last edited by TomSwitch,
beta99j Pre-releaseView attachment 518342
Added this to beta99j
It insert a comment in front of the offending line. Edit and check again to remove/update the comment.
There is also a python script to do it.
What's New
- Added a Focus Edit button for easier customization of the Focus Mode button list.
members only
click on See how it works gives 404 page not found
Thanks for feedback. I moved the file location. The link in release note has been updated now.beta99j Pre-release
What's New
- Added a Focus Edit button for easier customization of the Focus Mode button list.
members only
click on See how it works gives 404 page not found


Calling cheat makers to give it a try.
Should also be useful for the curious and those that want to customize cheats.
Members-only download
For type 0 code, you can use any valid ARM64 instruction. If you write two instructions separated by a semicolon it will perform a 16-byte write.
You can also use directives such as .byte, .short, .word, .float, and .double.
The "Sort ASM" checkbox will sort sequential assembly lines within a cheat that are out of order. This helps you read the assembly code more easily, without needing to mentally rearrange it.

Last edited by TomSwitch,
Hi @TomSwitch
I got the same issues with LaMano when updating to your latest pre release 99j
reverting back to 99i latest release solves the issue of modular error pop up upon opening the breeze for the first time.. and on my further inspection of other menus i noticed that when exiting to search manager, the same error pops again.. and i cant leave a cheat with save b aswell
i tot this was an issue on specific codes where i raised to @OblivionReign in kingdoms of amalur.. but when i encountered it again this time on xenoblade x, which i did not experience during my first playthrough of this game.. im suspecting that breeze is the actual culprit..
(i believe my previous version during that time is beta99h when i first test their codes)
but all the codes are still working as intended despite of the error pop ups.
I got the same issues with LaMano when updating to your latest pre release 99j
I downloaded the new version and keep getting popups with "R2 is not main base address" or "m_R1 not found in m_memInfosModuleCodeStatic" etc. in my example for Mario Kart where there is no need for R2 or modular base... Do I have to configure something correctly that this popups are fine or not popping up with each change in the cheat list?
Also encounter the last days that sometimes I can not leave a cheat with Save "B" and I have to go through Home button and reenter Breeze.
reverting back to 99i latest release solves the issue of modular error pop up upon opening the breeze for the first time.. and on my further inspection of other menus i noticed that when exiting to search manager, the same error pops again.. and i cant leave a cheat with save b aswell
i tot this was an issue on specific codes where i raised to @OblivionReign in kingdoms of amalur.. but when i encountered it again this time on xenoblade x, which i did not experience during my first playthrough of this game.. im suspecting that breeze is the actual culprit..

(i believe my previous version during that time is beta99h when i first test their codes)
but all the codes are still working as intended despite of the error pop ups.
Last edited by pillowbasher,
It is an issue with breeze. But I can't tell if it's because of the modular setting that was added or a full on issue.Hi @TomSwitch
I got the same issues with LaMano when updating to your latest pre release 99j
reverting back to 99i latest release solves the issue of modular error pop up upon opening the breeze for the first time.. and on my further inspection of other menus i noticed that when exiting to search menu, the same error pops again.. and i cant leave a cheat with save b aswell
i tot this was an issue on specific codes where i raised to @OblivionReign in kingdoms of amalur.. but when i encountered it to again on xenoblade x, which i did not experience during my first playthrough on this game.. im suspecting that breeze is the actual culprit..
(i believe my previous version during that time is beta99h when i first test their codes)
but all the codes are still working as intended despite of the error pop ups.
Because there is a setting that you can turn on to use modular master code for games that support modules. And I was thinking, maybe that's interacting with the regular master code. The option can be turned off but I don't know if that same effect will still happen or not.
i looked around for the setting you've mentioned but i cant find it anywhere.. where exactly it is located? or maybe whats the exact name of it in the settings?It is an issue with breeze. But I can't tell if it's because of the modular setting that was added or a full on issue.
Because there is a setting that you can turn on to use modular master code for games that support modules. And I was thinking, maybe that's interacting with the regular master code. The option can be turned off but I don't know if that same effect will still happen or not.
Settings > then Normal [7] > use_module_id=0i looked around for the setting you've mentioned but i cant find it anywhere.. where exactly it is located? or maybe whats the exact name of it in the settings?
There is a check for valid R1 and R2 if they are in the master code and there is dynamic module in play.Hi @TomSwitch
I got the same issues with LaMano when updating to your latest pre release 99j
reverting back to 99i latest release solves the issue of modular error pop up upon opening the breeze for the first time.. and on my further inspection of other menus i noticed that when exiting to search manager, the same error pops again.. and i cant leave a cheat with save b aswell
i tot this was an issue on specific codes where i raised to @OblivionReign in kingdoms of amalur.. but when i encountered it again this time on xenoblade x, which i did not experience during my first playthrough of this game.. im suspecting that breeze is the actual culprit..
(i believe my previous version during that time is beta99h when i first test their codes)
but all the codes are still working as intended despite of the error pop ups.
The part about can't use B is a bug.
If you are not actually using Breeze on a game with dynamic module let me know and I will put it on higher priority. You can tell by looking at segment map and use the screen for module button.
If you are not working on game with dynamic module a quick work around is don't use master code. i.e. make it a normal code and place it first and turn it on. Make it master before release if you want the force on feature.
Post automatically merged:

updated assemble gui, now it highlight the error line and right panel will scroll in tandem with the left.
Post automatically merged:
This auto merge feature is super annoying. These two above are separate topic. If any admin see this message can you please put a consideration to trust people with higher level knowing that they are doing and don't auto merge their message?
Last edited by TomSwitch,
I dont really know what im doing or looking for here.. but attached is the image of the segment map and by pressing the screenmodule buttonThere is a check for valid R1 and R2 if they are in the master code and there is dynamic module in play.
The part about can't use B is a bug.
If you are not actually using Breeze on a game with dynamic module let me know and I will put it on higher priority. You can tell by looking at segment map and use the screen for module button.
This is the default right so meaning its off? i usually left the settings untouched or by default especially if im not sure what is it for..Settings > then Normal [7] > use_module_id=0
Post automatically merged:
ok this helps me on the pop ups and unable to exit on save b..If you are not working on game with dynamic module a quick work around is don't use master code. i.e. make it a normal code and place it first and turn it on. Make it master before release if you want the force on feature.
Attachments
Last edited by pillowbasher,
Similar threads
- Replies
- 1
- Views
- 253
- Replies
- 3
- Views
- 282
- Replies
- 8
- Views
- 571
- Replies
- 2
- Views
- 242













