[ hostname3 ]
[ -port portnum ] ] [ -mp ] [ -showkeysym ] [ generic-doom-arguments ]
This program is furnished on an AS IS basis for the fun of it. Neither Sun Microsystems or Id Software can support this program.
Sundgadoom is a complex, violent virtual reality game that can be played alone against the monsters or with/against other workstation users. For those unfamiliar with the game, please consult the file README.sun for the basic details, cheat codes, help, ftp locations, .....
In order to work properly, your path needs to include the location of the sundgadoom and sndserver binaries. The wad file must either be in the current directory, or the environment variable DOOMWADDIR must point to where one of the wad files can be found.
Games are always saved to the current directory, so using a consistent directory in which to playsundgadoom is probably a good idea.
These are the most popular options; others used in the PC version of the game may or may not work. They are described fully in the dmfaq666.txt file.
This is perhaps the neatest feature in doom - you can play each other. To start a net game between three workstations named huey, dewey and louie, one would enter the following commands for the respective workstations:
huey% sundgadoom -net 1 dewey louie
dewey% sundgadoom -net 2 huey louie
louie% sundgadoom -net 3 huey dewey
You can choose to play cooperatively or shoot each other in the back - it's up to you.
Sundgadoom works only on Solaris releases 2.4 and above. It has been run on the following platforms: SS1+, IPC, IPX, SS2, SSLX, SS5, SS10, SS20. It has been run on the following framebuffers: CG3, CG6 (GX & TGX), SX, TCX, and ZX. If your machine/framebuffer isn't listed above, try running the sunxdoom executable; this uses the MIT SHM extension to get the pixels on the screen. Yes, it's slower, so use a smaller window.
The best performance will be obtained from machines that have framebuffers on the memory bus such as the SX and the TCX. The SS5, SS10, SS20 and LX do pretty well with a CG6-type framebuffer. The SS2 and earlier machines suffer from the lack of integer divide & multiply instructions.
Note that a SS20 612 with an SX framebuffer running with the -mp and -turbo 255 options is a rather overwhelming deathmatch advantage.
If sundgadoom exits immediately at startup with the message "Game mode indeterminate." it means sundgadoom cannot find the wad files. One of the wad files specified above must be present in the current directory or the environent variable DOOMWADDIR must point to where one of the wad files may be found.
Occasionally the colormap will not install properly; this is a known bug. Pressing tab or any other key will often fix it, but sometimes it is necessary to restart the game. The game always maps in the center of the screen; place the cursor where the game ends up mapping prevents this from occurring.
The high/low graphic detail selection is broken and will not be fixed - run it in the default high resolution mode.
In order to allow the game to run as fast as possible,sundgadoom refuses to render the screen if it is at all obscured. Any window or icon or menu placed on top of the screen causes the game to stop rendering. To resume play, remove the offending window.
Keep in mind that some of the doom][ wads have bugs; errors such as Bad texture map column are in the wad, not in the game.
Note that any other features of the game are just that - features. This game is offered as-is, with no support possible or offered from either Sun or id Software. For help, please try the doom-related newsgroups such as rec.games.computer.doom.*. Neither id Software or Sun or anyone who worked on this project is responsible for any missed deadlines, meetings or loss of sleep and productivity resulting from playing sundgadoom.