This is Woof! 14.5.0 (Apr 30, 2024)

[NightFright]

Does this change if you switch complevel to something else? Could actually also be an issue with sky lump definitions.

Edited June 10, 2022 by NightFright

[LuciferSam86]

I'll try it tomorrow and update my previous post. Thanks for the tip, NightFright. 

Edited June 10, 2022 by LuciferSam86

[fabian]

10 hours ago, rzh said:

And I already found an unwanted effect with it :P

Not sure if it can be fixed though.

The bridge/ pathway also swirls.

 

BTW, which WAD/MAP is this?

[fabian]

2 hours ago, LuciferSam86 said:

I found this on Map 03: a weird HOM effect that doesn't exist if I play it on GZDoom.

 

Hm, the same HOM appears in PrBoom+, but not in Crispy Doom. Strange!

[LuciferSam86]

1 hour ago, fabian said:

 

Hm, the same HOM appears in PrBoom+, but not in Crispy Doom. Strange!

Oh and another thing. 

First map of Attack , there's an hidden blue armor , on gzdoom is ok but on woof I can see the blue armor "inside" the pedestal .

I'll take a screenshot tomorrow so you can see. 

[BMWAG65321]

I did some prodding around and found more HOM crucifixes in the southwest arena.

- HOMs in latest GZ software, Woof [all compat levels] DSDA [only tested default and 1.9]

- Black texture in latest Crispy

- Transparent in GZ hardware
 

Screenshots:

Spoiler

GZDoom, Software

 

Crispy

 

Woof!

 

 

27 minutes ago, LuciferSam86 said:

on woof I can see the blue armor "inside" the pedestal .

That's part of the old columns renderer. A lot of things appear to be slightly in the floor with it. The way GZ's hardware renderer works, the parts of the sprites that should be in the ground, are, and aren't visible. To get around how crappy that would look, there's sprite clipping options in full options to raise them so you can see more, or all of the sprite. The easiest way to see the amount of offset is to go to Display Options [Simple options] or Set video mode [Full options] and cycle through the render modes on a busy scene.

[rzh]

6 hours ago, fabian said:

 

BTW, which WAD/MAP is this?

It's E4M1 of Favillesco Alpha Episode: Apostasy on Amalthea.

[liPillON]

2 hours ago, rzh said:

It's E4M1 of Favillesco Alpha Episode: Apostasy on Amalthea.

 

the starting room's ceiling also swirls... weird

 

[NightFright]

Hum... note @ self: maybe better to keep that swirling liquids option turned off for pwads.

Edited June 11, 2022 by NightFright

[LuciferSam86]

I've tried with DSDA-Doom in software mode: the same problem as Woof! with the HOM, but when I changed to OpenGL renderer the HOM in Map03 disappeared.

 

Edit: in OpenGL mode, it disappeared the blue armor "inside" the pedestal, too

Edited June 11, 2022 by LuciferSam86

[Shepardus]

I don't think the problem is with Woof or dsda-doom here, I've seen Crispy Doom not render HOMs that it should, such as the infamous "illusio-pit" in wow.wad:

Spoiler

 

Edited June 11, 2022 by Shepardus

[fabian]

On 6/11/2022 at 12:09 AM, fabian said:

Hm, the same HOM appears in PrBoom+, but not in Crispy Doom. Strange!

 

Sorry for my bs, of course there is HOM in Crispy. It is just that I decided back then to render HOM in black, which makes it nearly impossible to spot such mapping glitches. I will fix this.

[fabian]

On 6/11/2022 at 6:39 AM, rzh said:

It's E4M1 of Favillesco Alpha Episode: Apostasy on Amalthea.

Alright, thanks! I just checked this map out with swirling flats and indeed the bridge flats are also swirling due to the animated slime gaps in the ladder structure. 

 

Also, I was considering to add some "flow" to swirling flats as seen in International Doom, but this effect would make things even worse in this case. 

[Average]

Hey folks.  I have encountered an issue in the last few dev builds.  I load a weapons/graphics mod through the config file:

 

[("")] WAD file preloaded at program startup 
wadfile_1                  "C:\Doom\D4W_Final.wad"

 

 

It worked perfectly until a couple of builds ago.  Now, it the game loads but the auto loading mod in the cfg is ignored.  Checking back it seems master build 1240 was the last one that worked as expected.

[rfomin]

6 minutes ago, Average said:

Now, it the game loads but the auto loading mod in the cfg is ignored.

We have replaced this with the autoload folder. Just place the file in the woof/autoload/doom-all/ folder.

[Average]

I've tried that but it doesn't load from there either.  I've gone back and tried on previous builds. 1241 was the last one that loads my WAD from the autoload folder.  To clarify, I have only tried the master builds.  To clarify further, the mod loads and works fine when dragged onto the EXE or when loaded through ZDL or Doom Runner.

[rfomin]

7 hours ago, Average said:

I've tried that but it doesn't load from there either.

I just checked and it works for me. If you build it yourself, there will be several autoload folders in the repository. You need to place it in the autoload/doom-all folder where woof.exe is located.

[lisiczka]

As I see that Woof gets more and more QoL changes together with Crispy HUD, I once again suggest my own layout I made for GZDoom)))

 

In any case, it could improve Crispy HUD if you move the mugshot to the left instead of keeping it at the center over the weapon sprite. Just my opinion))

[fabian]

4 minutes ago, lisiczka said:

As I see that Woof gets more and more QoL changes together with Crispy HUD, I once again suggest my own layout I made for GZDoom)))

 

Sorry, but this gets the same reply as this here:

https://github.com/fabiangreffrath/woof/issues/593#issuecomment-1151368134

[Average]

9 hours ago, rfomin said:

I just checked and it works for me. If you build it yourself, there will be several autoload folders in the repository. You need to place it in the autoload/doom-all folder where woof.exe is located.

I just download the 'nightly' builds from the repository. :)

 

I have created a new folder and put the latest build into it and moved my autoload folder over to the new installation.  My mod now loads (I presume there was some incompatibility in the old cfg file).  However, my mod contains its own palette which seems to be overwritten by the IWAD now.  That didn't happen before.  How would I get my mod palette to remain intact?

[fabian]

The IWAD is always loaded first, before anything from the autoload directory, so this is most probably not the cause for the issue you see. However, files from the autoload directory are loaded in alphabetical order, and thus probably in a different order than before. So, it's possible that a file that gets autoloaded after your mod overrides its palette, which you have never seen before, because your mod was loaded last? If this is the case, please change the alphabetical ordering of your autoloaded files by e.g. preceding them with '00_' or similar. 

[lisiczka]

3 hours ago, fabian said:

 

Sorry, but this gets the same reply as this here:

https://github.com/fabiangreffrath/woof/issues/593#issuecomment-1151368134

 

No problem, I should have check the issues tab first. Crispy HUD is fine, but I'd still appreciate if you could move the mugshot away from the center)

[NightFright]

One could either (optionally) place the mugshot where the medikit symbol is or instead of the ARMS display (which isn't that useful, anyway).

[Average]

6 hours ago, fabian said:

The IWAD is always loaded first, before anything from the autoload directory, so this is most probably not the cause for the issue you see. However, files from the autoload directory are loaded in alphabetical order, and thus probably in a different order than before. So, it's possible that a file that gets autoloaded after your mod overrides its palette, which you have never seen before, because your mod was loaded last? If this is the case, please change the alphabetical ordering of your autoloaded files by e.g. preceding them with '00_' or similar. 

 

Thanks for the info.  I have now managed to get it loading correctly using the above method.  Again, thank you @rfomin and @fabian for your help. :)

[liPillON]

hi, is there a menu option (a config variable is fine too) to colorize the stats counters in the automap?

on my end labels and values are both displayed in red (map name in yellow)

 

IIRC crispy does this when "colorize hud elements" is set to "hud texts" 

 

 

[fabian]

No, but we can add this after the 10.0 release. Could you please file a request on the github tracker, so we won't forget it?

[liPillON]

so a new release is approaching, eh? congrats!

though I was hoping this feature would have made the cut

 

/edit

github issue created as #605

 

Edited June 16, 2022 by Delfino Furioso

[NightFright]

Looks like v10.0 is out. ;)

[fabian]

Woof! 10.0.0 is released on Jun 17, 2022.

 

Main Features

 

• Implement Crispy HUD as an alternative to Boom HUD.
• Add mouselook implementation.
• Stretch short skies (< 200 px height) optionally, else fill with a solid color (from Eternity Engine).
• More demo playback QOL features (progress bar, -skipsec, fast-forward key).
• Smooth diminishing lightning from Crispy Doom.
• Gradual decrease/increase of gamma from Doom Retro (the old gamma levels are still available with the default F11 key).
• Brightmaps for textures and sprites from Crispy Doom.
• Add woof-setup multiplayer launcher with master server browser (from Chocolate Doom).
• Add support for SMMU swirling flats.
• Strict mode (sets compatibility and cosmetic settings according to DSDA rules).
• Fix netgame level reload.
• Fix uncapped mode in netgame (needs more testing).

 

Binaries for Windows are available here:

 

https://github.com/fabiangreffrath/woof/releases/download/woof_10.0.0/Woof-10.0.0-win32.zip

https://github.com/fabiangreffrath/woof/releases/download/woof_10.0.0/Woof-10.0.0-win64.zip

Have a lot of fun!

[Lila Feuer]

congratulations on the release! 😁 will update my build when I get around to playing Memento Mori II