Author Topic: UDP Issues on some routers  (Read 2323 times)

Quan

  • Newbie
  • *
  • Thank You
  • -Given: 1
  • -Receive: 0
  • Posts: 21
    • View Profile
UDP Issues on some routers
« on: July 19, 2013, 06:08:59 PM »
I have run into issues using UDP and certain routers. Using the examples as a test I find that example 3 with sendquickly doesn't update the cubes positions until the mouse is released.

I have checked that Universal Plug & Play is enabled on both the router and PC and the program reports that UDP is enabled but nothing gets sent or received. If I set the UDP port then port map it on the router example 3 works fine.

The Two routers I know that are giving issues are:

Belkin F5D8236-4v1
TPLink TD-W8960N

As far as I can tell TCP isn't giving any of these issues.

Thanks

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: UDP Issues on some routers
« Reply #1 on: July 19, 2013, 06:24:22 PM »
What version of TNet are you using here?

Quan

  • Newbie
  • *
  • Thank You
  • -Given: 1
  • -Receive: 0
  • Posts: 21
    • View Profile
Re: UDP Issues on some routers
« Reply #2 on: July 19, 2013, 06:59:40 PM »
Latest from the asset store, 1.7.2c


ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: UDP Issues on some routers
« Reply #3 on: July 20, 2013, 03:50:56 AM »
If the program reports that UDP is enabled, then the initial UDP packet has arrived successfully, which begs the question of why don't others? I'm in Copenhagen right now but I'll see if I can reproduce it when I get back.

Quan

  • Newbie
  • *
  • Thank You
  • -Given: 1
  • -Receive: 0
  • Posts: 21
    • View Profile
Re: UDP Issues on some routers
« Reply #4 on: July 20, 2013, 06:45:54 PM »
No hurry, in fact its more a kick in the pants for me to stop being lazy using UDP and start using TCP with client prediction instead :)