Jump to content

formlesstree4

Member
  • Posts

    303
  • Joined

  • Last visited

Everything posted by formlesstree4

  1. I honestly have no idea because I don't have a 3DS to test things out on.
  2. I've re-looked over the source code that takes that into account, nothing stands out. I'll rewrite it soon possibly if I get time.
  3. Do not put your local IP in unless you are only distributing to yourself. Then it doesn't matter. Use the IP address from checkmyip.com.
  4. A: No, the program uses a DNS spoofer to override the DS's requests for the Nintendo server. Unless you can write this program as a web-server (Such like Willaien did), then you will not be able to turn your PC off and continue to distribute.
  5. Leave your PC on, that's the only way to do it. Or find a dedicated windows server that allows ports to be forwarded and will run a windows executable.
  6. It's something I can attempt doing in the program, but it's insanely hard for some reason, at least for me. I can't find any samples for easily doing UPnP via code.
  7. Check with your router and make sure all ports are assigned correctly, otherwise no program will be able to work with it (Unless UPnP were to be successfully configured).
  8. Do you have a router Yoshi? I'm suggesting that, if you do have a router, the assigned IP address from your router could've changed, which would mess up the port forwarding and leaving it to not work. Also, attempting a connection via web browser fails while ShinyGTS should output some data. This adds to my suggestion that your router (if you have one) changed the assigned IP to your PC.
  9. It sounds like a routing issue, that's all I can think of. Make sure nothing has changed on your router, or your assigned IP address from your router.
  10. I've only seen it be off by one in either direction (one above or one below), but that was extremely rare and usually the program used to generate the Pokemon file was at fault. It should match like...99% of the time if the program used (such as PokeGen) is good.
  11. I'll have to look into the source code and see where things could mess up... Same issue as Sabeta; check back later.
  12. The 192.168.1.12 is your assigned IP from the Router to your DS. The only thing I can think of now is that it might be an issue with your router or DS, or some combination of the two. I'm not sure why it's messing up...so when you -try- and send it...hmm...wait...are you using the latest ShinyGTS/DTS? I think there was a time where I disabled it.
  13. So, you've set it in receive mode I assume. Not to mention that you're probably using a local IP instead of a public IP address. Can you show me the setup you have on ShinyGTS and list your WiFi settings on your DS?
  14. How many times did your friend try? This, unfortunately, isn't a perfect art. Tell him to keep trying; your screenshot proves that the server -does- work and that you have setup everything just fine (since all IP's are external and not internal), but now all you need to do is keep trying. I'm not sure what else to tell you sadly; I've had this issue several times on my own PC and the only advice I have is to keep trying. It will work eventually.
  15. Jocelyn, if you have some sort of instant messenger, I'll be more than happy to work with you personally to get a Mono build working; I've had interest myself in getting it to work.
  16. The error appears to be the NotifyIcon I use in ShinyGTS. There's nothing I can really do about that other than remove it...
  17. 1) I wrote ShinyGTS, I know exactly how it works and it's not very different. The fact that it is a different programming language makes little difference, just changes the syntax and toolset utilized (since, in the end, all code runs through some type of parser to become machine executed code, which is all the same). 2) If you put in the proper IP address instead of a Local IP, it will in fact work. You have a moderator and another programmer telling you that it does work. We're not saying we don't appreciate what you did, we're just saying there's no real reason for it. Also, the big red text isn't necessary. We do know what we're talking about. Any decent router would handle NAT transitions just fine (I've had a 4 year old router be able to do it and my newly upgraded one does it just fine as well).
  18. Nonsense; if you forward your ports properly, it should work fine. Heck, Shiny(G/D)TS works just as well through NAT without any additional programming because it relies on Port Fowarding. It's up to the server host to reroute properly (such as the IP being your outbound one and having ports fowarded). You just took out one piece of the equation with some automatic checking.
  19. Guys, try this IP for the DNS: 204.45.29.54
  20. So it didn't work with that? Try just sending zero bytes and see what happens.
  21. Something might be using 80. Everything looks fine, just double check that no applications are using Port 80 at the same time or could possibly be overriding ShinyGTS.
  22. Did you change your DNS IP in your DS Wifi settings?
  23. Heh, I didn't. I was just making sure the server was responding to Internet pings like it should.
  24. Please redirect all questions to the support thread.
×
×
  • Create New...