Toggle sidebar

Hacking NTR 3.4 Screen Recorder Test Thread

  • Thread starter Thread starter NekoMichi
  • Start date Start date
  • Views Views 84,653
  • Replies Replies 443
  • Likes Likes 5
thekarter104 said:
Yes, I have, what else is going on ??
Click to expand...
Which CFW are you using as base? I'm currently using AuReiNAND.
astronautlevel said:
Yes, but it's probably still better to connect over Ethernet.
Click to expand...
The spec sheet for the router I'm about to buy says it supports up to 433mbps via wireless, but only 100mbps over Ethernet. That can't be right, can it?
 
Last edited by NekoMichi,
Here you go, two videos of it. In the first I use MH4U, Liberation Maiden and MK7, and in the second I play MH4U and smash. All the game seem good with the stream. I'm using OBS to record them.

 
  • Like
Reactions: NekoMichi and astronautlevel
NekoMichi said:
Which CFW are you using as base? I'm currently using AuReiNAND.

The spec sheet for the router I'm about to buy says it supports up to 433mbps via wireless, but only 100mbps over Ethernet. That can't be right, can it?
Click to expand...
Realistically you are never going to see 433mbps speeds over wifi, there's too much overhead. You may get 100mbps out of it though if you're lucky.
It seems unlikely that it wouldn't support 1gbit ethernet, most things do these days. If it really doesn't support gbit ethernet you should look for a router that does. It shouldn't cost any more.
 
  • Like
Reactions: NekoMichi
The Real Jdbye said:
Realistically you are never going to see 433mbps speeds over wifi, there's too much overhead. You may get 100mbps out of it though if you're lucky.
It seems unlikely that it wouldn't support 1gbit ethernet, most things do these days. If it really doesn't support gbit ethernet you should look for a router that does. It shouldn't cost any more.
Click to expand...
The sheet says it has 10/100mbps Ethernet, which I think means that the mode switches between 10 and 100mbps depending on the device on the other end, right?

I've found 2 models, both do simultaneous 2.5/5GHz bands. The only difference is that one has 10/100mbps Ethernet while the other has 10/100/1000mbps Ethernet. There is a bit of a price difference.

Our Internet service is only about 2-3mbps, so upgrading the router isn't going to improve Internet speeds. The main aim is to improve device-to-device communications within our house (we use AirPlay a lot), which one of the two routers would you recommend?
 
Last edited by NekoMichi,
NekoMichi said:
The sheet says it has 10/100mbps Ethernet, which I think means that the mode switches between 10 and 100mbps depending on the device on the other end, right?
Click to expand...
The norm these days is 10/100/1000. Nothing ever uses 10mbps (though it's still supported), almost everything uses 1000mbps.
 
  • Like
Reactions: NekoMichi
Just a quick update, switching the PC from Wi-Fi to Ethernet seems to improve the connection stability. Using Zelda MM3D as a test, I'm getting around 20-30FPS during gameplay and 30+ FPS during title and menu screens. The most significant improvement seems to be the frame rate consistency, using a wired connection means less drops in frame rate mid-recording and fewer instances where the stream freezes on a single frame.
 
I just started my N3DS (SysNAND 9.2 / EmuNAND 10.7.0) and started NTR Debugger..
Then on my PC i just started my NTR Debugger and typed in connect('192.166.122.41' 8000)
Then my NTR Debugger just freezes and gives an Error
 
Phil5004 said:
I just started my N3DS (SysNAND 9.2 / EmuNAND 10.7.0) and started NTR Debugger..
Then on my PC i just started my NTR Debugger and typed in connect('192.166.122.41' 8000)
Then my NTR Debugger just freezes and gives an Error
Click to expand...
Are you sure the IP address begins with 192.166 and not 192.168?
 
Phil5004 said:
Whoops.. Jep.. 168 is right
Click to expand...
It sounds like NTR is working normally on the 3DS and the debugger is correctly installed on the PC, the only issue is the PC and 3DS aren't communicating with each other. Try these:

- Make sure the 3DS is connected to the same Wi-Fi network as your PC. (If you have multiple Wi-Fi networks in the area, make sure your 3DS is connected to the correct one and not to any other networks, if possible, delete any other networks from the 3DS settings and leave only the network that your PC is connected to)
- Remove any proxies under the 3DS wireless settings.
- Make sure that communications through port 8000 is allowed on the Windows Firewall.
 
NekoMichi said:
It sounds like NTR is working normally on the 3DS and the debugger is correctly installed on the PC, the only issue is the PC and 3DS aren't communicating with each other. Try these:

- Make sure the 3DS is connected to the same Wi-Fi network as your PC. (If you have multiple Wi-Fi networks in the area, make sure your 3DS is connected to the correct one and not to any other networks, if possible, delete any other networks from the 3DS settings and leave only the network that your PC is connected to)
- Remove any proxies under the 3DS wireless settings.
- Make sure that communications through port 8000 is allowed on the Windows Firewall.
Click to expand...
-Yes
-Yes
-Yes
 
Yes , everything is right...
I'll send the Error here...
> connect('102.168.122.41', 8000)
Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat 102.168.122.41:8000
bei System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
bei ntrclient.NtrClient.connectToServer()
bei ntrclient.ScriptHelper.connect(String host, Int32 port)
bei Microsoft.Scripting.Interpreter.ActionCallInstruction`3.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.LightLambda.Run5[T0,T1,T2,T3,T4,TRet](T0 arg0, T1 arg1, T2 arg2, T3 arg3, T4 arg4)
bei System.Dynamic.UpdateDelegates.UpdateAndExecute4[T0,T1,T2,T3,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2, T3 arg3)
bei Microsoft.Scripting.Interpreter.DynamicInstruction`5.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.LightLambda.Run2[T0,T1,TRet](T0 arg0, T1 arg1)
bei IronPython.Compiler.PythonScriptCode.RunWorker(CodeContext ctx)
bei Microsoft.Scripting.Hosting.ScriptSource.Execute(ScriptScope scope)
bei ntrclient.CmdWindow.runCmd(String cmd)
> connect('102.168.122.41', 8000)
Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat 102.168.122.41:8000
bei System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
bei ntrclient.NtrClient.connectToServer()
bei ntrclient.ScriptHelper.connect(String host, Int32 port)
bei Microsoft.Scripting.Interpreter.ActionCallInstruction`3.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.LightLambda.Run5[T0,T1,T2,T3,T4,TRet](T0 arg0, T1 arg1, T2 arg2, T3 arg3, T4 arg4)
bei System.Dynamic.UpdateDelegates.UpdateAndExecute4[T0,T1,T2,T3,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2, T3 arg3)
bei Microsoft.Scripting.Interpreter.DynamicInstruction`5.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.LightLambda.Run2[T0,T1,TRet](T0 arg0, T1 arg1)
bei IronPython.Compiler.PythonScriptCode.RunWorker(CodeContext ctx)
bei Microsoft.Scripting.Hosting.ScriptSource.Execute(ScriptScope scope)
bei ntrclient.CmdWindow.runCmd(String cmd)
 
Phil5004 said:
Yes , everything is right...
I'll send the Error here...
> connect('102.168.122.41', 8000)
Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat 102.168.122.41:8000
bei System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
bei ntrclient.NtrClient.connectToServer()
bei ntrclient.ScriptHelper.connect(String host, Int32 port)
bei Microsoft.Scripting.Interpreter.ActionCallInstruction`3.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.LightLambda.Run5[T0,T1,T2,T3,T4,TRet](T0 arg0, T1 arg1, T2 arg2, T3 arg3, T4 arg4)
bei System.Dynamic.UpdateDelegates.UpdateAndExecute4[T0,T1,T2,T3,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2, T3 arg3)
bei Microsoft.Scripting.Interpreter.DynamicInstruction`5.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.LightLambda.Run2[T0,T1,TRet](T0 arg0, T1 arg1)
bei IronPython.Compiler.PythonScriptCode.RunWorker(CodeContext ctx)
bei Microsoft.Scripting.Hosting.ScriptSource.Execute(ScriptScope scope)
bei ntrclient.CmdWindow.runCmd(String cmd)
> connect('102.168.122.41', 8000)
Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat 102.168.122.41:8000
bei System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
bei ntrclient.NtrClient.connectToServer()
bei ntrclient.ScriptHelper.connect(String host, Int32 port)
bei Microsoft.Scripting.Interpreter.ActionCallInstruction`3.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.LightLambda.Run5[T0,T1,T2,T3,T4,TRet](T0 arg0, T1 arg1, T2 arg2, T3 arg3, T4 arg4)
bei System.Dynamic.UpdateDelegates.UpdateAndExecute4[T0,T1,T2,T3,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2, T3 arg3)
bei Microsoft.Scripting.Interpreter.DynamicInstruction`5.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
bei Microsoft.Scripting.Interpreter.LightLambda.Run2[T0,T1,TRet](T0 arg0, T1 arg1)
bei IronPython.Compiler.PythonScriptCode.RunWorker(CodeContext ctx)
bei Microsoft.Scripting.Hosting.ScriptSource.Execute(ScriptScope scope)
bei ntrclient.CmdWindow.runCmd(String cmd)
Click to expand...
It shows 102.168 instead of 192.168, but I think that might just be a typo. Do you know if the router has security settings that prevent device-to-device communications? Have you tried connecting using a different PC?

One other factor I can think of is that maybe your keyboard's been configured to use non-standard quote or commas. Try copying and pasting this command directly:

connect('192.168.122.41', 8000)
 
Last edited by NekoMichi,

Site & Scene News

Go to forum More news

Popular threads in this forum

Why did the price of 3ds shoot up ?

Hacking Homebrew Project  BlazerTube - a YouTube 3DS revival using the REAL app!

[WIP] SMW 3DS Port - Early Playable Demo by ZalgonEn

Problems getting Homebrew to appear outside of the Homebrew Launcher (homebrew won't appear on the HOME menu)

Homebrew app Emulator  [Release] 3DS-CLI - Run a real RISC-V Linux environment on the Nintendo 3DS

Website for finding alternative games for 3DS

Homebrew  [Progress update] LCE Minecraft 3ds

Gaming  any good rpgs on 3ds?