Homebrew NTR Viewer Automated Launch Scripts

[Vahkiti]

So after spending days trying to get the setup for NTR 3.4's remote play thingy working properly, I decided to make it a bit cleaner and easier to run just on a whim. The result is these bunch of scripts that make the entire process of running the PC programs automatic right down to command input. You will however need Autohotkey for that part. Here's a demonstration:



The following is a rundown of what all the attached files do.

NOTE: This assumes you need FakeProxy, and have it in the same folder as the folders for NTRViewer and NTRDebugger. It can be easily edited to work without FakeProxy, but I don't particularly feel like doing so myself right now.

Spoiler

START.bat: The main launcher for the script set. You can make a shortcut to this wherever.

Proxy.bat: Second in the chain. Launches FakeProxy, and temporarily dumps it's output to output.log

Proxy.vbs: A VBS script used to hide the command window for Proxy.bat

NTRViewer.bat: Contains custom window scaling settings for the NTR Viewer. You may need to edit this and replace the command with your own preferred settings. Consult the tutorial linked below for more info on that.

NTRViewer.vbs: Ditto to Proxy.vbs

Connect.ahk: Autohotkey script that launches NTRDebugger, inputs the commands automatically, then kills the process. You will need to edit this and replace the aforementioned commands with your own IP address and preferred settings. Consult the tutorial linked below for more info on that.

ntrconfig.xml: The only file I rehosted from NTR itself. For some reason it wants to create it here instead of in the executable's folder, and will break the script chain if it's not found the first time.

Cleanup.bat: Technically the third in the chain, but also the last. Tests for the activity of NTRViewer.exe. If not found, the script terminates itself and FakeProxy.

Cleanup.vbs: Ditto to the last two VBS scripts.

And before you say it, yes, I know my demonstration does not show the debugger closing on it's own. I only added that after I made the video, because it was only then that I realized it didn't need to be open for the viewer to remain functional.

Aforementioned tutorial for setting this whole ordeal up: https://gbatemp.net/threads/tutoria...without-a-capture-card-ntr-cfw-method.423445/

If you have any further question on this, I suppose you know how to get a hold of me.

 

[JustAKirby]

Nice. Thanks for sharing this tool with us

 

[Majickhat55]

So my question is would you be able to save different configurations as separate commands? Like if my IP address for my 3DS isn't static or if I want to change the arguments for the NTR Debugger/viewer? That would be cool to save different settings for different games and auto-launch without having to reconfigure every instance.

 

[Vahkiti]

So my question is would you be able to save different configurations as separate commands? Like if my IP address for my 3DS isn't static or if I want to change the arguments for the NTR Debugger/viewer? That would be cool to save different settings for different games and auto-launch without having to reconfigure every instance.

I'm not sure about different COMMANDS, but as different batch files, yes. Some of the ones I've included need to be altered anyways, as mentioned in the rundown. Besides, if your 3DS' IP isn't static, you'd probably just be better off making it so. You can do that through the system's own internet connection settings.

 

[Majickhat55]

Yeah I know how to make it static, I meant running different arguments in the NTR debugger like the priority mode etc. It would get tedious changing that everytime if the "sweetspot" in games are different.

 

[Vahkiti]

Yeah I know how to make it static, I meant running different arguments in the NTR debugger like the priority mode etc. It would get tedious changing that everytime if the "sweetspot" in games are different.

Ah, fair point. Well I'm sure there's a way it can be done, I'd just need to look into it. To be perfectly honest, I know very little about scripting myself. I just throw these things together based on loose excerpts from tutorials I Google for various functions I want to create. I know more about Minecraft's butchered-ass command block Json than I do about this. Although it DID help that I already made something very similar for Starbound back when it had corruption problems up the wazoo.

 

[Majickhat55]

Fair enough. Just something I thought about that could potentially improve the usefulness, though it would be pretty simple to just edit the .bat to run the arguments and just save them as per game used. Still, would be better to auto-boot the auto-boot and be able to choose which config to run at execute vs having a folder full of BAT files...... Hmmmmm I'll fiddle with them if you don't mind XD

 

[Vahkiti]

Fair enough. Just something I thought about that could potentially improve the usefulness, though it would be pretty simple to just edit the .bat to run the arguments and just save them as per game used. Still, would be better to auto-boot the auto-boot and be able to choose which config to run at execute vs having a folder full of BAT files...... Hmmmmm I'll fiddle with them if you don't mind XD

Go right ahead. I'm curious to look into it myself, but at the same time I should probably take a break. I've been up all night working on this, and right before uploaded it, I accidentally made Proxy.vbs reference Start.bat instead of Proxy.bat. The result? An endless loop of infinitely launching command prompts that crashed my computer. It took me a lot longer than I'd like to admit to figure out what the problem was. Never code when you're overtired. :|

To the best of my current understanding, I think your best bet would be to look into making a prompt that asks for a number input, which would correspond to a specific Autohotkey file that then contains your perimeters. Whatever commands do that, would either replace, or be placed before the autolaunch sequence at the end of Start.bat.

 

[Vahkiti]

Fair enough. Just something I thought about that could potentially improve the usefulness, though it would be pretty simple to just edit the .bat to run the arguments and just save them as per game used. Still, would be better to auto-boot the auto-boot and be able to choose which config to run at execute vs having a folder full of BAT files...... Hmmmmm I'll fiddle with them if you don't mind XD

Just figured it out. Well.. mostly. Only needed to edit START.bat. Give it a whirl.

Spoiler

@Echo off
cd FakeProxy
del output.log
cd..
start Proxy.vbs
cd FakeProxy
:loop
timeout /t 2 >NUL
echo Waiting for N3DS...
(type output.log |find "GET") > nul 2>&1
if errorlevel 1 goto loop

timeout 50

cd..
@Echo off
echo Please choose a configuration.
echo Config 1
echo Config 2
echo Config 3

set /p whatapp=

if %whatapp%==1 (
start Connect1.ahk
start NTRViewer.vbs
start Cleanup.vbs
) else if %whatapp%==2 (
b
) else if %whatapp%==3 (
c
)
exit

Obvs, config 2 and 3 are placeholders, and do nothing but exit the batch when selected. B and C are also placeholders for basically the same set of start commands that are where A would be. Connect.ahk is renamed here for the purpose of demonstration.