SendQuickly not working

[Bug5532]

I've been testing out the demo scenes but I cant seem to get SendQuickly to work. The debug code at the top say TCP+UDP but when I try example 3 I dont see the drag movement only the final placement.
Any idea what i'm doing wrong?

[Bug5532]

Ok, so I set the UDP port numbers to be the same at that seems to have made it almost start working... now when I move the boxes on anything but the host, they move on the host, but not on the other devices....
How am I meant to set up the udp port numbers?

[ArenMook]

What device are you hosting it on? Have you tried reversing the host, making it hosted on another device?

[Bug5532]

Sorry when I said host I meant server host.
So if I force all the UDP ports to be the same number then the server host receives UDP messages but the others dont. The others do send UDP messages though.
I think I must be setting it up wrong. is UDP meant to work when a device is hosting the server? or does it only work with a fixed server?

[ArenMook]

Yes, UDP works anywhere it's supported. 3G networks don't, for example. Current release (1.8.5) also doesn't handle multiple network interfaces properly -- something I addressed in 1.8.6 (which is currently in the Pro repository). However, since you are seeing TCP+UDP shown in the top left corner, it implies that UDP packets arrived successfully, so assuming you are on 1.8.5 and not on an earlier version, it should still work as expected.

I'll release 1.8.6 within a few days (likely this weekend), so maybe the changes there will help as well.

[Bug5532]

Yeah thats what I thought about the TCP+UDP in the top left, thats what confused me.

Just to add, I hosted a windows server with the .exe file and now UDP works fine between all devices. So it seems to be something to do with hosting the server on a device. Is that what the 1.8.6 update will address? (sorry I'm still very new to networking)

[ArenMook]

There will be a way to address it, but whether it will be auto-fixed or not remains to be seen.

Basically I noticed that in situations where there is more than one network interface on the same computer it would not be clear where the UDP traffic would be going. I only noticed it after I installed Hamachi for AoW3 -- Tools.localAddress was giving me 25.XX.XX.XX instead of 192.168.1.XX.

So now in 1.8.6 you can retrieve a list of your IPs (via Tools.localAddresses), a list of network interfaces (in case you want to give the user a choice), and you can explicitly specify which network interface you want to be using by setting the UDP's local address. Doing so fixed everything on my end and made it possible to get the current Windward prototype to work properly with multiple networks.