Toggle menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

NTRRemoteDebugger 3DS: Difference between revisions

From GameBrew
m (Text replacement - "Category:PC utilities for 3DS homebrew" to "")
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Infobox 3DS Homebrews
{{Infobox 3DS Homebrews
|title=NTRRemoteDebugger
|title=NTRRemoteDebugger
|image=NTRRemoteDebugger-3DS.png
|image=Ntrremotedebugger4.png
|description=Tool to interface with NTR CFW's remote debugging.
|description=Tool to interface with NTR CFW's remote debugging.
|author=valarnin
|author=valarnin
Line 30: Line 30:
The progress bar does not work for narrowing search results, just be patient. It's about 1/3rd of a second per result check.  
The progress bar does not work for narrowing search results, just be patient. It's about 1/3rd of a second per result check.  


NTR's performance seems to degrade over time if the connection gets interrupted at all.  
'''Note:''' NTR's performance seems to degrade over time if the connection gets interrupted at all. After about 10 interrupted connections, a reboot is needed to get NTR's Debugger to start responding properly again. It seems that running [https://github.com/Shadowtrance/BootNTR NTR 3.3 fork] from Shadowtrance with the 3.2 ntr.bin (same repo) is better for stability and also works on 10.6.
* After about 10 interrupted connections, a reboot is needed to get NTR's Debugger to start responding properly again.  
* It seems that running [https://github.com/Shadowtrance/BootNTR NTR 3.3] fork from Shadowtrance with the 3.2 ntr.bin (same repo) is better for stability and also works on 10.6.


==Screenshots==
==Screenshots==
https://dlhb.gamebrew.org/3dshomebrews/ntrremotedebugger3.png
https://dlhb.gamebrew.org/3dshomebrews/ntrremotedebugger3.png


==Compatibilty==
==Compatibility==
Tested on 11.4 with BootNTR 3.5 loaded via BootNTR Selector. No stability issues found.
Tested on 11.4 with BootNTR 3.5 loaded via BootNTR Selector. No stability issues found.


Line 43: Line 41:
* GitHub - https://github.com/valarnin/NTRRemoteDebugger
* GitHub - https://github.com/valarnin/NTRRemoteDebugger
* Reddit - https://www.reddit.com/r/3dshacks/comments/44jtfm/beta_release_for_ntr_cheat_tool_a_new_tool_to
* Reddit - https://www.reddit.com/r/3dshacks/comments/44jtfm/beta_release_for_ntr_cheat_tool_a_new_tool_to
[[Category:3DS homebrew applications]]
[[Category:PC utilities for 3DS homebrew]]

Latest revision as of 04:32, 6 Mayıs 2024

NTRRemoteDebugger
Ntrremotedebugger4.png
General
Authorvalarnin
TypePC Utilities
Version0.8.6.3-beta
LicenseMixed
Last Updated2016/05/23
Links
Download
Website
Source

NTRRemoteDebugger is a tool to interface with NTR CFW's remote debugging functionality.

Features

  • Nice GUI for searching for memory addresses and modifying them.
  • No messing about with files or other external resources.
  • Allows searching for byte, short, int, long, float, double, list of bytes, and text strings.
  • Subsequent searches will narrow search results by only requesting the memory addresses needed, speeding up things significantly.
  • Ability to "lock" memory addresses to a given value. This means that they are set automatically based on a configured value.
  • Can convert AR3DS codes to work with the tool.
  • Works on mono and via wine. Thanks to u/Melon__Bread for verifying mono support (and MonoDevelop compile support) and u/MattKimura for verifying wine support.

User guide

The first half of the progress bar at the bottom is for receiving memory values from the 3DS. The second half is for searching for the value.

Editing items in the bottom-right grid (the 'Values' grid) requires double clicking. This is strange behavior for the checkbox and dropdown cells.

The progress bar does not work for narrowing search results, just be patient. It's about 1/3rd of a second per result check.

Note: NTR's performance seems to degrade over time if the connection gets interrupted at all. After about 10 interrupted connections, a reboot is needed to get NTR's Debugger to start responding properly again. It seems that running NTR 3.3 fork from Shadowtrance with the 3.2 ntr.bin (same repo) is better for stability and also works on 10.6.

Screenshots

ntrremotedebugger3.png

Compatibility

Tested on 11.4 with BootNTR 3.5 loaded via BootNTR Selector. No stability issues found.

External links

Advertising: