NetDoom and Randoom 1.52

[Pierre Fournier]

We tried to use Randoom 1.52 to play NetDoom 1.2. It seems Randoom
messed everything up. We were never able to play because Doom was either
freezing or crashing with the message "consistency failure".

We decided to all do "randoom -D" to restore everything back, but
the problem always reappeared. Our only solution was to reinstall Doom on
the four machines so we can get a clean doom.wad.

I'm writing this to know if anybody succesfully ran NetDoom with
Randoom... if not, forget about using randoom. It really messes up your
doom.wad for network games.

[Wade Bortz]

Pierre Fournier (pierref@atlantis) wrote:
: We tried to use Randoom 1.52 to play NetDoom 1.2. It seems Randoom

: messed everything up. We were never able to play because Doom was either
: freezing or crashing with the message "consistency failure".

You need to have identical wad files on each computer to play netdoom - it wouldent work if one guy had a BFG 9000 where someone else had a louie. Since you didn't give randoom a seek character, it uses the system clock for a seed number, so each computer gets a compleatly different wad file. Try using -cx, where x is your seed character, or better yet, randomized only 1 of the wad files and copy it to each of the other computers using the net. Could take a while, but is sure-fire (i think?). Have fun!

[Scott Coleman]

pierref@atlantis (Pierre Fournier) writes:
^^^^^^^^^^^^^^^^

Sorry, tried emailing this to you, but because of the incomplete address
the reply bounced. You might want to have a little chat with your
sysadmin... ;-)

> We tried to use Randoom 1.52 to play NetDoom 1.2. It seems Randoom
>messed everything up. We were never able to play because Doom was either
>freezing or crashing with the message "consistency failure".

> We decided to all do "randoom -D" to restore everything back, but
>the problem always reappeared. Our only solution was to reinstall Doom on
>the four machines so we can get a clean doom.wad.

RanDOOM 1.52 is an old version which was released prior to DOOM 1.2;
consequently, 1.52's restore function does not work with DOOM 1.2.

Grab RanDOOM 1.55 from wuarchive.wustl.edu, directory

/pub/MSDOS_UPLOADS/games/doomstuff/rdoom155.zip

--
Scott Coleman tm...@uiuc.edu
President ASRE (American Society of Reverse Engineers)
Ed Green Fan Club #005

[Mark Drunken SkullPopper Chen]

> > We tried to use Randoom 1.52 to play NetDoom 1.2. It seems
Randoom
> >messed everything up. We were never able to play because Doom was
either
> >freezing or crashing with the message "consistency failure".
>
> > We decided to all do "randoom -D" to restore everything back, but
> >the problem always reappeared. Our only solution was to reinstall Doom
on
> >the four machines so we can get a clean doom.wad.
>

i've experienced both problems too...
the first is really easy to solve:
all the wad files have to be identical for all the computers
that means that you can't run randoom on all of your machines because
since it is random the doom.wad files won't be the same...
in order to fix this you have to randomize it on one machine and then copy
the doom.wad file to the other machines...
this can take a while.... on a serial port it takes about 20 minutes i
think for each copy...

the second problem is probably this...
you don't have the same versions of randoom on all of your machines...

i'd go and get 1.55 from wuarchive
i know there's another randomizer called jumble and it's supposed to be
able to randomize for netdoom, but i don't know if it works well or not

mark

[Thomas Naughton]

In article <2ko6e2$e...@scratchy.reed.edu>,

Mark Drunken SkullPopper Chen <gc...@envy.reed.edu> wrote:
>the first is really easy to solve:
>all the wad files have to be identical for all the computers
>that means that you can't run randoom on all of your machines because
>since it is random the doom.wad files won't be the same...

Randoom works just fine for networked games! We use it
all the time and have no problems. All you have to do is agree on
a seed. We usually do a `randoom -d` before each network session,
and then announce the seed. Something like: "The seed is 'r'".
Then everybody does a `randoom -m2 -wdeath.w -cr`. We have no
problems and it's a lot easier to copy the death.w file to each
machine than a 10MB wad file. Remember that no (repeat "no")
computer can generate a truly random number, they all need a seed.
If you can all choose the seed all the wad files will end up the
same.

--
Tom Naughton naug...@htc.com Hull Trading Company (312)697-2715
"The Net interprets censorship as damage and routes around it."
-John Gilmore