The firing frames for the zombie and assault tripod look weird if they're not
shown in full brightness, so add a dehacked tweak to set them to full
brightness. Doom has the same bug but it isn't quite as noticeable.
This could theoretically cause a mod compatibility issue since unexpected
frames might be fully lit. However, (1) the worst that can happen is a minor
cosmetic issue, and (2) I don't know of any actual mods this affects (maybe
there aren't any). I think the benefit outweighs the potential downside.
DOOM2.WAD contains a MAP33, which is being represented here as only
the dummy map, and also M_EPI1 and M_EPI2 lumps for the “Hell on Earth”
and “No Rest for the Living” texts, both of which are now replicated
here as well (using “Phase 2” and “The Missing Levels” as names instead).
No, we still don’t plan on having a real MAP33, the inclusion here is
only to avoid engine crashes.
Fixes: #533
Ref: #529
Split the piano and bass guitar groups into separate groups to give more
variation. Move several instruments around which don't fit, and move
several random percussion instruments into an enlargened "blank" group
since these percussion effects are not really similar to each other and
it's better to leave them out than play something that sounds wrong.
Replace all {S,W,B}FALL textures in the levels with their animated
equivalents, and remove {S,W,B}FALL from textures.cfg.
The {S,W,B}FALL were leftovers from when Freedoom had the goal of
being Boom-compatible instead of vanilla-compatible.
Also, rebuild these levels' nodes and reject tables with ZenNode.
A useful vanilla-compatible trick is that it's possible to include
sprites as patches inside texture definitions. It turns out that
both Final Doom IWADs added textures which do this, and Freedoom
inherits this as a result. We shouldn't include these sprites in the
pnames.txt that gets generated for inclusion in wadinfo.txt, since
they're already defined in wadinfo.txt under [sprites] and won't
be found under patches/ anyway.
This should help as a step towards resolving #485.
Map changes since v0.11 have desynced these. I recorded demo2_p2
keyboard-only, so the gameplay is extra bad. On demo4_p1, I used
a mouse, so it is a little more skillful.
Causes conflicts with ZDoom mods that try to define their own HUDs,
at least three on IRC were reported as being basically totally broken
with Freedoom 0.11. While it was a good attempt at adding an
enhancement to Freedoom under ZDoom, we cannot afford to break mod
compatibility.
The tags are shorthand for the license of each file and avoid
copying the full license text into each one (and avoids having
to manually update the dates in each one...).
The .gitattributes file tries to enforce Unix newlines, for
Windows users, but somehow this still got forced through...
It messed up the display of `git status`
Redefine all of the new aquatex textures to be 128px tall.
This avoid tutti-frutti in vanilla Doom, where textures do not tile
property unless their heights are a multiple of 128.
Discussed in PR #292, this change was a bit pointless and driven by
too much eagerness to be different than Doom. These terms are
well-accepted in the FPS genre and changing them will only be
confusing.
This partially reverts 2016-08-29T14:15:32Z!ayubahmed2240@gmail.com
GitHub’s AsciiDoc parser barfs on the standard AsciiDoc syntax to
represent such characters with only ASCII… Well, everybody should
support UTF‐8 these days. Let’s just use these directly.
Revised Phase 2 screens and some monster name changes.
New/modified lines to the pickup messages, to make it feel unique.
Added better story screens for Phase 1.
Minor edits to Phase 2's story screens.
All levels in Phase 2 have been named:
-MAP06 (Voltcom9)
-MAP09 (Kristien "sajbear" Nilsen)
-MAP10 (Jewellds)
-MAP26 (DragonMorpheus)
-MAP27 (Voltcom9)
All levels, but C3M5, in Phase 1 have been named:
-C2M3 (Voltcom9)
-C3M4 (Voltcom9)
The DMX sound library used by Vanilla Doom has a bug where instruments
referencing other instruments as stand-ins can only reference
instruments listed earlier in the file. Actually, the instrument
references are just arbitrary cross-reference tags and the first
instrument to use that tag is used for all instruments with that tag.
This behavior can have some strange effects; more information can be
found on David Flater's page: <http://www.flaterco.com/kb/DOOM/DMXGUS/>
This has consequences for Freedoom's GENMIDI generation, particularly
as Chocolate Doom now emulates this behavior. To avoid assigning the
wrong instrument mappings, change the ordering of instruments in the
output file, so that "leader" instruments always appear earlier in the
file than instruments that reference them.
Some textures which appear in both doom.wad and doom2.wad are defined
differently in each. We were always using the same definition in both
Phase 1 and Phase 2, causing compatibility problems with some levels
which expected a particular version of the texture.
To resolve, add both versions of the conflicting textures, controlled by
a new DOOM1_VERSIONS #define that allows which the version to be
selected. Use the doom.wad versions for Freedoom: Phase 1, and the
doom2.wad versions for Freedoom: Phase 2. This resolves part of #194.
