Every single update made makes 0 changes to NTRViewer, if it cant connect, then I cant help.
Okay, well thanks anyway. It still a great tool, so keep up the good work.
I hope I figure out the problem soon.
--------------------- MERGED ---------------------------
Sidenote: I noticed that on startup it autodetects an IP address, but since that not my 3DS I have to change it back.
I checked and for some reason the IP it autodetects is my Wii U's IP.
I am able to connect and the application works much better than Nitro Stream! Only problem I'm facing is a problem I also had with Nitro Stream which is that my screen size is extremely small compared to yours (I'm assuming this is because you are using the N3DS XL while I'm using the N3DS). In any case, is there a possible method to expand screen size outside of what I'm already using (OBS)?
[v1.4.6] Socket Disposed Bug SQUASHED!
https://github.com/initPRAGMA/kit-kat/releases/tag/1.4.6
This squashes the annoying Socket.Disposed error you get when you use both NTRViewer AND IR at the same time.
The error was caused by overlapping the same socket with different functions, Input Redirector was mistakenly using the same socket as NTRViewer's socket.
I simply made it use a brand new socket, and now its fixed.
--------------------- MERGED ---------------------------
Does it keep changing it to the WiiU's IP on launch even when you change it to the 3DS ip?
--------------------- MERGED ---------------------------
If you want to use it, use it combined with a Connectify setup. You can read how here: https://gbatemp.net/threads/tutoria...without-a-capture-card-ntr-cfw-method.423445/
(Go to the Windows Section, and then the Part 2).
https://github.com/initPRAGMA/kit-kat/releases/tag/1.4.6
This squashes the annoying Socket.Disposed error you get when you use both NTRViewer AND IR at the same time.
The error was caused by overlapping the same socket with different functions, Input Redirector was mistakenly using the same socket as NTRViewer's socket.
I simply made it use a brand new socket, and now its fixed.
--------------------- MERGED ---------------------------
Yeah thats the only bad thing about the Auto-Detector, if you have multiple 3DS's or Nintendo Products in general it will detect them, nothing I can really do about it either.
Does it keep changing it to the WiiU's IP on launch even when you change it to the 3DS ip?
--------------------- MERGED ---------------------------
Its not coming back - It just causes issues.
If you want to use it, use it combined with a Connectify setup. You can read how here: https://gbatemp.net/threads/tutoria...without-a-capture-card-ntr-cfw-method.423445/
(Go to the Windows Section, and then the Part 2).
In settings, theres an option for Screen Scale, simply hit that up to whatever you want.
--------------------- MERGED ---------------------------
Ok, I told the IP Detector to only try fetch the IP if there wasnt an IP set up... Ill review the code and try fix that.
Though I do need someone to help test, I only have 1 nintendo device, so I cant test this bug. Can you please add my discord: PRAGMA#2141? (It might fail to add, if it does, tell me yours ill add you)
p.s if you dont have discord please get it :3
[v1.4.7] IP-Detector Slight Bug Fix
https://github.com/initPRAGMA/kit-kat/releases/tag/1.4.7
When you have multiple Nintendo Products, it sometimes grabs the IP of the device you dont want, and when you change the IP to the one for the device your using, re-opening kit-kat would revert it back to the unwanted device's IP.
With this update thats fixed. Once you change the IP, It will be changed for good and the Auto-IP-Detector wont do anything to the IP.
https://github.com/initPRAGMA/kit-kat/releases/tag/1.4.7
When you have multiple Nintendo Products, it sometimes grabs the IP of the device you dont want, and when you change the IP to the one for the device your using, re-opening kit-kat would revert it back to the unwanted device's IP.
With this update thats fixed. Once you change the IP, It will be changed for good and the Auto-IP-Detector wont do anything to the IP.
Watch the tutorials.
--------------------- MERGED ---------------------------
Probably not since I dont own any one of those.
This application works great! I need to bump this so more people can see! Although I get 15-35 FPS. I have terrible internet.
You should be more concerned about your router speed rather than the internet speed itself.
Similar threads
-
- Article
Rotflmao 
