This is Woof! 14.5.0 (Apr 30, 2024)

[fabian]

 

Woof! is a continuation of the Boom/MBF bloodline of Doom source ports.

 

MBF stands for "Marine's Best Friend" and is widely regarded as the successor of the Boom source port by TeamTNT. It serves as the code base for popular Doom source ports such as PrBoom+/DSDA-Doom or The Eternity Engine. As the original engine was limited to run only under MS-DOS, it has been ported to Windows by Team Eternity under the name WinMBF in 2004. Woof! is developed based on the WinMBF code with the aim to make MBF more widely available and convenient to use on modern systems.

 

To achieve this goal, this source port is less strict regarding its faithfulness to the original MBF. It is focused on quality-of-life enhancements, bug fixes and compatibility improvements. However, all changes have been introduced in good faith that they are in line with the original author's intentions and even for the trained eye, this source port should still look very familiar to the original MBF.

 

In summary, this project's goal is to forward-port MBF.EXE from DOS to 21st century and remove all the stumbling blocks on the way. Furthermore, just as MBF was ahead of its time, this project dedicates itself to early adoption of new modding features such as DEHEXTRA+DSDHacked, UMAPINFO and MBF21.

 

Please visit the project homepage for more information:
https://github.com/fabiangreffrath/woof

 

 

Woof! 14.5.0 is released on Apr 30, 2024.

 

A complete list of new features, improvements and bug fixes can be found on the release page:

 

https://github.com/fabiangreffrath/woof/releases/latest

 

Binaries for Windows are available here:

 

https://github.com/fabiangreffrath/woof/releases/download/woof_14.5.0/Woof-14.5.0-win32.zip

https://github.com/fabiangreffrath/woof/releases/download/woof_14.5.0/Woof-14.5.0-win64.zip

 

An AppImage for Linux is available here:

 

https://github.com/fabiangreffrath/woof/releases/download/woof_14.5.0/Woof-14.5.0-Linux.appimage

 

Have a lot of fun!

- Fabian

Edited April 30 by fabian
Woof! 14.5.0 is released on Apr 30, 2024

[Spectre01]

In layman's terms, what features does this port contain which differentiate it from PRBoom+?

[drfrag]

 Missing zlib1.dll.

[Linguica]

I compiled a Mac executable for the chosen few who might find that useful.

 

After a minute of testing, for some reason this feels more responsive than Eternity, which still has weird mouse lag for me for some reason. Plus it's not the mess that prboom-plus is. I think this may have instantly shot to the top of my Boom-compatible ports list.

 

woof.mac.zip

[fabian]

13 minutes ago, drfrag said:

 Missing zlib1.dll.

Ah, sorry! The build system is still WIP. 

[Linguica]

 

[Diabolución]

For when the sugarless variant?

[Redneckerz]

So glad i could play test this - Try it out. Its *perfect* for those who want more than Chocolate Doom but do not want Crispy for whatever reason

 

The biscuit port to give to your dog. 

Edited February 29, 2020 by Redneckerz

[drfrag]

Quote

is some good glitchcore

 That should not happen, even in RUDE it looks mostly good and it still has pretty much the vanilla renderer with a few fixes.

 I think the same happened here and i applied some fix but i don't remember what i did right now.

 Edit: could be "Fix rendering error casued by overflow of the rw_distance variable" or "fix overflows in R_PointToAngle() for very long distances" (with their prerequisites).

Edited February 29, 2020 by drfrag

[maxmanium]

As with @Linguica's post, there still seem to be rendering problems on very large maps (drawseg overflows?). Here's Eviternity's MAP32 (which was hard to capture, btw; any chance for PNG screenshots?):

 

Spoiler

  

 

I'm super stoked to see that Woof now supports maps with these node formats though!

 

Also, what future development can we expect with Woof? I have some suggestions but I understand staying within the project's philosophy.

[Linguica]

Would it be feasible to patch the Cardboard renderer wholesale into this?

[fabian]

@Linguica Yeah, sure, why would one want to test a new-born port with a normally sized map? ;) To be true, I have seen these glitches before, as planisf2 is my to-go map for testing compressed ZDBSP nodes (I have the WAD prepared like this lying around on my drive). But I had to get this out of development hell as soon as possible and call it 1.0 one day.

 

Why you felt the need to spread these glitches via Twitter is beyond me, though. Makes my new project look rather crappy, I am afraid. :/

 

8 hours ago, Diabolución said:

For when the sugarless variant?

 

What exactly?

 

7 hours ago, maxmanium said:

As with @Linguica's post, there still seem to be rendering problems on very large maps (drawseg overflows?). Here's Eviternity's MAP32 (which was hard to capture, btw; any chance for PNG screenshots?):

 

Yes, it's in the README. You'll need to put SDL2-Image.dll next to the executable. I'll probably turn this back into a hard dependency for the next release, but the build system needs to be stabilized before (kudos to @AlexMax who is currently at that).

 

7 hours ago, maxmanium said:

Also, what future development can we expect with Woof? I have some suggestions but I understand staying within the project's philosophy.

 

I think I'll fix the visual glitches first, Not sure what's next...

 

6 hours ago, Linguica said:

Would it be feasible to patch the Cardboard renderer wholesale into this?

 

Serious question?

[Diabolución]

@fabian

That fork named DietBoom.

[fabian]

11 minutes ago, Diabolución said:

@fabian

That fork named DietBoom.

That's @fraggle's baby, though he hasn't pulled for a month or so. 

[Redneckerz]

3 hours ago, Diabolución said:

@fabian

That fork named DietBoom.

Oi, that missed my scanners. An updated Boom variant?

[Diabolución]

@Redneckerz

It seems like a heavily trimmed down fork of Woof.

 

Edited March 3, 2020 by Diabolución

[seed]

4 minutes ago, Diabolución said:

@Redneckerz

It seems like a heavily trimmed fork of Woof.

 

How does it differ then?

[Redneckerz]

17 minutes ago, Diabolución said:

@Redneckerz

It seems like a heavily trimmed fork of Woof.

 

Shoud have gone with Bark as its name, then :p

 

Btw Wikipage for this is up and coming, Fabian knows.

[Diabolución]

Anyway, the dietetic variant is mentioned in the network of forks of WinMBF on GitHub. As for differences... look at the commits, I guess.

[Linguica]

5 hours ago, fabian said:

Why you felt the need to spread these glitches via Twitter is beyond me, though. Makes my new project look rather crappy, I am afraid. :/

 

Because it looked cool? I was surprised it even "worked" at all, despite the visual errors. No one is expecting a v1.0.0 to support every extreme test case you can throw at it.

[fabian]

36 minutes ago, Linguica said:

 

Because it looked cool? I was surprised it even "worked" at all, despite the visual errors. No one is expecting a v1.0.0 to support every extreme test case you can throw at it.

 

Ah, okay then. I have mistaken this for one of those "haha look how that fails lol" postings. 

[Redneckerz]

Woof, Woof! Woof! has its own DoomWiki page now.

[andrewj]

13 hours ago, Diabolución said:

Anyway, the dietetic variant is mentioned in the network of forks of WinMBF on GitHub. As for differences... look at the commits, I guess.

Yeah it's about maintaining balance in the universe -- Fabian took Fraggle's chocolate doom and added stuff, so Fraggle took Fabian's woof and removed stuff.

Edited March 1, 2020 by andrewj

[valkiriforce]

This is pretty cool - I also had to download the missing zlib1.dll as mentioned above, and for some reason it spits out an odd error when I try to drag and drop a wad onto the executable, so forgive me of my unfamiliarity. I resorted to using ZDL to launch wads and it seems to work just fine that way. Here is the error in question:

 

 

It's got just the right amount of options to be simple enough to understand - sort of trimmed down from what I'm used to seeing in PrBoom-Plus but that's okay, as I understand the goal of the project. It fixes a few things I wasn't too fond of in my experience with PrBoom-Plus and I've tested it on at least a few wads, it seems to hold up just fine on my end. Looking forward to future updates!

[VGA]

What happens if you timedemo it against prboom+, which of these is faster?

[Linguica]

Why not do it yourself if you want to know?

[VGA]

1 minute ago, Linguica said:

Why not do it yourself if you want to know?

Well, these esteemed individuals already have it set up on their PCs. I don't even have the latest prboom fork.

[fabian]

6 hours ago, valkiriforce said:

and for some reason it spits out an odd error when I try to drag and drop a wad onto the executable, so forgive me of my unfamiliarity

 

This was a plain bug, thanks for reporting!

[fabian]

I have just re-released this as Woof! 1.0.1 with two minor fixes and all the required DLL files included:

 

https://github.com/fabiangreffrath/woof/releases/download/woof_1.0.1/woof-1.0.1-win32.zip

 

[Graf Zahl]

Why are you releasing this only as a 32 bit build?