I’m experimenting with DirectPlay, yes yes yes, I know its deprecated, but FS2002/4 is not and you need it to talk to those animals.
The reason I’m playing is that I want to see if I can integrate FS and Need for speed or any other such like game, so I need those gateways… I’m just having fun outside the box, not flying straight and level so to speak.
Here’s something I can’t understand and maybe a Guru out there can help me, my software on the 2004 GUID and Port 23456 will happily connect with servers out there, and I can check out the planes, inject some and do other such wonderful things.
But this same software is completely ignored when I tell it to be a 2002 client and connect as such, using the 2002 GUID and Port 47624.
Absolutely nothing happens, its stone dead, and what is even stranger is that if I start my app up as a server… it will actually coexist with another server… the ports don’t even clash… however on 2004 settings the servers will complain and say that someone else is already playing in their space… which is what one would expect.
Now the other thing is that I notice that 2004 servers control the port themselves, whereas 2002 servers don’t, the 47624 port is actually owned by the Dplayer server.
Which means that somehow the server app is working through Dplayer srvr on 2002… and I guess that means I have to somehow tell dplayer server to talk to my app… or something.
There is something not the same between 2002 and 2004 dplay… as I said this software works great on 2004, but not 2002… in client and server mode???
Can you solve the riddle… probably have to be a wise old guy
For a start, if the port belongs to DplayServer on 2002 how on earth don’t anything connect to your server app, in 2004, the port belongs to the app server that you made????
Something is different… can u see it.
Its almost like in 2002 the client and server peer basically register with Dplay and it does the work… where in 2004 Dplay is just a lib.
… guesses are good as well because boy does the Microsoft documentation suck…
The reason I’m playing is that I want to see if I can integrate FS and Need for speed or any other such like game, so I need those gateways… I’m just having fun outside the box, not flying straight and level so to speak.
Here’s something I can’t understand and maybe a Guru out there can help me, my software on the 2004 GUID and Port 23456 will happily connect with servers out there, and I can check out the planes, inject some and do other such wonderful things.
But this same software is completely ignored when I tell it to be a 2002 client and connect as such, using the 2002 GUID and Port 47624.
Absolutely nothing happens, its stone dead, and what is even stranger is that if I start my app up as a server… it will actually coexist with another server… the ports don’t even clash… however on 2004 settings the servers will complain and say that someone else is already playing in their space… which is what one would expect.
Now the other thing is that I notice that 2004 servers control the port themselves, whereas 2002 servers don’t, the 47624 port is actually owned by the Dplayer server.
Which means that somehow the server app is working through Dplayer srvr on 2002… and I guess that means I have to somehow tell dplayer server to talk to my app… or something.
There is something not the same between 2002 and 2004 dplay… as I said this software works great on 2004, but not 2002… in client and server mode???
Can you solve the riddle… probably have to be a wise old guy
For a start, if the port belongs to DplayServer on 2002 how on earth don’t anything connect to your server app, in 2004, the port belongs to the app server that you made????
Something is different… can u see it.
Its almost like in 2002 the client and server peer basically register with Dplay and it does the work… where in 2004 Dplay is just a lib.
… guesses are good as well because boy does the Microsoft documentation suck…