Having trouble loading wads on server using shell
I have no problem creating my own server and having others join, but when I try to have the server load a custom wad by putting "load epic2.wad" for example in the options the map is not loading correctly. I will see the map from a distance and can't move (see screenshot).
- I have the latest version installed
- I do have epic2.wad enabled when launching doom2
- I have the epic2.wad file in both my custom wads folder and the server-runtime folder (see screenshot)
Perhaps I am missing something simple here? Others connecting to my server with the custom wad will see the same thing.
Screenshots:
https://drive.google.com/file/d/0B9rSwzu-UaOEblFpdmpFUXJMdkU/view
https://drive.google.com/file/d/0B9rSwzu-UaOEbl9NTnk5a0o5YlE/view
- I have the latest version installed
- I do have epic2.wad enabled when launching doom2
- I have the epic2.wad file in both my custom wads folder and the server-runtime folder (see screenshot)
Perhaps I am missing something simple here? Others connecting to my server with the custom wad will see the same thing.
Screenshots:
https://drive.google.com/file/d/0B9rSwzu-UaOEblFpdmpFUXJMdkU/view
https://drive.google.com/file/d/0B9rSwzu-UaOEbl9NTnk5a0o5YlE/view
Comments
Machine specs:
AMD FX8350 Processor
16GB RAM
AMD HD 7970 Graphics card
Windows 10 Pro 64-bit
240GB Corsair SSD
I can see how this is a bit confusing, though. My plan is to have the Shell show this kind of options as GUI widgets in the future.
In practice, you can issue console commands via the command line options. Try putting this in the Options field:
I tried uninstalling and reinstalling just now and that also didn't work. No trouble loading the custom wads in single player either. Seems like only the server is having trouble loading it. I tested other wads too, same result.
Doomsday.out from server-runtime folder:
any other ideas?
Check out the server-runtime Doomsday.out above. I have -file with the directory and file specified, there's no spaces or anything funky in the file path. The log shows the server continues to load the maps from Doom2.wad and ignores the file command. I also find it odd that there's a large spacial gap between 18: and 19: in the command line options.
So when the server is starting, it is not loading game resources from the custom wad like it should be. I understand how to do it but can't figure out why it's not working on my machine.
My primary desktop/gaming PC has likely seen several versions of doomsday since ~2012, including some of the unstable versions I've tested. I wonder if there are some lingering files from old installations preventing the server/shell from functioning correctly. I noticed when I uninstalled, deleted the install folder, and reinstalled it still kept the server shell preferences and settings.
I think I need to completely remove doomsday and reinstall to a fresh directory to get this working on my primary machine.
Looking at my server-runtime doomsday.out I notice this line that does not appear on my laptop with the working/fresh install:
Skyjake-If there is something lingering from testing a 2.0 version, how could I go about completely removing it?
All the persistent information is kept in the "(server-)runtime" folders. You could first try renaming your existing "C:\Users\TimothyJames\AppData\Local\Deng Team\Doomsday Engine\server-runtime" to something else, so Doomsday will recreate it with default contents.
I completed the following steps:
- Uninstalled
- Deleted folder from Program files
- Deleted front end directory from My Documents
- Deleted folder in AppData\Local
- I did a Ctrl+F in the registry and deleted anything Doomsday related
- Rebooted
- Reinstalled in different directory
Probably overboard but I'm happy to have finally got it working. Thanks all!