>>6723365Here is a quote from page 7 of that thread, regarding some errors with some textures:
>The colored line in the sky is because in this PWAD the sky texture consists of only a single patch and is thus not composed, so the columns are rendered directly from the patch lump. The two colored horizontal lines correspond to the palette colors for the patch's column length and offset values. The cut-off chain texture is because the texture width is not a power of two but some other arbitrary value. >Both issues are stricly Doom (and even Boom/BMF) incompatibilities! They would have popped up earlier if PWADs were actually tested with the ports for which they claim compatibility. It's high time people realize that "works with PrBoom+ -complevel 11" does not mean "MBF-compatible". Especially, since PrBoom+ has derived central parts of its patch and texture processing code directly from ZDoom. Luckily the only bugs seem to be minor texture bugs like the magenta lines in pic related
>>6723630>Woof has potential to be a great source portI agree. Imagine, not a Boom-compatible Crispy Doom... but an MBF-compatible Crispy Doom.
If demo recording is your thing, you will be sad to know that the port is doomed to only record -complevel 11 demos:
>there are compatibility flags to enable playback of Vanilla and Boom 2.02 demos - but let's say they have not been maintained to the same degree that we got used to from PrBoom+. I ironed out much of it, but by far not enough to open it up for demo recording in any other then MBF's own format. I am testing out the 2048 megawad in Woof and so far no problems, but that does not mean that demos recorded in Woof will not desync in Boom.
