Michael Bäuerle

Bossaction problem

The reason for the intermediate data is to provide a thread-safe API. The parser itself is not thread-safe. The library selects the last (not the first) entry, if there are multiple entries. The UMAPINFO specification is not very precise what should happen in such cases.

Looks good now. Ticket can be closed.

On my system "Auto" does the same as "Fit_Height" (looks wrong with both). I have used 1280x1024 pixels fullscreen, but a test with a 320x200 window shows the same problem. The settings "Fit_Width" and "Stretch" do not show this problem. The attached archive contains the WAD file and some screenshots (there is also a screenshot from PrBoom+ for comparison).

Sorry for the late answer. Thank you for merging UMAPINFO support! I have done a quick test with 1.48.14 and it seems to work as expected. I have not looked at the details yet.

Flats not rendered correctly with viewfit set to auto

Does this discussion explicitly cover the content of the library, or just the interface between the library and DoomLegacy All code proposed in this FR was written by me (the library itself, the glue code for the engine in "umapinfo.c" and the patches for the engine to use the UMAPINFO data). Nobody else has a copyright on (parts of) this code. You have explicit permission to cherry pick and integrate the code (including the library code) under the Doom Legacy license (GPLv2), as this seems what...

From my understanding, you cannot make that version with that copyright cease to exist, as someone else may have relied upon what that copyright says. No, my comment was about the law in some countries. The final 1.0.0 release of the library (with BSD license) is now available here: https://micha.freeshell.org/libdoom-umapinfo/ Attached is a version containing the same code, but without the copyright line and a literal copy of the GPLv2 license from Doom Legacy. This version should allow you to rip...