zulooto.blogg.se - Bootntr troubleshooting pcalc

#Bootntr troubleshooting pcalc install#
#Bootntr troubleshooting pcalc Patch#
#Bootntr troubleshooting pcalc code#

It uses debug sessions to have read/write access to the game.

#Bootntr troubleshooting pcalc Patch#

PokeReader doesn't patch system modules, so it's more resiliant to updates and less prone to patching incorrectly. This also prevents locks between PokeReader, the game, and the home menu. The pkrd:game session handle is given to PokeReader so games don't need to open a session, which means smaller patches.ĭebug sessions are closed after they're used so other tools (like Rosalina) can freely open debug sessions as well, provided the sessions are cleaned up after use.

#Bootntr troubleshooting pcalc code#

PokeReader receives the stack pointer as an argument, opens a debug session with the game, and runs whatever code we want for that game.The game runs the patched function and behaves the same as normal, except it also runs pkrd:game's game hook command.The patch runs pkrd:game's game hook command with a copy of the pkrd:game session handle When a game launches, PokeReader checks to see if it's a known game and patches the same function NTR patches.The launcher runs the setup command, which moves pkrd:game's session handle to PokeReader.The launcher opens a session to pkrd:game.

PokeReader sets up pkrd:game and subscribes to a custom Luma notification to be notified when a game launches.

The launcher homebrew launches PokeReader.

PokeReader also comes with a launcher homebrew, so it only runs when a user wants it to.īelow are the steps of launching PokeReader to running code with game access: This service provides two commands: a setup command and a game hook command. PokeReader is a sysmodule that runs as a background process, and runs a service called pkrd:game. It was great at the time, but Luma has added several extensions and patches that could provide a better solution. However patching multiple sysmodules makes NTR a fragile solution. With the same permissions and hooking into a function responsible for graphics, plugins can easily draw to the console screen.

Patch the game in a function responsible for helping with graphics to run the plugin codeīy having the game's process run plugins, plugins have all permissions the game does.

Load plugins into memory when a game launches.

Provide the ability to run custom code when a game is launched.

NTR works by patching several sysmodules to accomplish a few things: While this hides two register's values, it does provide pretty quick insight into a problem area. If luma's crash screen is enabled, panics will show the last four characters of the causing file in r9 and the line that caused the panic in r10. The debug build will write logs to /ctr-logs.txt, so it will be slower than the release build. Luma will load those when the sysmodule is launched. Rather than installing the cia after every change, you may find it more convenient to copy the files at out//000401300000CB02 to /luma/titles/000401300000CB02 on your 3ds.

Run pkrd-launcher from the hombrew menu (if 3dsx) or home menu (if cia).

#Bootntr troubleshooting pcalc install#

Install out/release/pkrd.cia to your console.Install launcher/out/pkrd-launcher.cia or copy launcher/out/pkrd-launcher.3dsx to your console's /3ds directory.Run make in the launcher directory to build the launcher.Run make to build the debug and release builds.Install make, rust, makerom, ctrtool, devkitarm, and devkitpro's 3ds libs.You most likely shouldn't install it right now. PokeReader is a 3ds sysmodule that currently doesn't do anything, and is just a fun test. This is an experiment to replace ntr + pcalc with something more stable using modern Luma features.