I was wondering could someone post some help on starting a LAN game across 2 - 4 computers? The latest build of Dukester X doesn't seem to work (just shows the list box of duke v1.999 commands when I try to host).
I am using this build:
JFDuke3D binaries 20050228 (zip package - net test update) - 726.28 kB
Win32 executables for JFDuke3D (zip package). Released 28th February 2005
and shareware duke from 3drealms.com (3dduke13.zip)
the machines are in the ip range of
192.168.1.100
192.168.1.101
192.168.1.102
192.168.1.103
I'm just looking for the command line for the host and then the command lines for the 2 -3 clients.
thanks! :D
paincakes at
releasenotes.html
missed that first time around
all good now!
CannibalBob at
Could you tell us how the LAN game went, was it laggy, did it go out of sync any time?
addfaz at
Re: Starting a LAN game via command line
paincakes said
The latest build of Dukester X doesn't seem to work (just shows the list box of duke v1.999 commands when I try to host).
Yeah, seems the -name command line argument is broken in the new JFDuke release. If its specified before /net it displays the list box. If its after, its ignored :(
DX always includes this command argument when launching the game. So the new JFDuke is effectively unsupported by DX now :cry:
JonoF at
Starting a LAN game via command line
Everything after the '-net' parameter is ignored by the game and is read by the network code, so yes, you have to put -name before the -net. I could have sworn I mentioned that in the release notes but on further review it looks like I hadn't made it clear enough.
Jonathon
paincakes at
CannibalBob: The LAN game de-synced, but my HOST pc could barely run duke3d (not to mention even Windows XP) so no conclusions can be drawn from this test. I also alt-tabbed out of the client and it de-synced shortly there after.
Jonathon: has anyone else mentioned a bug where changing an option within the actual duke3d program generates a duke3d.cfg that will not allow the game to play upon next loading? I made my duke3d.cfg read only to fix this. I have both .cfg files if you need to see what is changing.
BTW awesome job! 8)
paincakes at
Executions = 1
that string under [Misc] makes my duke no longer load and is generated upon exit in the duke3d.cfg
paincakes at
these strings all cause duke to no longer load and are added when duke3d.exe is executed:
Sounds like something may be seriously wrong with your Duke installation.
Nxskingdom at
Re: Starting a LAN game via command line
addfaz said
paincakes said
The latest build of Dukester X doesn't seem to work (just shows the list box of duke v1.999 commands when I try to host).
Yeah, seems the -name command line argument is broken in the new JFDuke release. If its specified before /net it displays the list box. If its after, its ignored :(
DX always includes this command argument when launching the game. So the new JFDuke is effectively unsupported by DX now :cry:
Hey addfaz, you aren't the only one that cannot play with -name command. Imagine that when you are playing with more than 4 players... phheee :)
TX at
Starting a LAN game via command line
I have confirmed that -name is entirely broken and have notified JonoF as such. The issue is that the actual command line parser was changed in the latest release to accept both parameters in the form of, say, duke3d -s3 -l1 and the more classic duke3d /s3 /l1. This is a problem because the player's name isn't set with -name in that function, but rather in the config file reading function. It will be fixed for the next release.
Nxskingdom at
TX said
I have confirmed that -name is entirely broken and have notified JonoF as such. The issue is that the actual command line parser was changed in the latest release to accept both parameters in the form of, say, duke3d -s3 -l1 and the more classic duke3d /s3 /l1. This is a problem because the player's name isn't set with -name in that function, but rather in the config file reading function. It will be fixed for the next release.
okay. thanks you :)
ProAsm at
Regarding the game not running if something is changed in the CFG file.
At some stage (not sure when) the game writes garbage to the [Misc] section and it would seem that that section can only be up to X bytes long and if it exceeds this length then the game will freeze at startup the moment Executions = goes above 99
You can try it by typing in a dummy line.
The normal [Misc] here is:
I have searched the code for this but cannot find anything so I wrote a line that locks the Executions = 99
paincakes at
Here is my duke3d.cfg. I configured the controls via setup.exe then ran the game and went back and cut out anything duke3d.exe parsed. I then made the .cfg read only and have no problems now.
I also tried LAN play on a more capable computer for about 5 minutes and had no desync. More testing will be conducted tonight when the "victim" shows up at my house :P