Yes, as long as you port forward. Howerer, considering that they will be on two different networks, streaming performance could be poor.@RattletraPM , Sooo... It works even though my PC doesn't have Wireless Internet compatibility?
Yes, as long as you port forward. Howerer, considering that they will be on two different networks, streaming performance could be poor.@RattletraPM , Sooo... It works even though my PC doesn't have Wireless Internet compatibility?
The logfile stops right after it tries to init remoteplay (hotkeys don't work because they will be available for use right after the stream starts). You might want to try to adjust WaitRemoteplayInit to a different value (lower=snickerstream will wait less before initing remoteplay, higher=the opposite).
I have no suggestion for Snickerstream itself but you can use the OG NTRViewer as a troubleshooting threshold to see if the issue is on your end, or the program. If you can connect with NTRViewer than it's a problem with this program, if you can't it's more than likely your network setup.Unfortunately your advice didn't change anything. I tried setting it up a few steps to a limit of 30000 and also the opposite few steps down to 10. I guess the value is in ms, atleast i waited for that long after testing 30000 ^^
Any other recommendations what I can try to get it working or atleast throwing an error so I know whats the problem since the logfile looks like the last one (no errors at all). 3DS and PC are connected to the same network, ntr-cfw is running and I used the correct IP.
I hope someone has an idea.
Unfortunately your advice didn't change anything. I tried setting it up a few steps to a limit of 30000 and also the opposite few steps down to 10. I guess the value is in ms, atleast i waited for that long after testing 30000 ^^
Any other recommendations what I can try to get it working or atleast throwing an error so I know whats the problem since the logfile looks like the last one (no errors at all). 3DS and PC are connected to the same network, ntr-cfw is running and I used the correct IP.
I hope someone has an idea.
He said NTRViewer worked for him but the log he's getting is really strange. It cuts off right before the TCP packet for Remoteplay gets even sent (the program should log whether it has been sent properly or not) and even if it didn't, he should be getting a bunch of UDPRecv errors if something went wrong. This makes me think that it could be a firewall issue, as no packet - TCP or UDP - ever gets sent or recieved.I have no suggestion for Snickerstream itself but you can use the OG NTRViewer as a troubleshooting threshold to see if the issue is on your end, or the program. If you can connect with NTRViewer than it's a problem with this program, if you can't it's more than likely your network setup.
I have no suggestion for Snickerstream itself but you can use the OG NTRViewer as a troubleshooting threshold to see if the issue is on your end, or the program. If you can connect with NTRViewer than it's a problem with this program, if you can't it's more than likely your network setup.
He said NTRViewer worked for him but the log he's getting is really strange. It cuts off right before the TCP packet for Remoteplay gets even sent (the program should log whether it has been sent properly or not) and even if it didn't, he should be getting a bunch of UDPRecv errors if something went wrong. This makes me think that it could be a firewall issue, as no packet - TCP or UDP - ever gets sent or recieved.
So @Cyclon - please try to temporarily disable the firewalls on your system (and possibly on your router too, if it has an integrated one) and see if it works.
No problem, I hope you enjoy my streaming tool!
I really have to thank you both! Your recommendations and tipps made me look twice in my firewall rules, where the problem actually was. It's really embarrassing
Again thanks a lot for your help! Now I can enjoy playing even more with Snickerstream
TCPConnect error 10060 means that the 3DS did not respond after the client tried to connect to it. Double check your firewall/antiviruses and check that NTR is properly running.Uh... I'm having issues. Here's my log. One thing I've noticed is that my computer's IP displays as 0.0.0.0
EDIT - I tried manually fixing my computer's IP and got the same error. It sucks because I want to stream my USUM wedlocke.
EDIT 2 - Just thought I'd let you know that I get the same errors with kit-kat and NTRViewer
----------------------------------------------------------------------------------
it hac, it bric, but most importantly, it S N I C C
----------------------------------------------------------------------------------
VERSION : v0.85b
LOGLEVEL: 3
----------------------------------------------------------------------------------
[16:36] Logging started.
[16:36] WARNING: The loglevel is now set to 3. This will produce GIANT logfiles.
[16:36] You should set your loglevel to something else unless you're troubleshooting some issues!
[16:36] CPU: Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz@2667MHz
[16:36] GPU: ATI Radeon HD 4300/4500 Series
[16:36] PC IP address: 0.0.0.0
[16:36] 3DS IP address: 192.168.1.98
[16:36] Priority: 1
[16:36] Priority factor: 10
[16:36] Image quaility: 40
[16:36] QoS: 34
[16:36] Interpolation mode: 0
[16:36] Screen layout: 0
[16:36] Using Direct2D: True
[16:36] -NOTE- The IP addresses should be internal. If you set them to public DO NOT share this log online!
[16:36] Starting remoteplay on 3DS.
[16:36] TCPConnect error, @error=10060.
[16:36] Remoteplay init failed, could not connect.
No luck. There's no changes on the 3ds's screen and I disabled windows firewall and my antivirus for that program. I'm running NTR 3.6. IDK if it's something with my computer since no other computers on my network will show up but yeah.TCPConnect error 10060 means that the 3DS did not respond after the client tried to connect to it. Double check your firewall/antiviruses and check that NTR is properly running.
If you get the same errors with NTRViewer and kit-kat then it's not an issue with Snickerstream itself, so it must be something with your connection or router. By the way, forgot ti mention: it's OK to have 0.0.0.0 as the PC's IP - it means that Snickerstream will bind the UDP listening port to all available interfaces and IPs.No luck. There's no changes on the 3ds's screen and I disabled windows firewall and my antivirus for that program. I'm running NTR 3.6. IDK if it's something with my computer since no other computers on my network will show up but yeah.
Yeah, I told him that because I thought that his 3DS was just slow to reply to the TCP packet - but his issue was actually firewall related. I suggest you check your firewall/s (both on your PC and router) and add Snickerstream to the exclusion list in your antivirus, sadly some AVs see AutoIt programs as malware even if they're completely harmless.Ive been getting blackscreen on snickerstream, even though when pressing connect my 3ds flickers, i see you responded to someone with the same issue, to change the WaitRemoteplayInit, but nothing is really working for me, snickerstream still blackscreens. Any idea what could be an issue? I mean kit kat worked fine when i tried that, a while ago, but snickerstream is just being really stubborn lol
Try doing the same after opening the game (load a save, go back to the home menu and wait for your 3DS to reconnect,then send the NFC patch). If it doesn't work, delete NFCLastAnswer from the INI and try again.I was trying to record some Pokemon Ultra Sun but i get a blackscreen, after the game launch of course the home menu and all work perfectly. Of course before launching the game i have click on the NFC patch.
Well , it seems like you were right , i tried today and its streaming perfectly thanks youYour log looks fine but it seems that your connection gets dropped a few times here and there. Are you sure it's not a connection issue? (Remember that screen streaming uses lots of bandwidth and that if you're far away from your router then you'll get poor performance)
Try doing the same after opening the game (load a save, go back to the home menu and wait for your 3DS to reconnect,then send the NFC patch). If it doesn't work, delete NFCLastAnswer from the INI and try again.
My anti-virus doesnt see snickerstream as a virus, so thats not a factor, ive already allowed it through the firewall as well, how do i check my routers firewall? Im not entirely sure im able to do that or not.Yeah, I told him that because I thought that his 3DS was just slow to reply to the TCP packet - but his issue was actually firewall related. I suggest you check your firewall/s (both on your PC and router) and add Snickerstream to the exclusion list in your antivirus, sadly some AVs see AutoIt programs as malware even if they're completely harmless.
Get in your router's control panel (usually 192.168.1.1, check via ipconfig - it will be your gateway IP) and check if there's a firewall option there (some routers have built in firewalls). If there isn't or it still doesn't work, try port forwarding even if it shouldn't be needed.My anti-virus doesnt see snickerstream as a virus, so thats not a factor, ive already allowed it through the firewall as well, how do i check my routers firewall? Im not entirely sure im able to do that or not.
yeah theres no firewall option in my routers settings, what do i port forward? And how.Get in your router's control panel (usually 192.168.1.1, check via ipconfig - it will be your gateway IP) and check if there's a firewall option there (some routers have built in firewalls). If there isn't or it still doesn't work, try port forwarding even if it shouldn't be needed.