GitLab

The cfg file should reflect the user's preferences even if the features
don't take effect. The cvars' descriptions document the incompatibility
that is happening.

- r_texfilter
- r_anisotropy
- r_useindexedcolortextures

I hit an assertion at 64.

It is an optional part of xxHash we are not using that breaks the build
everywhere but x86*.

VS: fix "C1083: Cannot open compiler generated file" error with polymost1Frag.glsl.cpp and polymost1Vert.glsl.cpp

I'm not entirely happy with this due to the addition of the extra filter in the IDE to hold the generated files, but it's better than having to hit build twice in order to get a successful compilation.

BUILD & Duke3D: lower the clamp value for "vid_brightness" from 0 to -10, allowing for negative brightness config to be saved

Needed because GOG .pkg installers default to the Documents folder

ZOOM Platform ships it with their DLC Pack.

This reverts commit f1aec344.

This avoids a bug which causes linking to fail for MinGW32 builds.
Co-authored-by: Evan Ramos <hendricks266@gmail.com>

Previous to this commit, the game would hijack the sprite, wall and sector
arrays to store the label data temporarily, which would get copied into
freshly allocated arrays once the scripts were fully parsed.

This lead to the maximum number of labels depending on MAXSPRITES.
This coupling is now removed, and an independent limit MAXLABELS
has been introduced, which is currently set to 16384.

Additionally, the limit is now checked before character data is loaded
into memory, rather than afterwards, preventing out of bounds accesses.

No longer backup the walock, waloff and picsiz arrays as this caused
problems elsewhere.

Fixes #66