---

Nuxius said:
There are quite a few people in the Doom community who still use vanilla Doom, so no, you are not alone.

If you want to submit anything to COMPET-N you have to use it.

---

---

From the COMPET-N rules:
Using a different EXE other than DOOM.EXE v1.9 (size 715493 bytes) for Ultimate DOOM, DOOM2.EXE v1.9 (size 709905 bytes) for DOOM2 and Final DOOM, DOOM2.EXE v1.9 (size 722629 bytes) for Final DOOM is not allowed.

---

---

Nuxius said:
Not even Chocolate Doom.

---

---

Nuxius said:
Not even Chocolate Doom.

---

---

Donce said:
Yep. And using Win98SE and a CRT monitor. Anyone managed to make 320x200 look at least half decent on LCD as it looks on a CRT?

---

---

Gez said:
I'm pretty sure a line like "DOOM2.EXE v1.9 (size 709905 bytes) for DOOM2 and Final DOOM, DOOM2.EXE v1.9 (size 722629 bytes) for Final DOOM" must be very confusing to the uninitiated.

---

---

Intel17 said:
Do you guys use vanilla DOOM at all?

---

---

printz said:
They can't tell what exe you're using to record!

---

---

DuckReconMajor said:
I don't know if he was full of crap or not (the only bug I can think of is the "no more than 8 letters in filename" thing)

---

---

myk said:
Not full of crap, but since the base system is different, something unusual could hypothetically produce some difference, but you should be fine for practically any purpose. Although, as you may know, you can use long file names in Doom. The file this_name_is_too_long.wad becomes this_n~1.wad, for example, and if you add another called this_name_is_even_longer.wad, you get this_n~2.wad, and so on.

---

---

printz said:
They can't tell what exe you're using to record!

BTW, playing vanilla Doom when making a classic non-limit-removing map is a must.

---

---

myk said:


Not full of crap, but since the base system is different, something unusual could hypothetically produce some difference, but you should be fine for practically any purpose. Although, as you may know, you can use long file names in Doom. The file this_name_is_too_long.wad can be read as this_n~1.wad, for example, and if you add another called this_name_is_even_longer.wad, you use this_n~2.wad, and so on.

I do it sometimes because some newer vanilla or limit removing WADs, as well as some new demos, are uploaded with longer names, and it's less confusing than renaming the files. Producing vanilla stuff with short file names is still recommended, of course, because it's unambiguous.

---

---

Never_Again said:
Chocolate DOOM comes close but it still has some display issues, e.g. the transparent non-shoot-through walls (e.g. a few windows on OTTAWAU.WAD E2M1).

---

---

Never_Again said:
After 12 years of source ports there is still no 100%-accurate replacement for vanilla. Chocolate DOOM comes close but it still has some display issues, e.g. the transparent non-shoot-through walls (e.g. a few windows on OTTAWAU.WAD E2M1).

---

---

Never_Again said:
After 12 years of source ports there is still no 100%-accurate replacement for vanilla.

---