A
And Wan
A very old game Theme Hospital luckily has DirectPlay IPX for multiplayer
support.
The problem is, it's very very slow in a high-ping network (ie. VPN via
Hamachi for across the internet). I mean, it causes all clients games to be
very very slow, it's unplayable. We can't scroll the screen without having
to wait 10 times longer than normal for the screen to scroll.
Is there anyway to make a wrapper for DirectPlay IPX so that it works across
DirectPlay TCP/IP? If not, could write a fake service which would speed up
the game clients so they don't have to wait? I believe all clients is
waiting for constant updates from each other, possibly an acknowledgement.
If was in a 300 ping network, this would be too slow.
Maybe use WireShark to sniff the IPX packets, to see what acknowledgements
look like. Then create a fake service for all clients that would send reply
acknowledges?
support.
The problem is, it's very very slow in a high-ping network (ie. VPN via
Hamachi for across the internet). I mean, it causes all clients games to be
very very slow, it's unplayable. We can't scroll the screen without having
to wait 10 times longer than normal for the screen to scroll.
Is there anyway to make a wrapper for DirectPlay IPX so that it works across
DirectPlay TCP/IP? If not, could write a fake service which would speed up
the game clients so they don't have to wait? I believe all clients is
waiting for constant updates from each other, possibly an acknowledgement.
If was in a 300 ping network, this would be too slow.
Maybe use WireShark to sniff the IPX packets, to see what acknowledgements
look like. Then create a fake service for all clients that would send reply
acknowledges?