Homebrew Homebrew app sys-patch - sysmod that patches on boot

[froggy55]

Yes they're difference but sadly due to all bitching and cat fight of the latest time the code was released the gurus are trying ykeep the code away of public. Once is stable I will share diffs for the one interested

where can i download syspatch 1.5.3 ive been looking and cant find it thanks again for the hard work

 

[draftguy123]

where can i download syspatch 1.5.3 ive been looking and cant find it thanks again for the hard work

https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10519569

 

[josete2k]

Test buid.

Thanks to @impeeza and the gurus of the scene. I'm just a compiler and tester.



New patternt for forwarders compatibility. Please report!!!! We need more tests.

Note: ERPT patch, debug_flag and debug_flag_off patches are disabled by default.

 

[captn1ko]

Hello everyone,

I have now updated syspatch for the first time after I had reinstalled everything and have a few questions that I hope someone here can answer.

Before the update, all patches that I had selected under “Toggle Patches” were displayed in the log. And all of them were either green or yellow.

Also es1-es7 were all displayed in green in the log. Unfortunately I don't have a screenshot of the log before the update

With the latest update it looks like this (see pictures)

- Options are all on
- debug and no_erpt off per default
- es1 - es6 and many FS patches no longer displayed green/yellow in the log

--> Is that ok the way it looks?
--> Can someone explain to me why many other patches (es1 to es7 for example) were shown green or yellow in the log before?
-- > Was the installation faulty before the update and showed too many patches or does it now show too few?

My newly created forwarders finally work with the latest update. Thanks @josete2k and @impeeza

 

[linuxares]

Looks at OK! Since es1 to es6 isn't used on newer firmwares. es7 is the latest in this case.

 

[impeeza]

Hello everyone,

I have now updated syspatch for the first time after I had reinstalled everything and have a few questions that I hope someone here can answer.

Before the update, all patches that I had selected under “Toggle Patches” were displayed in the log. And all of them were either green or yellow.

Also es1-es7 were all displayed in green in the log. Unfortunately I don't have a screenshot of the log before the update

With the latest update it looks like this (see pictures)

- Options are all on
- debug and no_erpt off per default
- es1 - es6 and many FS patches no longer displayed green/yellow in the log

--> Is that ok the way it looks?
--> Can someone explain to me why many other patches (es1 to es7 for example) were shown green or yellow in the log before?
-- > Was the installation faulty before the update and showed too many patches or does it now show too few?

My newly created forwarders finally work with the latest update. Thanks @josete2k and @impeeza

everything looks fine, if you like to disable erp loggin and be able to run old forwarders on new firmware you can enable them on <<toggle patches>> at main page of overlay, but they are optionals.

 

[captn1ko]

One Thing:

Debug flag enabled bugs FPSlocker. Is this a known issue?

 

[impeeza]

One Thing:

Debug flag enabled bugs FPSlocker. Is this a known issue?

as far I know debug flag remove the new way of processing the debug flags on the new firmware, that new flag processing algorithms avoid some type of homebrew like the forwarders to run on new firmware.

 

[captn1ko]

When I activate the debug flag, the FPSlocker overlay shows "nx-fps is not running",

Debug is disabled and FPS locker works as usual, but my old forwarders no longer work. I had to recreate them.

 

[NotUsingAnAltAccount]

Just make new forwarders, it takes seconds to do one of them.

 

[impeeza]

Just make new forwarders, it takes seconds to do one of them.

no everyone can, most people are not able to read two lines of text...

 

[NotUsingAnAltAccount]

no everyone can, most people are not able to read two lines of text...

That's the whole problem or rather they're making the problem with one flag. Most of them for sure don't have more than 5 or up to 10 forwarders.

 

[Blythe93]

Just make new forwarders, it takes seconds to do one of them.

I must be in minority for not using any forwarder whatsoever.

I also don't use cheats nor do I fiddle with overclocking and stuff either. The only sys-modules I use are sys-patch and emuiibo (and TriPlayer to play my own music when gaming, but not as often nowadays).

 

[captn1ko]

I must be in minority for not using any forwarder whatsoever.

I only have 1 (RetroArch) ^^

 

[NotUsingAnAltAccount]

I have Shenmue, Shenmue II, Diablo and that's it. I really can't see any problem in making new forwarders. Instead of fiddling around and make other things not working it's much easier to spend one minute on making new ones. But hey, people are people

 

[petspeed]

I must be in minority for not using any forwarder whatsoever.

I also don't use cheats nor do I fiddle with overclocking and stuff either. The only sys-modules I use are sys-patch and emuiibo (and TriPlayer to play my own music when gaming, but not as often nowadays).

Me too. I only have sys-patch.

 

[josete2k]

Yeah. I think that New forwarders are the best option.

They only have one issue, in some apps the exit button don't give you to the system menu, they just reload apps again.

DBI has the feature to exit to home menu or system menu, but chiaki or tinfoil don't.

 

[nerirififi]

I have a few questions about the new 19.0 firmware and the latest homebrew releases.

Is it stable, or are there still some bugs or things doesn't work?
Also, regarding forwarders, I understand they’re easy to create, but will they still work after future updates? That is, assuming Nintendo doesn’t make any changes that affect forwarders.

 

[shadow256]

I have a few questions about the new 19.0 firmware and the latest homebrew releases.

Is it stable, or are there still some bugs or things doesn't work?
Also, regarding forwarders, I understand they’re easy to create, but will they still work after future updates? That is, assuming Nintendo doesn’t make any changes that affect forwarders.

Nintendo can always make changes that could affect everything in fact, forwarders worked perfectly since firmware 12.0.0, now in 19.0.0 we should recreate them witch is the best option, the debug patches should be used just for the transition cause making new forwarders is not so difficult (and for me it's not realy useful except the one to launch the Homebrew Menu witch can also be launched by maintening "R" when launching a game (atmosphere's default config, could be changed by a config file)).

For homebrew it's the modules witch need to be recompiled for the new Atmosphere's version, others homebrews should work.

 

[TomSwitch]

One Thing:

Debug flag enabled bugs FPSlocker. Is this a known issue?

debug flag enabled elevate all applications (that is what games are) so whatever that need to be able to "debug" game and don't have the flag becomes useless.