Woolie Wool

So what exactly will I need to do for this? Will I need to download a specific branch from github and compile it manually? Currently I'm using the Arch AUR build script which I think is just straight from github master.

I could use portmidi, but ALSA is definitely better--it has less of a chance of introducing errors (e.g. hanging notes) when playing midis, and I do not have to open helvum to run a patch from the UM-ONE adapter (which runs to the Sound Canvas) to "Midi Through Port 0", as the low-level ALSA interface seems to detect my UM-ONE immediately.

I forgot you had forked from WinMBF instead of PrBoom and thus there never was an original Linux version to add features back from. SDL does have midi but I have no idea how to assign it a device under Linux. PrBoom-plus has both SDL and ALSA midi as well as OPL and (I think) FluidSynth. I know some soft synths like Timidity present virtual devices so if you did add ALSA midi you would not need hardware to test with.

Guess I'll be using prboom-plus under Linux then and have to forgo the HRTF and other fancy things Woof has, at least for now. Is there any possibility of this being added back? Especially if you can address MIDI devices directly like GZDoom instead of making me fuck around with patchbays every time I want to play Doom (and I still haven't figured out SDL midi on Linux).

Set your resolution to 320x200 (4:3) or 426x200 (16:9) in prboom-plus, it is an older port than Woof and might give you better performance. However, don't expect an old computer to play just any map. On my single-core Athlon XP rig there are many maps I cannot play, and I have the advantage on the Athlon of being able to use native 320x200 with a CRT under a legacy prboom version that has much, much less overhead than modern ports--the code that lets low resolutions display on modern-ish displays and GPUs has a performance cost. Things like "Kythraessos" from Legacy of Heroes or "God Machine" from Sunlust are still unplayable unless I switch to my modern Ryzen rig. I would strongly consider getting a better computer, even a used laptop that is a few years younger would be a significant improvement and will cost much, much less than a new computer. E: in general (though there are of course exceptions) older versions of source ports will generally give you better performance. Features add overhead, and overhead is the enemy of low-spec computers. If that means you have to live without modern amenities like HRTF audio or rewinds or other newfangled features, and miss out on MBF21 wads, so be it.

Does the Linux version of this support ALSA midi at all? I finally got an (annoying, inconvenient) way to get my SC-88 working with Doom source ports under Linux, but Woof does not seem to allow me to use it.

Does anybody know how to set up the default MIDI device in Linux? GZDoom can address my hardware synth directly but other ports generally use something like "portmidi" or "midi port 0" and I have been unable to figure out what exactly this is or how it works.

If you have a desktop, just use both. My main PC runs two SSDs (for Windows and Linux) and three HDDs (for data).

Running pacman -Qs cmake yields: local/cmake 3.26.3-1

Building on Arch Linux through either AUR or github results in the following errors: CMake Error in src/CMakeLists.txt: Imported target "SDL2_net::SDL2_net" includes non-existent path "//include/SDL2" in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include: * The path was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and references files it does not provide. CMake Error in src/CMakeLists.txt: Imported target "SDL2_net::SDL2_net" includes non-existent path "//include/SDL2" in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include: * The path was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and references files it does not provide. I reinstalled SDL2_net and rebuilt another program that uses sdl2_net (ECWolf) to ensure it wasn't SDL2_net's fault. Note that I have built the previous version of Woof from AUR successfully. E: also successfully built DSDA Doom to further test SDL2_net, no issues

I guess it depends on what you want to do with it. My Lenovo ThinkPad T520 is 12 or 13 years old and, with a RAM and SSD upgrade, still works great as an internet appliance using Arch Linux/KDE (the P key on the keyboard is going however, and I might have to eventually replace the keyboard if I want to keep using it). Gaming on it, however, is just a non-starter for any game made after around 2001, especially since I disabled the nVidia GPU to extend its miserable battery life and avoid having to deal with nVidia's shitty Linux drivers. As far as "gaming laptops" go, if I wanted to play serious games on a laptop I would just get a Steam Deck or a Nintendo Switch.

Unfortunately I am in a pretty hard financial situation and have no money to spare, but this is a horrifying story and I wish Laz the best in clearing his name and getting his life back together. His mods (especially the WolfenDoom versions) were a tremendous influence on my Wolf3D modding career and were also the first Doom pwads I ever played, getting me into both Doom wads and source ports (the first port I played back in 1999 was MBF because he recommended it). E: Laz was also the way a lot of PC users (myself included) learned of the "Mac Family" of Wolfenstein with its different mechanics and Second Encounter level set, and he contributed tremendously to raising awareness of these versions of the game and preventing them from sinking into obscurity beneath the shadow of the far more popular and accessible PC version.

Nearly all modern ports support resolution scaling, so have you considered reducing your resolution? I assume you're using a software renderer since GL renderers tend to vastly outperform them in terms of FPS. Reducing your resolution by half will mean your CPU has to do only a quarter of the work to render the scene. And speaking of that, I've been replaying 2022ADO under DOS and discovered that the set is almost fully compatible with MBF-SNM 2.04. The only problems are E3M5 (causes a segmentation violation on map load), E5M9 (level progression is hardcoded in MBF-SNM so the secret exit is in the wrong map), and the M10 maps (but I didn't like them anyway). Aside from that the set runs beautifully under DOS on my Athlon, with no FPS drops even in the largest setpieces.

New bug found while playing E3 of 2022 A Doom Odyssey: E3M5 in Ultimate Doom exits to the end of episode rather than to E3M6. I confirmed this also works with a bare iwad, not just in 2022ADO. E: is there any way to define new episodes in Tartar? Even if we can't have full UMAPINFO, it would be really nice to have 2022ADO fully playable under Tartar.