Duke nukem source port how to#
Duke nukem source port zip file#
Duke nukem source port driver#

Duke nukem source port driver#

The thing with the DOS duke nukem is that the COMMIT driver that was shipped with it controls ALL the underlying networking transport functions which includes player addresses. Even if the old lockstep code was still there, you'd still not be able to get them to network properly, because the actual game code is drastically different, and won't have the same deterministic outcome. You won't be able to get them to work together. It's using an incomplete Client/Server Authoritative networking model. The mainline EDuke32 networking code is drastically different, and isn't even deterministic lockstep anymore. Also, if this setup is true, I'm wondering how two 'clients' could connect to each other, unless all networking is passed through the game host's PC.ДЄlso, other than using IP addresses as parameters for clients, is the underlying network code the same as in the original Duke Nukem 3D when the game is in action or has that been modified? By this, I don't mean the protocol the code travels through the net over (UDP vs IPX), I mean the data format of the code itself.ДЄnd is there anything special I need to be aware of with regards to the networking functionality to Eduke32? Would all IP addresses here be on the UDP/IP protocol? Because that is faster for gaming than TCP/IP. Going by the Eduke32 multiplayer manual last edited almost 10 years ago, it states the host could start with the '-server' parameter and I think each client can start with the '-connect :yyyy' where xxx are digits to the IPv4 address and yyyy are digits to the port.

Duke nukem source port how to#

If I were to adopt Eduke32, I'm trying to figure out how to blend it in to my lobby system. Then again the original commit driver was meant to work for multiple games (including Shadow Warrior), so I would predict the data itself is dependent on what game is being played. With the sources to the Dos Duke Nukem Commit specification, I can only predict the network data to and from a player can be up to 2048 bytes in length but doesn't describe the data in detail. What I want to know is, would the underlying network code remain untouched? It would be so grand that you could backup the whole gaming experience on a CD-ROM or even a Zip drive (if you still have those) Then if your computer crashes, pop the media in and you're good to go. Like Eduke32, my driver is useless without valid Duke Nukem 3D components.Д«ecause Eduke32 is (for the most part) a modification of the presentation of Duke Nukem so that high graphics and more operating systems are supported, I think I could get a lobby consisting of some players on Eduke32 and some on DOS duke Nukem via my driver.

Duke nukem source port zip file#

The game data is illustrated in the README.TXT file contained in this zip file from 3D realms. In DOS duke Nukem 3D, the parameter to -net is a pointer to multiplayer game data which contains an interrupt address for the networking code. (I'm going to replace multiplayer clients with a web version in my driver suite.) But I did notice something interesting. And its suggesting anyone who wants multiplayer with an older Eduke32 can use Yang multiplayer client. I think if I could work my whole system a bit, I could make it where players that play Duke Nukem from Eduke32 can connect to those who use my driver to play Duke Nukem for DOS.