Hmm. It can take while for NTRViewer to show an image sometimes. Could you take a screenshot of both NTRViewer windows and Nitro Stream and also paste the log here?I restarted my PC and 3DS and I still get the same error as above. NTRViewer doesn't show anything.
This is great, thanks!
You can even change settings just by closing the viewer, change the settings and hit go again. No reboots. I think i wanna marry you.
So, about that marriage thing? You into pixelated toasters?Thanks for the feedback! Yeah I set a connected flag and skip the connection stage next time you press connect so all it does is relaunch NTRViewer with the new parameters. I found it worked pretty well.
Try forwarding the port. I know someone's gonna come along saying "HIPPITY HURPITY DER DUN NEED DAT ON LAN", but some routers fight with local reverse connections. It's worth a shot. Also, are you using some kind of AV that comes with a firewall?View attachment 57864
"
Connecting...
ERR: No connection could be made because the target machine actively refused it 192.168.2.9:8000
Connecting...
OK: Creating new connection
OK: Disconnected
ERR: No connection could be made because the target machine actively refused it 192.168.2.9:8000
Connecting...
OK: Disconnected
OK: Creating new connection
ERR: No connection could be made because the target machine actively refused it 192.168.2.9:8000
Connecting...
OK: Disconnected
OK: Creating new connection
OK: Connected
OK: Remoteplay initiated. This client will disconnect in 10 seconds.
ERR: Unable to read data from the transport connection: A blocking operation was interrupted by a call to WSACancelBlockingCall.
OK: Server disconnected
OK: Disconnected
OK: Disconnected
"
It was refusing to connect because I forgot to enable NTR. I'm gonna try port forwarding now.Port forwarding seems like it might solve the issue, I've had routers be a problem just because they can. Although your device was refusing the connection at one point too, I would suggest you reboot your console and double check you have enabled debugging on NTR CFW.
n3DS onlyStill N3DS or can this be worked on o3ds too? :3 Hoping hoping hoping......
Nooooooo.... damnit.... understandable but was still hoping. Oh well! Thanks for the quick response!n3DS only
I definitely only have one open and I had it open for 1 hour and 19 minutes.Hmm, I'm not sure what else to suggest. All exceptions get routed through the log so any errors would show up there. I get the same error even when it connects successfully some time as it's just how Ntr handles the disconnection. How long have you tried leaving the window open for & do you definitely only have one instance of NTRViewer open?