DE Gray Screen When Joining Co-op Server
Hi all,
A friend and I are trying to play Ultimate Doom or Doom 2 on the public co-op server. Both he and I get a gray screen with the 'DE' logo once we are connected to the server (Screen shots attached). We can both get into the PvP servers just fine, as well as the Heretic Co-op server just fine. I noticed there's a warning when selecting the server (see screen shot). Also posted is my runtime log.
Also, this happens regardless of add-ons being enabled or not.
Screen Shots:
http://my.ilstu.edu/~tjtegme/error%201.png
http://my.ilstu.edu/~tjtegme/error%202.png
Link to runtime log:
http://my.ilstu.edu/~tjtegme/runtime.html
Any ideas?
Thank you!
A friend and I are trying to play Ultimate Doom or Doom 2 on the public co-op server. Both he and I get a gray screen with the 'DE' logo once we are connected to the server (Screen shots attached). We can both get into the PvP servers just fine, as well as the Heretic Co-op server just fine. I noticed there's a warning when selecting the server (see screen shot). Also posted is my runtime log.
Also, this happens regardless of add-ons being enabled or not.
Screen Shots:
http://my.ilstu.edu/~tjtegme/error%201.png
http://my.ilstu.edu/~tjtegme/error%202.png
Link to runtime log:
http://my.ilstu.edu/~tjtegme/runtime.html
Any ideas?
Thank you!
Comments
Where did yours come from?
For reference, Dday currently doesn't officially support the new version of Doom2.wad from the recently released Doom3 BFG Edition; the Doom2.wad in the BFG edition was altered especially for that release. Though support is planned for it in the near future.
There is only a gray screen with logo, but if I shoot, the shot heard.
Do you get a titlepic when you start Doom2?
Did you get your Iwads from the stand alone version of Doom2 on Steam?
The titlepic appears when I start the game.
It turns out the co-op server needs resetting due to a long known bug with end game finalies.
Obivously though, if your Iwad is different from the servers, you may still encounter errors at some point.
I just restarted the servers so they should no longer be stuck.
This is one of the issues I plan to address in the future when I return to the multiplayer functionality...
But... I get this grey DE screen when joining the co-op server in Ultimate Doom.
Before starting, I get an error message that while the server is d12fbc, I run db003a.
Now, this is kind of irritating, as there were a lot of different versions of Doom, up to 1.9 - but there is only one version of Ultimate Doom known to me. The CRC32 is BF0EAAC0, size is 12408292 and date is May 25, 1995.
Anybody got an explanation?
Server "Deng Team (Co-on; Unstable)" shows no warnings. It is currently at E2M8 and only shows the grey DE screen.
Like Tea Monster, I run build 679 on Windows 7 x64. However, I had the same issues with all earlier versions before.
Funnily enough, I have no problems connecting to "Deng Team (DM; Unstable)", that one works fine.
Currently the Ultimate Doom co-op server is stuck on E2M8 and the Doom2 co-op server stuck on Map30; both final maps.
The reason the DM servers always work, is because they have the server side option to disable map exits set to on.
The co-op servers presumably don't have that option enabled.
As a short-term workaround I modified the co-op server map cycles to not include the last maps of each episode. They now cycle through the other maps in order.
I.e Dday would read the loaded MAPINFO lump or Map Info def and base off the 'cluster' information, to work out where each hub starts and ends.
Obviously, with Vanilla HeXen MAPINFO an assumption would probably have to be made that the first map in a new cluster is the start of the hub, but Dday's Map Info defs could maybe have a field added to indicate to Dday that the map is the start of the hub, for Dday mods that feature hubs.
Obviously, I may be missing something important in my analysis above.