Multiplayer lan problems

heretickedoff

Please help I am having problems with multiplayer in jheretic, when I host a new multiplayer game, as soon as one of my other two computers tries to join that game it jheretic crashes on that computer. I am getting this error message:

0 : Doomsday 1/16 10900 jheretic 1.4.8 :13209
E1M5 (HERETIC.WAD:ea102d) p:0ms Multiplayer Host
heretic-ext skill5 dm nmonst
Players: Player

N_SendDataBufferReliably: Tried to send 3 bytes (max pkt size 2).


What do I do?

skyjake

That is unfortunately a known bug in the Beta 6.x releases. Multiplayer is not working in them.

You can try out the newer unstable builds, which have several multiplayer related bugfixes (although they are incompatible with the older releases; everyone in the game needs to run the same version), or you can wait for the next stable release (1.9.7) which will have working multiplayer.

You can access the unstable releases through the Builds RSS feed. The current build is: http://code.iki.fi/builds/build185

heretickedoff

Thank you for the response, I downloaded the build you linked me to for both my pcs and my mac and now there is no way to host a game, However i noticed that in singleplayer there is a new option fate's something and it says that it's not recommended for singleplayer not sure what thats about but it was fun!

Well, any other suggestions?

PostFatal

I also got the 185 build hoping to show a friend some hexen co-op but found no option to host. Am I missing something obvious?

KuriKai

Just run doomsday from the command line
or run a dedicated server on your computer and join it through doomsday's gui

http://www.dengine.net/dew/index.php?ti ... er_options

skyjake

heretickedoff wrote:

I downloaded the build you linked me to for both my pcs and my mac and now there is no way to host a game

Sorry, forgot to mention that the GUI for hosting games is currently disabled in the unstable builds. You'll need to run a dedicated server instead, and as KuriKai says that needs to happen via the command line. At least on the Mac the dedicated server should be working; I've been developing with it on my own Mac.

You could try this in the Mac Terminal (in /Applications/Doomsday Engine.app/Contents):

Doomsday.app/Contents/MacOS/Doomsday -appdir . -game jHeretic.bundle -iwad /your/path/to/heretic.wad -basedir Doomsday.app/Contents/Resources -dedicated -server -file ../doomsday.pk3 ../jheretic.pk3

The GUI for hosting games will be restored before the stable release of 1.9.7 is made.

oremornhoj

skyjake wrote:

You could try this in the Mac Terminal (in /Applications/Doomsday Engine.app/Contents):

Doomsday.app/Contents/MacOS/Doomsday -appdir . -game jHeretic.bundle -iwad /your/path/to/heretic.wad -basedir Doomsday.app/Contents/Resources -dedicated -server -file ../doomsday.pk3 ../jheretic.pk3

The above command did not work for me. Did you test it before posting?
It goes in to the dedicated server console and almost immediately exits so that it's hard to see the error reports. I had to take a screen shot quickly enough to find out that it was unable to find the pk3 files and after some trial & error I found this to work:

$ pwd
/Applications/Doomsday Engine.app/Contents
$ Doomsday.app/Contents/MacOS/Doomsday -appdir . -game jHeretic.bundle -iwad /Users/jesus/Games/DooM/Heretic.wad -basedir Doomsday.app/Contents/Resources -dedicated -server -file ../doomsday.pk3 ./jHeretic.bundle/Contents/Resources/jHeretic.pk3

Btw, how to make the application print out the errors to stdout or somewhere where I can actually see them?


And how to run this in Windows?

skyjake

oremornhoj wrote:

The above command did not work for me. Did you test it before posting?
It goes in to the dedicated server console and almost immediately exits so that it's hard to see the error reports. I had to take a screen shot quickly enough to find out that it was unable to find the pk3 files and after some trial & error I found this to work:

Ah yes, I have my PK3s in a different folder (the build directory) -- when running the installed application they are indeed inside the bundles.

The console output should be in a file named doomsday.out in the directory you started the server from.

About Windows: Doomsday's window management on Windows currently does not support running in the text console mode -- thus the dedicated server is not working at the moment.

oremornhoj

Thanks for the reply.

skyjake wrote:

About Windows: Doomsday's window management on Windows currently does not support running in the text console mode -- thus the dedicated server is not working at the moment.

How about Linux?

What's the best version of Doomsday that supports network play without so much hassle?
Pre-beta 6.x releases?

DaniJ

skyjake wrote:

About Windows: Doomsday's window management on Windows currently does not support running in the text console mode -- thus the dedicated server is not working at the moment.

I'm currently fixing up both the dedicated server and novideo modes on Windows, in the ringzero branch (will commit later on today most likely). Once the UI work in branch ringzero has been completed we can then start merging it back to the master.

oremornhoj

DaniJ wrote:

skyjake wrote:

About Windows: Doomsday's window management on Windows currently does not support running in the text console mode -- thus the dedicated server is not working at the moment.

I'm currently fixing up both the dedicated server and novideo modes on Windows, in the ringzero branch (will commit later on today most likely). Once the UI work in branch ringzero has been completed we can then start merging it back to the master.

When can we expect this? This week, next week?

Meanwhile I will use Skulltag. The network code feels really smooth.

DaniJ

I'm currently massaging the changes so that the patch can be cherry picked and merged into the master (thus it will appear in the next automated build).

DaniJ

Both dedicated and novideo modes are now working again in the ringzero branch, on Windows.

Relevant commits:
bef63926d784eccda574c9a8a5fc81f313216488
8f1d7bd62e2d85184009b14f66c42de00b161448
704f0591bcda1410525c28e4738fb3e5993e6a9b